info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Hypervisor from Scratch
25 views
Skip to first unread message
James Harris
Dec 1, 2023, 5:26:05 PM12/1/23
to
Perhaps the most flexible model for an OS is one which is designed
potentially to coexist on a machine with other OSes. I don't mean to be
installed in a separate partition and separately bootable but able to
run simultaneously with other OSes.
Under such a model there would be a hypervisor which would essentially
manage the resources of the machine. The OS or perhaps really the
'supervisor' beneath it would be the entity that programs interacted
with. IOW the supervisor would be the OS as far as the programs were
concerned: they would not need to know that it got its resources from a
hypervisor.
With suitable communication between the parts (e.g. see Intel's
vmlaunch, vmresume, etc) someone developing an OS could split his
efforts in two:
1) the management of resources
2) providing an environment in which other programs can operate
That would raise some interesting possibilities such as 'adding' memory
while a machine is running - in that the hypervisor could commit more
memory to a given supervisor, or maybe some hardware really would have a
way of adding and removing banks of memory on the fly.
At any rate, some links on developing a hypervisor:
https://github.com/SinaKarvandi/Hypervisor-From-Scratch
https://nixhacker.com/developing-hypervisior-from-scratch-part-1/
And if memory serves there's at least one person who contributes to this
group who has already worked on an extensive hypervisor.
--
James Harris
potentially to coexist on a machine with other OSes. I don't mean to be
installed in a separate partition and separately bootable but able to
run simultaneously with other OSes.
Under such a model there would be a hypervisor which would essentially
manage the resources of the machine. The OS or perhaps really the
'supervisor' beneath it would be the entity that programs interacted
with. IOW the supervisor would be the OS as far as the programs were
concerned: they would not need to know that it got its resources from a
hypervisor.
With suitable communication between the parts (e.g. see Intel's
vmlaunch, vmresume, etc) someone developing an OS could split his
efforts in two:
1) the management of resources
2) providing an environment in which other programs can operate
That would raise some interesting possibilities such as 'adding' memory
while a machine is running - in that the hypervisor could commit more
memory to a given supervisor, or maybe some hardware really would have a
way of adding and removing banks of memory on the fly.
At any rate, some links on developing a hypervisor:
https://github.com/SinaKarvandi/Hypervisor-From-Scratch
https://nixhacker.com/developing-hypervisior-from-scratch-part-1/
And if memory serves there's at least one person who contributes to this
group who has already worked on an extensive hypervisor.
--
James Harris
Scott Lurndal
Dec 1, 2023, 6:13:09 PM12/1/23
to
James Harris <james.h...@gmail.com> writes:
>Perhaps the most flexible model for an OS is one which is designed
>potentially to coexist on a machine with other OSes. I don't mean to be
>installed in a separate partition and separately bootable but able to
>run simultaneously with other OSes.
>
>U
>Perhaps the most flexible model for an OS is one which is designed
>potentially to coexist on a machine with other OSes. I don't mean to be
>installed in a separate partition and separately bootable but able to
>run simultaneously with other OSes.
>
>U
>And if memory serves there's at least one person who contributes to this
>group who has already worked on an extensive hypervisor.
>
That would be me.
>group who has already worked on an extensive hypervisor.
>
Dan Cross
Dec 1, 2023, 9:15:10 PM12/1/23
to
In article <6MtaN.194061$svP4....@fx12.iad>,
You and I both, I think.
But everything the OP listed has been done.
- Dan C.
But everything the OP listed has been done.
- Dan C.
0 new messages