This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH] Guest boot loader support

To: Jeremy Katz <katzj@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Guest boot loader support
From: aq <aquynh@xxxxxxxxx>
Date: Tue, 26 Apr 2005 18:32:23 +0900
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 26 Apr 2005 09:32:06 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=sjKR2yVkvUiRU2PM5O+cdL/nVL5IXhNPheveorNlwS7c3dcw5upM/V5sq/eNPz3sOU3O+1/No999zkOHfwry4rtyBQa6uIY2JvTUKqU0x0BQ94Xyj41/hUMYhvlcCdzae87bwonOjpaRi2HFxpDk+dfe2xDF3dFyS1V1cfN0ZPA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1114469427.4336.42.camel@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1114469427.4336.42.camel@xxxxxxxxxxxxxx>
Reply-to: aq <aquynh@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 4/26/05, Jeremy Katz <katzj@xxxxxxxxxx> wrote:
> Attached is an updated version of the patch to add boot loader support
> for guest domains.
> 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
> 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.
> 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
> Signed-off-by: Jeremy Katz <katzj@xxxxxxxxxx>
> Jeremy
> [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.


Xen-devel mailing list