WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] VFS: Unable to mount root fs on unknown-block(0,0)

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] VFS: Unable to mount root fs on unknown-block(0,0)
From: Bo <barnesno@xxxxxxxxx>
Date: Sat, 16 Dec 2006 15:35:56 -0500
Delivery-date: Sat, 16 Dec 2006 18:58:14 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.8 (X11/20060911)
I have compiled a kernel from the sources in xen-3.0.3_0-src.tgz.  I
generated an initrd via mkinitrd /boot/initrd-2.6.16.29-xen.img
2.6.16.29-xen (after doing a depmod) 

I did a make world/make install from the source directory, per
instructions in the README.  I extracted the files from the initrd file
to see what the init script looked like.  It has a line inserting the
ext3.ko module.

The last few lines from the output:

(XEN) Xen trace buffers: disabled
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
input to Xen).
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
 (XEN) Domain 0 crashed: 'noreboot' set - not rebooting.

The menu.lst (trimmed)

serial --unit=0 --speed=19200 --word=8 --parity=no --stop=1
terminal --timeout=10 serial console
title Fedora Core (2.6.16-29_FC4xen0)
        root (hd1,1)
        kernel /boot/xen.gz dom0_mem=262144 noreboot com1=19200n81
        module /boot/vmlinuz-2.6.16-xen ro root=/dev/hdb2 quiet
console=tty0 console=ttyS0,19200n8
        module /boot/initrd-2.6.16.29-xen.img

This seems to conform to everything I've ever been able to google on
making Domain 0 boot. Here is the section that boots normally.
title Fedora Core (2.6.11-1.1369_FC4)
        root (hd1,1)
        kernel /boot/vmlinuz-2.6.11-1.1369_FC4 ro root=LABEL=/12 rhgb quiet
        initrd /boot/initrd-2.6.11-1.1369_FC4.img

Note that I had to replace the root=LABEL=/12 with root=/dev/hdb2
because it complained about not finding that label.

There are no errors during compilation and no errors in the boot
messages prior to the failure.

The first few lines of the boot messages:

  Booting 'Fedora Core (2.6.16-29_FC4xen0)'

root (hd1,1)
 Filesystem type is ext2fs, partition type 0x83
kernel /boot/xen.gz dom0_mem=262144 noreboot com1=19200n81
   [Multiboot-elf, <0x100000:0x815d8:0x48a28>, shtab=0x1ca078,
entry=0x100000]
module /boot/vmlinuz-2.6.16-xen ro root=/dev/hdb2 quiet console=tty0
console=tt
yS0,19200n8
   [Multiboot-module @ 0x1cb000, 0x2d703c bytes]
module /boot/initrd.img
   [Multiboot-module @ 0x4a3000, 0x282200 bytes]

Any suggestions as what to try next would be appreciated.  I've googled
and read all I could find on FC and xen to no avail.

Thanks,
Bo



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