WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Error: Device 2049 (vbd) could not be connected. Backend dev

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Error: Device 2049 (vbd) could not be connected. Backend device not found.
From: Joe Warren-Meeks <joe.warren-meeks@xxxxxxxxxxxxx>
Date: Wed, 26 Apr 2006 13:26:09 +0100
Delivery-date: Wed, 26 Apr 2006 05:26:53 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

Hey guys,

I've installed xen 3 and xen-tools on my ubuntu server and all seems well, until I try to start a client domain. (running on Linux xenserver 2.6.12.6-xen #1 SMP Wed Feb 1 21:23:17 UTC 2006 i686 GNU/ Linux)

I get the error: "Error: Device 2049 (vbd) could not be connected. Backend device not found.
"

Now, I tracked it initially to being that Domain0 doesn't have /dev/ sda*, which the client domains are using as root, so I used MAKEDEV to create the device nodes and had some success.

However, if I halt/reboot/shutdown the client domain, the error returns if I try to restart it, even though the devices are in Domain0's /dev/

Also, if I reboot the whole machine, sometimes the client domains will start and some times they won't. Again, if they do, I can't restart them without that error occurring.

I get a lot of errors like the following in /var/log/xen-hotplug.log

"
xenstore-read: xenstore-read: couldn't read path backend/vbd/1/2049/node
couldn't read path backend/vbd/1/2050/node
xenstore-read: couldn't read path backend/vbd/2/2049/node
xenstore-read: couldn't read path backend/vbd/2/2050/node
xenstore-read: couldn't read path backend/vbd/3/2050/node
"

My /etc/xen/server.cfg:

kernel = "/boot/xen-linux-2.6.12.6-xen"
memory = 128
name   = "squid1"
root   = "/dev/sda1 ro"
vif    = [""]
disk = [ 'file:/xen/domains/squid1/disk.img,sda1,w', 'file:/xen/ domains/squid1/swap.img,sda2,w' ]
dhcp = "dhcp"

Any ideas chaps?

Thanks!

 -- joe.

Joe Warren-Meeks                       T: +44 (0) 208 962 0007
Aggregator Limited                     M: +44 (0) 7789 176078
Unit 62/63 Pall Mall Deposit           E: joe.warren-meeks@xxxxxxxxxxxxx
124-128 Barlby Road, London W10 6BL
PGP Fingerprint: 361F 78D0 56F5 8D7F 2639  947D 71E2 8811 F825 64CC



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