[Xen-devel] Re: [PATCH 3/3] domUloader

To:	Xen development list <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	[Xen-devel] Re: [PATCH 3/3] domUloader
From:	Kurt Garloff <garloff@xxxxxxx>
Date:	Tue, 17 Jan 2006 00:44:18 +0100
Delivery-date:	Mon, 16 Jan 2006 23:52:35 +0000
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
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>
Mail-followup-to:	Kurt Garloff <garloff@xxxxxxx>, Xen development list <xen-devel@xxxxxxxxxxxxxxxxxxx>
Organization:	SUSE/Novell
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent:	Mutt/1.5.9i

Hi,

On Mon, Jan 16, 2006 at 11:26:09PM +0000, Kurt Garloff wrote:
> (3) The domUloader.py script.

The domUloader.py program documents itself best.

Just omit kernel and ramdisk from a domU config file, and put
bootentry = [dev:]kernel[,initrd]
bootloader = /path/to/domUloader.py
in it :-)

Works both with and without dev:, and is tested including the
reboot case.

Cheers,
-- 
Kurt Garloff, Head Architect, Director SUSE Labs (act.), Novell Inc.

domUloader.py
Description: Text document

pgpgmRIrQTMwT.pgp
Description: PGP signature

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

WARNING - OLD ARCHIVES

xen-devel

[Xen-devel] Re: [PATCH 3/3] domUloader