|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] [PATCH] [XM] Enable a bootloader when using XM via Xen-A
> John Levon <levon@xxxxxxxxxxxxxxxxx>
> Sent by: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>
> 07/29/2008 10:45 PM
>
> To
>
> Stefan Berger/Watson/IBM@IBMUS
>
> cc
>
> xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
>
> Subject
>
> Re: [Xen-devel] [PATCH] [XM] Enable a bootloader when using XM via
Xen-API
>
> On Tue, Jul 29, 2008 at 10:37:44PM -0400, Stefan Berger wrote:
>
> > This enables the usage of a bootloader, i.e., pygrub, when starting
a
> > domain using xm in Xen-API mode.
>
> It's supposed to default to using pygrub if no kernel is specified,
is
> this still true after your change?
>
> regards
> john
I don't think it actually worked correctly before
with xm.
Using a vm config file with the following entries
and the domU kernel as the first title in grub.conf
name = "test"
memory = 512
disk = ['file:/temp/fc8-i386.img,sda,w']
bootloader = "/usr/bin/pygrub"
I tested using 'xm create' in Xen-API mode by enabling
and disabling the 'bootloader' line and got this here:
- without the patch and the bootloader line
'on' : 'Internal Error: Had a bootloader specified, but no disks
are bootable'
- without the patch and the bootloader line
'off': 'Internal Error: Had a bootloader specified, but no disks
are bootable'
- with the patch and the bootloader
line 'on' : * boots domU *
- with the patch and the bootloader
line 'off': * boots domU *
I think the patch solves the problem with the bootloader.
Is it possible to have pygrub display its GUI while
doing 'xm create'? How?
Stefan
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|