This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


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

To: Satoshi Uchida <s-uchida@xxxxxxxxxxxxx>
Subject: RE: [Xen-users] Device 2049 (vbd) could not be connected. Backenddevice not found.
From: Brian Lavender <brian@xxxxxxxxxxxxx>
Date: Wed, 14 Dec 2005 19:57:57 -0800
Cc: 'Borja Sotomayor' <borja@xxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 15 Dec 2005 04:00:31 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <iss.47225e1f.4d7e.43a0db55.ba305.cd@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <iss.47225e1f.4d7e.43a0db55.ba305.cd@xxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
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*
losetup $i

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

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

Brian Lavender <brian@xxxxxxxxxxxxx>

Xen-users mailing list