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

RE: [Xen-devel] [RFC] Bootloader configuration


  • To: "John Levon" <levon@xxxxxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
  • Date: Mon, 27 Feb 2006 22:14:12 -0000
  • Delivery-date: Mon, 27 Feb 2006 22:14:41 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcY7vbkEom9ESlTbR3+jUPG02ntHvAAK82wg
  • Thread-topic: [Xen-devel] [RFC] Bootloader configuration

> Bootloader interface
> --------------------
> 
> The Xen python code parses the 'kernel' value into 'method' 
> and 'params', then searches for a bootloader handler matching 
> 'method' as follows:
> 
>      /usr/lib/xen/boot/bootload-<method>
>      <auxbinpath>/bootload-<method>
>      /etc/xen/scripts/bootload-<method>
> 
> When found, the bootloader is invoked as follows:
> 
>      -b <bootdisk> -k <kernel's method-param> [-r <ramdisk's 
> method-param>] \
>         -d <disk1> [ -d <disk2> ... ]

In principle, I think invoking a binary to run the boot loader is
probably a good thing. It's quite possible we'll want to drop in new
guest-specific boot loader binaries. 

Ian

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

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