[Xen-users] where is my root?

[Hans de Bruin <jmdebruin@xxxxxxxxx>]

The pvops kernel has some trouble finding my root:

grub'2'.cfg:

menuentry "GNU/Linux, with Linux 2.6.31.13" --class gnu-linux --class 
gnu --class os {
        set gfxpayload=keep
        insmod raid
        insmod mdraid
        insmod ext2
        set root='(md0)'
        search --no-floppy --fs-uuid --set 
5d272f28-2087-490b-8de2-c7d12beaff69
        echo    Loading Linux 2.6.31.13 ...
        linux   /vmlinuz-2.6.31.13 root=/dev/md2 ro console=tty0 
console=ttyS0,38400,8n1
}
...
menuentry "Xen 4.0.0. linux-2.6.31.13 pvops" {
        insmod raid
        insmod mdraid
        insmod ext2
        set root='(md0)'
        search --no-floppy --fs-uuid --set 
5d272f28-2087-490b-8de2-c7d12beaff69
        echo    Loading Linux 2.6.33 ...
        multiboot /xen-4.0.1-rc1-pre.gz dom0_mem=512M  loglvl=all 
guest_loglvl=all com1=38400,8n1,0x3f8,4 console=com1 iommu=0
        module /vmlinuz-2.6.31.13 root=/dev/md2 ro console=hvc0 
earlyprintk=xen nomodeset
}


pvops kernel by itself:

[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 2.6.31.13 (hans@bootes) (gcc version 4.4.3 
(GCC) ) #3 SMP Sat May 22 13:46:23 CEST 2010
[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-2.6.31.13 root=/dev/md2 
ro console=tty0 console=ttyS0,38400,8n1
....
[    8.177481] VFS: Mounted root (ext4 filesystem) readonly on device 9:2.
[    8.197548] Freeing unused kernel memory: 508k freed
[    8.212901] Write protecting the kernel read-only data: 8016k
[    8.283642] Warning: unable to open an initial console.
[   11.637889] scsi 2:0:0:0: Direct-Access              USB DISK 2.0 
 PMAP PQ: 0 ANSI: 0 CCS
[   11.664631] sd 2:0:0:0: Attached scsi generic sg2 type 0
[   11.681100] sd 2:0:0:0: [sdc] 15882240 512-byte logical blocks: (8.13 
GB/7.57 GiB)
[   11.705456] sd 2:0:0:0: [sdc] Write Protect is off
[   11.719981] sd 2:0:0:0: [sdc] Assuming drive cache: write through
[   11.741948] sd 2:0:0:0: [sdc] Assuming drive cache: write through
[   11.760338]  sdc: sdc1
[   11.770449] sd 2:0:0:0: [sdc] Assuming drive cache: write through
[   11.788846] sd 2:0:0:0: [sdc] Attached SCSI removable disk
[   13.131600] md: stopping all md devices.
[   13.143484] md: md1 switched to read-only mode.
[   13.157185] md: md2 switched to read-only mode.
[   13.170878] md: md0 switched to read-only mode.
[   14.675056] sd 0:0:1:0: [sdb] Synchronizing SCSI cache
[   14.690799] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[   14.755088] e1000 0000:04:07.0: PCI INT A disabled
[   14.769676] e1000 0000:04:06.0: PCI INT A disabled
[   14.784256] e1000 0000:04:04.0: PCI INT A disabled
[   14.799257] Restarting system.
[   14.808522] machine restart


So there is a mounted rootfs on /dev/md2 but apparently no console.

pvops on top of xen:

[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 2.6.31.13 (hans@bootes) (gcc version 4.4.3 
(GCC) ) #3 SMP Sat May 22 13:46:23 CEST 2010
[    0.000000] Command line: ro console=hvc0 earlyprintk=xen nomodeset

here root=/dev/md2 has disappeared!

...
[    3.289417] md: ... autorun DONE.
[    3.289830] VFS: Cannot open root device "<NULL>" or unknown-block(0,0)
[    3.289856] Please append a correct "root=" boot option; here are the 
available partitions:
[    3.289903] 0800       488386584 sda driver: sd
[    3.289935]   0801           72261 sda1
[    3.289962]   0802          530145 sda2
[    3.289989]   0803          530145 sda3
[    3.290021]   0804       487251450 sda4
[    3.290048] 0810       488386584 sdb driver: sd
[    3.290077]   0811           72261 sdb1
[    3.290084]   0812          530145 sdb2
[    3.290084]   0813          530145 sdb3
[    3.290084]   0814       487251450 sdb4
[    3.290084] 0900           72192 md0 (driver?)
[    3.290084] 0902          530048 md2 (driver?)
[    3.290084] 0901          530048 md1 (driver?)
[    3.290084] Kernel panic - not syncing: VFS: Unable to mount root fs 
on unknown-block(0,0)
[    3.290084] Pid: 1, comm: swapper Not tainted 2.6.31.13 #3
[    3.290084] Call Trace:
[    3.290084]  [<ffffffff81544197>] panic+0x75/0x130
[    3.290084]  [<ffffffff818daa67>] mount_block_root+0x257/0x26e
[    3.290084]  [<ffffffff818daad4>] mount_root+0x56/0x5a
[    3.290084]  [<ffffffff818dac48>] prepare_namespace+0x170/0x19d
[    3.290084]  [<ffffffff818d9f40>] kernel_init+0x1b5/0x1c5
[    3.290084]  [<ffffffff81014daa>] child_rip+0xa/0x20
[    3.290084]  [<ffffffff81013f67>] ? int_ret_from_sys_call+0x7/0x1b
[    3.290084]  [<ffffffff8101471d>] ? retint_restore_args+0x5/0x6
[    3.290084]  [<ffffffff81014da0>] ? child_rip+0x0/0x20

which ends in a disaster.

I have got to questions. In case of the pvops only boot is the an error 
in the grub.cfg file do I need to change the console?  In case of the 
xen-pvops boot where has the root=/dev/md2 gone?


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