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

[Ricardo Ariel Gorosito]

I was installed a rawhide domain using xenguest-install.py .
Installation was successful, but when I try to start the domain, it die
with a kernel panic (guest)
The full output from the console in guest domain is in the attachment.

the following lines make me think that initrd is not generated correctly
during the installation of guest domain:

XENBUS: Device with no driver: device/vbd/51712
...
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'

Any hint?



Going to boot Fedora Core (2.6.17-1.2548.fc6xen)
  kernel: /vmlinuz-2.6.17-1.2548.fc6xen
  initrd: /initrd-2.6.17-1.2548.fc6xen.img
Started domain xuxa
Linux version 2.6.17-1.2548.fc6xen (brewbuilder(a)hs20-bc2-4.build.redhat.com) (gcc version
4.1.1 20060802 (Red Hat 4.1.1-14)) #1 SMP Thu Aug 10 23:10:42 EDT 2006
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000010800000 (usable)
0MB HIGHMEM available.
264MB LOWMEM available.
Using x86 segment limits to approximate NX protection
ACPI in unprivileged domain disabled
Built 1 zonelists.  Total pages: 67584
Kernel command line:  ro root=/dev/VolGroup00/LogVol00
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
CPU 0 irqstacks, hard=c0728000 soft=c0708000
PID hash table entries: 2048 (order: 11, 8192 bytes)
Xen reported: 1908.934 MHz processor.
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Software IO TLB disabled
vmalloc area: d1000000-f4ffe000, maxmem 2d7fe000
Memory: 250368k/270336k available (2043k kernel code, 11520k reserved, 850k data, 176k
init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 4775.27 BogoMIPS (lpj=9550546)
Security Framework v1.0.0 initialized
SELinux:  Initializing.
SELinux:  Starting in permissive mode
selinux_register_security:  Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 512
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 12k freed
Brought up 1 CPUs
checking if image is initramfs... it is
Freeing initrd memory: 4377k freed
Grant table initialized
NET: Registered protocol family 16
Brought up 1 CPUs
PCI: setting up Xen PCI frontend stub
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
xen_mem: Initialising balloon driver.
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: System does not support PCI
PCI: System does not support PCI
NetLabel: Initializing
NetLabel:  domain hash size = 128
NetLabel:  protocols = UNLABELED CIPSOv4
NetLabel:  unlabeled traffic allowed by default
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 6, 327680 bytes)
TCP bind hash table entries: 8192 (order: 5, 163840 bytes)
TCP: Hash tables configured (established 16384 bind 8192)
TCP reno registered
IA-32 Microcode Update Driver: v1.14-xen <tigran(a)veritas.com&gt;
audit: initializing netlink socket (disabled)
audit(1155423080.036:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
SELinux:  Registering netfilter hooks
Initializing Cryptographic API
ksign: Installing public key data
Loading keyring
- Added public key 9E1464B61C97F3AB
- User ID: Red Hat, Inc. (Kernel Module GPG key)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
rtc: IRQ 8 is not free.
Non-volatile memory driver v1.2
Linux agpgart interface v0.101 (c) Dave Jones
RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
Xen virtual console successfully installed as tty1
Event-channel device installed.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
ide-floppy driver 0.99.newide
usbcore: registered new driver libusual
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
powernow-k8: Processor cpuid 6a0 not supported
Using IPI No-Shortcut mode
XENBUS: Device with no driver: device/vbd/51712
XENBUS: Device with no driver: device/vif/0
Freeing unused kernel memory: 176k freed
Red Hat nash version 5.1.2 starting
Mounting proc filesystem
Mounting sysfs filesystem
Creating /dev
Creating initial device nodes
Setting up hotplug.
Creating block device nodes.
Loading xenblk.ko module
Loading jbd.ko module
Loading ext3.ko module
Loading dm-mod.ko module
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel(a)redhat.com
Loading dm-mirror.ko module
Loading dm-zero.ko module
Loading dm-snapshot.ko module
Making device-mapper control node
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!

[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

[Ricardo Ariel Gorosito]

Hi Chris, I has no luck with 2558. Now I can't install. Last 3 lines 
from xenguest-install.py console:

XENBUS: Device with no driver: device/vbd/51712
XENBUS: Device with no driver: device/vif/0
Freeing unused kernel memory: 172k freed

guest state is 'blocked'

R.-

Chris Lalancette escribió:
>  ...
>  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
>

[Mark McLoughlin]

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.

[Ricardo Ariel Gorosito]

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.
>
>
>

[Chris Lalancette]

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(a)redhat.com
>  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

[Ricardo Ariel Gorosito]

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(a)redhat.com
> > 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
>