> When a box is powered on, first bios is loaded and executed, then the boot
> loader, then the operating system.
>
> Now with the introduction of VMM, the boot loader first loads the VMM, then
> loads the OS.
>
> Why not implement a boot loader which is itself a VMM? That is, the boot
> loader can fulfil its traditional function, as to select to load an OS
> separately, but also, it can function as a VMM, which can load two or more
> OSes as guest OSes simultaneously.
>
> I have started a project with the name vGRUB, to enhance GRUB with the
> virtualization functions of XEN. The aim of the project is to simplify the
> hierachy of software. That is, vGRUB is the firmware that between bios and
> OSes.
>
> vGRUB equals GRUB plus XEN.
>
> I am anxious for all your suggestions. Thanks a lot.
It's a good concept. FYI, there are companies doing something similar to this
at the moment, since they're putting Xen in flash on their systems - although
that's almost more like making Xen the *bios*.
Question: with Xen you need a dom0 running in the background in order to
support multiple virtual machines. Where do you see it fitting in your
model? Would it be loaded by vGRUB? Part of vGRUB?
Cheers,
Mark
--
Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/)
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|