Re: [Xen-devel] pygrub: further improve grub2 support

[Boris Derzhavets <bderzhavets@xxxxxxxxx>]

I would guess HVM image is bkoken on for Ubuntu 10.04 Server Beta
Attempt to load PV via profile :-

memory = 2048
name = "Ubuntu10.04"
kernel="/home/boris/lynx/vmlinuz-2.6.32-16-server"
ramdisk="/home/boris/lynx/initrd.img-2.6.32-16-server"
vcpus = 2
vif = [ 'bridge=eth0' ]
disk = [ 'phy:/dev/sda8,xvda,w']
extra="root=/dev/sda1 ro console=hvc0"

xm create -c Lynx.cfg

[    0.149124] XENBUS: Device with no driver: device/vbd/51712
[    0.149129] XENBUS: Device with no driver: device/vif/0
[    0.149135] XENBUS: Device with no driver: device/console/0
[    0.149149]   Magic number: 1:252:3141
[    0.149160] /build/buildd/linux-2.6.32/drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    0.149167] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[    0.149172] EDD information not available.
[    0.149254] Freeing unused kernel memory: 800k freed
[    0.149491] Write protecting the kernel read-only data: 7936k
Loading, please wait...
[    0.175675] udev: starting version 151
Begin: Loading essential drivers... ...
Done.
Begin: Running /scripts/init-premount ...
Done.
Begin: Mounting root file system... ...
Begin: Running /scripts/local-top ...
Done.
[    0.241186] blkfront: xvda: barriers enabled
[    0.241453]  xvda: xvda1 xvda2 < xvda5 >
Gave up waiting for root device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
   - Check root= (did the system wait for the right device?)
   - Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/sda1 does not exist. Dropping to a shell!


BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu9) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs)


/dev/sda1 does show up as root FS for HVM has been built.

Boris.

--- On Fri, 3/26/10, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:

From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Subject: Re: [Xen-devel] pygrub: further improve grub2 support
To: "Ian Campbell" <Ian.Campbell@xxxxxxxxxx>
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Friday, March 26, 2010, 6:57 AM

I've tried to PV domU with ready HVM domU via profile:-

memory = 2048
name = "UbuntuLynx"
bootloader="/usr/local/bin/pygrub"
vcpus = 2
vif = [ 'bridge=eth0' ]
disk = [ 'phy:/dev/sda8,xvda,w']
vfb= ['type=vnc,vncunused=1']

> Do you know how grub2 tries to interpret this, perhaps using a
> device.map type file in /boot/grub? Or perhaps it is simply a bug in
> 10.04 beta?

In meantime i don't know. I will take a look at device.map a bit latter.
But , it doesn't look to myself  as "beta"  issue

Boris.

--- On Fri, 3/26/10, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:

From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Subject: Re: [Xen-devel] pygrub: further improve grub2 support
To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Friday, March 26, 2010, 6:49 AM

On Fri, 2010-03-26 at 10:41 +0000, Boris Derzhavets wrote:
> In Ubuntu 10.04 beta grub entry root looks like :
>
>   set root='(/dev/sda,1)'  vs  set  root=(hd0,1) in 9.10

So grub in Ubuntu 10.04 uses _Linux_ device naming in the bootloader
configuration? That seems like an awfully big break with tradition.

Do you know how grub2 tries to interpret this, perhaps using a
device.map type file in /boot/grub? Or perhaps it is simply a bug in
10.04 beta?

sda isn't really a valid name for a modern PV domU kernel anyway. It
should be xvda. Looks like you need to do some additional tailoring to
convert your HVM Ubuntu domain into a PV one.

Ian.

-----Inline Attachment Follows-----

_______________________________________________
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