Re: XENBUS: Device with no driver: device/vbd/51712

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Yes, I see this. Now I have a fc6test2 (kernel 1.2517) booted correctly as domU (xenguest-install from a mirror of fc6t2). kernels 1.2564 and 1.2558 can't attach console. I'm using 1.2564 as dom0
Ricardo.-

Chris Lalancette escribió:
Ricardo Ariel Gorosito wrote:
I Mark,
With rawhide's kernel (2.6.17-1.2564.fc6xen), xenguest-install stop after kernel is loaded. Looking at .../images/xen/initrd.img , xenblk and xennet are inside.
Can it be caused for the 'blkfront bug' which quoted Christ ?
Thanks,
Ricardo.-

Mark McLoughlin escribió:

On Sat, 2006-08-12 at 20:40 -0300, Ricardo Ariel Gorosito wrote:

XENBUS: Device with no driver: device/vbd/51712


You can ignore this, it's not a problem. It just means that when the
kernel finished loading, no driver had yet been loaded for the virtual
block device. But that's fine, the driver is in the initrd and will be
loaded later.

Cheers,
Mark.




--
Fedora-xen mailing list
Fedora-xen@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-xen


Ricardo,
I am also seeing this. I think somewhere in the kernel boot messages you should see something like:

WARNING: Failed to register Xen virtual console driver as 'tty1'

Basically, the domU isn't crashed, it just isn't properly connected to the console, so you can't see anything. I'm not sure what the problem is; we are trying to track it down internally. I'll let you know when we find something.

Chris Lalancette


--
Fedora-xen mailing list
Fedora-xen@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-xen

[Index of Archives]     [Fedora General]     [Fedora Music]     [Linux Kernel]     [Fedora Desktop]     [Fedora Directory]     [PAM]     [Big List of Linux Books]     [Gimp]     [Yosemite News]

  Powered by Linux