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 ** Attachment added: "dmesg-domU.txt" http://launchpadlibrarian.net/13303907/dmesg-domU.txt -- xen guest system cannot detect root filesystem https://bugs.launchpad.net/bugs/214821 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
