[Fedora-xen] XENBUS: Device with no driver: device/vbd/51712

[Chris Lalancette]

<snip>
> Scanning logical volumes
>   Reading all physical volumes.  This may take a while...
>   No volume groups found
> Activating logical volumes
>   Volume group "VolGroup00" not found
> Creating root device.
> Mounting root filesystem.
> mount: could not find filesystem '/dev/root'
> Setting up other filesystems.
> Setting up new root fs
> setuproot: moving /dev failed: No such file or directory
> no fstab.sys, mounting internal defaults
> setuproot: error mounting /proc: No such file or directory
> setuproot: error mounting /sys: No such file or directory
> Switching to new root and running init.
> unmounting old /dev
> unmounting old /proc
> unmounting old /proc/bus/usb
> ERROR unmounting old /proc/bus/usb: No such file or directory
> forcing unmount of /proc/bus/usb
> unmounting old /sys
> switchroot: mount failed: No such file or directory
> 4gb seg fixup, process nash-hotplug (pid 219), cs:ip 73:080addd1
> 4gb seg fixup, process nash-hotplug (pid 219), cs:ip 73:08159148
> 4gb seg fixup, process init (pid 1), cs:ip 73:080addd1
> 4gb seg fixup, process init (pid 1), cs:ip 73:08159148
> Kernel panic - not syncing: Attempted to kill init!
> 

Ricardo,
     Quoting from Rik van Riel:

"This is the "blkfront bug", where the initrd scripts try to
mount the root filesystem before the vbd disks are attached
to the guest domain. "

We believe this has now been fixed; an updated kernel with this should be pushed out pretty soon (you will want to look for a kernel-xen-2.6.17-1 with a revision number >= 2558).  Once that is released, it will probably be easiest just to run another install with xenguest-install.py, and report back the results.

Chris Lalancette