xen guest system cannot detect root filesystem

[kochab]

I'm running Hardy, I've installed ubuntu-xen-server, and I've installed the last xen-tools from source (with the xen-tools from the repository nothing changes).

xen-tools runs fine with these options in xen-tools.conf:
lvm = vg00
install-method = debootstrap
size = 20Gb # Disk image size.
memory = 500Mb # Memory size
swap = 500Mb # Swap size
# noswap = 1 # Don't use swap at all for the new system.
fs = ext3 # use the EXT3 filesystem for the disk image.
dist = etch # Default distribution to install.
image = sparse # Specify sparse vs. full disk images.
gateway = 192.168.1.1
netmask = 255.255.255.0
broadcast = 192.168.1.255
passwd = 1
kernel = /boot/vmlinuz-`uname -r`
initrd = /boot/initrd.img-`uname -r`
arch=amd64
mirror = http://ftp.it.debian.org/debian/
ext3_options = noatime,nodiratime,errors=remount-ro
boot = 1
disk_device = sda

by running the command:
xen-create-image --hostname=test --ip=192.168.1.8

unfortunately the guest system cannot find the root filesystem, showing this error at boot:

Begin: Running /scripts/init-premount ...
Done.
Begin: Mounting root file system... ...
Begin: Running /scripts/local-top ...
Done.
Begin: Waiting for root file system... ...
Done.
        Check root= bootarg cat /proc/cmdline
        or missing modules, devices: cat /proc/modules ls /dev
  Reading all physical volumes. This may take a while...
ALERT! /dev/sda2 does not exist. Dropping to a shell!

BusyBox v1.1.3 (Debian 1:1.1.3-5ubuntu12) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs)

I've tried with no success to change the disk_device option to hda and also tried with the --ide option.
I attach the xen a.cfg file.

[Thiago Martins (martinx)]

I have the same problem here, but my setup have one little difference: in my domU cfg file, I have changed "file:" to "tap:aio:" because of bug https://bugs.launchpad.net/ubuntu/+source/xen-3.2/+bug/205450, I think...

And yes, I have the latest Hardy and ubuntu-xen-server in a fresh install.

I my running Debian Etch kernel 2.6.18.8-xen with xen-3.2, I can see this lines on domU boot messages:
...
xen-vbd: registered block device major 8
blkfront: sda: barriers enabled
 sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 sda9 >
...
But on Hardy I can't see this corresponding lines, see dmesg on attachment!
There is nothing about VBD, this is right anyway?!

PS.: In Debian I don't have loopback files, is LVM.

Command used to create domU (debo01):
xen-create-image --hostname=debo01 --ip=10.1.10.216 --dir=/home/xen --dist=etch

[Thiago Martins (martinx)]

Oops! I give the worng dmesg message!

Remove from your eyes the string "init=/bin/bash" from Command line in dmesg-domU.txt file, all the rest are the same.
I was trying to debug it! Sorry.

So I have tried the xen-create-image again with --ide option, but I got the same error:

....
[ 0.000000] Command line: root=/dev/hda2 ro 2 console=xvc0
....
[ 0.261431] Freeing unused kernel memory: 216k freed
Loading, please wait...
Begin: Loading essential drivers... ...
[ 0.571427] fuse init (API version 7.9)
[ 0.613397] thermal: Unknown symbol acpi_processor_set_thermal_limit
Done.
Begin: Running /scripts/init-premount ...
Done.
Begin: Mounting root file system... ...
Begin: Running /scripts/local-top ...
Done.
Begin: Waiting for root file system... ...
Done.
        Check root= bootarg cat /proc/cmdline
        or missing modules, devices: cat /proc/modules ls /dev
ALERT! /dev/hda2 does not exist. Dropping to a shell!

BusyBox v1.1.3 (Debian 1:1.1.3-5ubuntu12) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs)

[kochab (kochab-gmail)]

Ok,
I've fixed this issue by following the comment here:
https://bugs.launchpad.net/ubuntu/+source/xen-3.2/+bug/205450/comments/13

[Thiago Martins (martinx)]

> ...and network works!?

How? The eth0 interface of my Gutsy domU never receives a RX back...
pt-br: Como? A eth0 do meu domU nunca recebe um RX de volta... :)

I'm trying!! ^^

[kochab (kochab-gmail)]

no, I just fixed _this_ issue,
for fixing networking I had to use the gutsy xen kernel, see here:
https://bugs.launchpad.net/ubuntu/+source/xen-3.2/+bug/204010/comments/35

[Thiago Martins (martinx)]

Can be this bug closed?
Because it's not an issue to me anymore... :)

[Thiago Martins (martinx)]

kochab fix this little issue.

[crazee (crazee64)]

I'm also seeing this issue - also on Hardy with a fresh install of everything from the repos. Funny thing is i managed to create one domU fine and if I try to use those settings again (or any others) with xen-create-image for more domUs they fail to see a root file system. But the original one I did still works every time. I did a diff between the config files and all that changed was the ip address, disk size, ram size and host name.

I tried the fix suggested with no luck - was I correct to add the modules to /etc/initrams-tools/modules on dom0 && update-initramfs -u? Any other suggestions on how to solve this one?