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

[Brian Lavender <brian@xxxxxxxxxxxxx>]

On Thu, 2005-12-15 at 11:56 +0900, Satoshi Uchida wrote:
> >
> > 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.
> 

When the domain fails, try this.

for i in /dev/loop*
do
losetup $i
done

If you don't have any VM's running, and you see a loopback device
connected, it could be that somewhere in Xen (I believe xenstored) is
not releasing the losetup connection to the image file. I have seen some
problems with this in testing. You can manually delete the connection
using

losetup -d /dev/loop<number that is connected to your image file>

brian
-- 
Brian Lavender <brian@xxxxxxxxxxxxx>


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