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


[Xen-devel] Error: Device 768 (vbd) could not be connected. Backend devi

To: xen-users@xxxxxxxxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Error: Device 768 (vbd) could not be connected. Backend device not found.
From: "Jonathan M. McCune" <jonmccune@xxxxxxx>
Date: Wed, 19 Apr 2006 10:12:04 -0400
Delivery-date: Wed, 19 Apr 2006 07:13:59 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Debian Thunderbird 1.0.7 (X11/20051017)

I am getting this error when I try to start an HVM guest on an AMD Sahara system. The xen-unstable-hvm.hg revision 8724 works fine. I tried to upgrade to xen-unstable.hg revision 9668. I got 9668 to boot using 'yaird' to build the initrd for the -xen kernel. I can successfully start a paravirtualized guest, but I am now having trouble starting an HVM guest. The error message is:

Error: Device 768 (vbd) could not be connected. Backend device not found.

I googled a bit and other people have seen this error, but no solutions
seem to be presented.

Each attempt to start the domain puts a line like the following in
/var/log/xen-hotplug.log (The '8' here is the domain ID):

xenstore-read: couldn't read path backend/vbd/8/768/node

Here is my config file:

kernel = "/usr/lib/xen/boot/hvmloader"
memory = 260
name = "Sarge"
disk = [ 'file:/sarge/disk.img,ioemu:hda,w' ]
vif = [ 'type=ioemu, mac=00:14:bf:52:df:5e, bridge=xenbr0' ]
device_model = '/usr/lib/xen/bin/qemu-dm'
memmap = '/usr/lib/xen/boot/mem-map.sxp'

I have made sure that xend and xenstored are running, but I'm not sure what else to check (it works on the older Xen!). Any suggestions would be greatly appreciated.


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>