> On Fri, 2005-02-04 at 02:30 +0000, Ian Pratt wrote:
> > One fairly simple option is to use Linux as a domU boot loader. Boot
> > with an intrd, mount the specified filesystem, read off
> grub.conf, display a menu over
> > the xencons, kexec the appropriate kernel.
>
> Linux really seems like a very heavy hammer for something like this.
> Even just thinking from a resource perspective, why boot up a whole
> kernel to do nothing more than read an fs and mount another kernel.
I don't buy the resource argument: it takes only a couple of seconds to
boot a xenU kernel to user space, and you're about to be booting another
kernel anyhow.
> Especially as you start thinking about things like modular fs's, etc,
> it's going to be much less clean of a solution and be a significant
> slowdown on your guest boot time.
A few seconds slow down -- nothing compared to what a BIOS normally
adds.
I don't see why the filesystems would particularly need to be modular,
though you might do so for convenience.
> And then, it's yet another kernel to keep updated, etc.
I don't see any reason to keep it up to date. Its running in a protected
environemnt and doesn't have any extra access that the kernel about to
be booted is going to get.
I think this approach will work well.
We already booy all of our *physical* machines using a CDROM containing
a Linux bootloader -- see xenoboot:
http://www.cl.cam.ac.uk/Research/SRG/netos/xeno/xenoboot/
Ian
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel
|
Home