Fedora xen - Aug 2006 - XENBUS: Device with no driver: device/vbd/51712

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?

<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

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
>

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.

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

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

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