RE: [Xen-users] Device 2049 (vbd) could not be connected. Backenddevice not found.

["Satoshi Uchida" <s-uchida@xxxxxxxxxxxxx>]

>
> My guess is that the problem is not in Xen itself, but in some
configuration issue
> (I'm also wondering if the udev and hotplug packages included in
SLES9SP2 are 
> a bit dated). Take into account that I have no problem creating a
domain with multiple
> images using the same Xen 3.0.0 on a different machine (with Ubuntu
Breezy Badger
> , which is relatively recent).
>

Hi.

Ok,  I miss my comprehension.

>Dec 14 15:45:00 tp-c120 logger: /etc/xen/scripts/block:
>                                    Writing backend/vbd/1/2050/node
/dev/loop1 to xenstore.
>Dec 14 15:45:00 tp-c120 logger: /etc/xen/scripts/block: losetup
>                                   /dev/loop1
/vm/vm_images/vosg/GK/osg-gk-base.img failed

But,  I see that missing to allocate image file into loop back device.
your log shaw VBD 2050 ( /vm/vm_images/vosg/GK/swap1.img ) is allocated
loop1 and,
VBD 2049 ( file:/vm/vm_images/vosg/GK/osg-gk-base.img ) is trying to
allocate loop1.

Thank you.

Satoshi UCHIDA

smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users