From mboxrd@z Thu Jan 1 00:00:00 1970 From: aq Subject: Re: [PATCH] Guest boot loader support Date: Tue, 26 Apr 2005 18:32:23 +0900 Message-ID: <9cde8bff050426023247aa475b@mail.gmail.com> References: <1114469427.4336.42.camel@bree.local.net> Reply-To: aq Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <1114469427.4336.42.camel@bree.local.net> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeremy Katz Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 4/26/05, Jeremy Katz wrote: > Attached is an updated version of the patch to add boot loader support > for guest domains. >=20 > Changes from the initial set of patches: > * Per Ian's request, adds an option to specify booting a specific kernel > from the host domain (you can specify it either with the title of the > boot loader config entry or with the grub 0-based index) > * Reduces some of the code duplication for finding out what the virtual > disk to boot off of is > * Improved error handling to use the standard Xen logging and error > facilities >=20 > At this point, I think that we handle the use cases where a user just > wants to have everything specified from within the guest domain, > creating a domain with xm create and wanting to be able to interactively > select a kernel and asking for a specific entry from the grub.conf to be > booted when creating a domain. >=20 > Future things (which I think are fine to do after the initial pass is > committed) include > * Reworking to use the planned new console infrastructure [1] > * Handling whole disks > * More filesystem support -- the code is generic and has all the hooks, > I just haven't delved deep enough into any of the other fs libraries > * Further improvements for the menu interface >=20 > Signed-off-by: Jeremy Katz >=20 > Jeremy >=20 > [1] And I foolishly told Ian I'd start a discussion about this last week > and still haven't. Hopefully tonight. Jeremy, I tried it out with the latest xen-unstable got from the homepage and patch with xen-booloader.patch. There are few "hunk". What xen-unstable version are you using? By the way, did you forget __init__.py in pygrub/src/ ? pygrub is a python package, and looks like we need it. At the moment compilation spit out an error "... __init__.py not found...". Quick fix: touch tools/pygrub/src/__init__.py then no more complain. regards, aq