[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-API] grub/cmdline

On Mon, Nov 20, 2006 at 04:46:42PM -0700, Jim Fehlig wrote:

> Ewan Mellor wrote:
> [snip]
> >>What about support for other boot loaders?  SLES for example uses 
> >>domUloader.  How would this be specified?  Although moving forward, 
> >>particularly with the work John has been doing, I'm thinking we should 
> >>just be using pygrub.  Not sure why we  were using domUloader anyway and 
> >>the person with some context behind this decision is not available ATM.
> >>    
> >
> >What would that take?  As I understand it, domUloader has the same
> >semantics as pygrub, in that the guest kernel's permanent home is the
> >guest filesystem, and it is booted non-HVM.  Is the difference that 
> >domUloader
> >doesn't parse the grub configuration?  What does it do instead?
> >  
> Looks like your latest proposal will support domUloader, i.e.

Yes, that's another reason that I came around to John's way of thinking ;-)

> vm.pv.bootloader
> vm.pv.entry
> vm.pv.kernel
> vm.pv.ramdisk
> vm.pv.args
> domUloader does get kernel/ramdisk from guest filesystem but does not 
> parse the grub configuration, instead relying on input parameters.  E.g. 
> a legacy config file entry for domUloader might be
> bootloader = '/usr/lib/xen/boot/domUloader.py'
> bootentry = 'hda2:/boot/vmlinuz-xen,/boot/initrd-xen'
> The bootloader params could be stuffed in vm.pv.entry or sprayed across 
> entry, .kernel and .ramdisk.

Yes, you'd just use kernel = "hda2:/boot/vmlinuz-xen",
ramdisk="/boot/initrd-xen" in this example, I think.  That seems good to me.


xen-api mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.