Error Device 2049 Vbd
To: xen-users@xxxxxxxxxxxxxxxxxxx Subject: [Xen-users] Error: Device 2049 (vbd) could not be connected. Backend device not found. From: Joe Warren-Meeks 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: List-id: Xen user discussion List-post: List-subscribe: , List-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
xen-users@xxxxxxxxxxxxxxxxxxx Subject: [Xen-users] Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. From: "J J" Date: Wed, 26 Jul 2006 19:39:12 -0400 Bcc: Delivery-date: Wed, 26 Jul 2006 16:39:57 -0700 Envelope-to: www-data@xxxxxxxxxxxxxxxxxx List-help: List-id: http://old-list-archives.xenproject.org/xen-users/2006-04/msg00968.html Xen user discussion List-post: List-subscribe: , List-unsubscribe: , Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx I am getting this error when doing an xm create. [root@xen scripts]# udevmonitor & [root@xen scripts]# xm create -c jj Using config http://old-list-archives.xenproject.org/xen-users/2006-07/msg00728.html file "/etc/xen/jj". UEVENT[1153956764.945952] add@/devices/xen-backend/vbd-13-2049 UEVENT[1153956775.318771] remove@/devices/xen-backend/vbd-13-2049 Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. Any help would be appreciated. JJ ------------------- [root@xen scripts]# cat /etc/xen/jj kernel ="/boot/vmlinuz-2.6.17-1.2157_FC5xenU" memory = 64 name = "jj" disk = ['file:/jj.img,sda1,w'] root = "/dev/sda1" extra = "ro selinux=0 3" [root@xen scripts]# uname -a Linux xen.pogg.net 2.6.17-1.2157_FC5xen0 #1 SMP Wed Jul 12 00:28:36 EDT 2006 i686 i686 i386 GNU/Linux [root@xen scripts]# cat /etc/redhat-release Fedora Core release 5 (Bordeaux) [root@xen scripts]# udevinfo -Vudevinfo, version 084 Xen version 3.0.2 Release 3.FC5 kernel-xen0 Version: 2.6.17 Release: 1.2139_FC5 kernel-xenU Version: 2.6.17 Release: 1.2157_FC5 _________________________________________________________________ Is your PC infected? Get a FREE onl
Threaded andy at strugglers Nov28,2005,5:19PM Post #1 of 3 (247 views) Permalink Error: Device 2049 (vbd) could not http://www.gossamer-threads.com/lists/xen/users/5613 be connected. Backend device not found. Hi folks, Trying out -unstable, have dom0 booted and the network-bridge script working, but I'm having problems starting the first domain: $ sudo xm create -c /etc/xen/irc.sxp Using config file "/etc/xen/irc.sxp". Error: Device 2049 (vbd) could not be connected. Backend device not found. /etc/xen/irc.sxp contains: name = "irc" kernel = "/boot/vmlinuz-2.6.12.6-xenU_dnuk_1" root = "/dev/sda1 error device ro" memory = 128 disk = [ 'phy:vg00/domu_irc_root,sda1,w', 'phy:vg00/domu_irc_swap,sda2,w' ] nics = 1 Relevant items in xend.log, plus dom0 kernel config can be found here: http://strugglers.net/~andy/tmp/xen/ There's nothing in /var/log/messages or /var/log/xend-debug.log. This is on: xen_changeset : Sat Nov 26 01:21:55 2005 +0000 8054:b9181b1c576f Any ideas where the problem may lie? Cheers, Andy Attachments: signature.asc (0.18 KB) joe.warren-meeks at aggregator Apr27,2006,7:04AM error device 2049 Post #2 of 3 (245 views) Permalink Re: Error: Device 2049 (vbd) could not be connected. Backend device not found. [In reply to] On 27 Apr 2006, at 14:49, Nicola Bianchi wrote: > Joe Warren-Meeks wrote: >> Bit of a follow-up. If I try to start the DomU, it initally errors >> as so: >> root [at] xenserve:/etc/xen# xm create -c squid1.cfg >> Using config file "squid1.cfg". >> Error: Device 2049 (vbd) could not be connected. Backend device >> not found. > > have you start xend daemon? > # xend start Yes, it was running. It seems to be some interaction between the /dev/sda stuff and the scsi module. I just managed to get DomU to boot once by doing a modload sd_mod and then un-pausing a stuck boot. But doing it from fresh fails. My xen server is an ide machine (it is a development environment) Any more pointers? -- 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 [at] ag