Error Device 2049 Vbd Could Not Be Connected
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/
[PermanentLink][Original] To: Subject: [Xen-users] Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. From: "Yacine Kheddache" Date: Tue, 20 Dec 2005 00:53:27 +0100 Delivery-date: Tue, 20 Dec 2005 12:02:54 +0000 Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx In-reply-to: List-help: List-id: Xen user discussion List-post: List-subscribe: , List-unsubscribe: , Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx Thread-index: AcYE3NUHcTotMM1NSRmAD4O7biwRpAAGXHcA Hi, I saw a few post on with the same error in the mailing archive but none seem to be related http://old-list-archives.xenproject.org/xen-users/2006-04/msg00968.html to the issue I have. OS is Ubuntu 5.10 "Breezy Badger" Issue reproduce with the latest xen_changeset : # xm info system : Linux host : srv002 release : 2.6.12.6-xen0 version : #2 SMP Mon Dec 19 21:05:01 CET 2005 machine : i686 nr_cpus : 4 nr_nodes : 1 sockets_per_node : 2 cores_per_socket : 1 http://old-list-archives.xenproject.org/xen-users/2005-12/msg00598.html threads_per_core : 2 cpu_mhz : 3591 hw_caps : bfebfbff:20100000:00000000:00000080:0000659d total_memory : 6144 free_memory : 3394 xen_major : 3 xen_minor : 0 xen_extra : .0 xen_caps : xen-3.0-x86_32p platform_params : virt_start=0xf5800000 xen_changeset : Thu Dec 15 20:57:27 2005 +0100 8259:5baa96bedc13 cc_compiler : gcc version 3.4.5 20050809 (prerelease) (Ubuntu 3.4.4-6ubuntu8) cc_compile_by : root cc_compile_domain : (none) cc_compile_date : Mon Dec 19 21:04:20 CET 2005 # cat debian.3-1.xen-lvm.cfg kernel = "/boot/vmlinuz-2.6-xenU" memory = 128 name = "debian.3-1.lvm" nics = 1 dhcp = "dhcp" disk = ['pty:/dev/Alyseo/VMroot01,sda1,w', 'pty:/dev/Alyseo/VMswap01,sda2,w'] root = "/dev/sda1 ro" # xm create debian.3-1.xen-lvm.cfg Using config file "debian.3-1.xen-lvm.cfg". Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. # tail -10 syslog Dec 20 00:32:05 srv002 logger: /etc/xen/scripts/vif-bridge: online XENBUS_PATH=backend/vif/11/0 Dec 20 00:32:05 srv002 logger: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/11/2050 Dec 20 00:32:05 srv002 kernel: device vif11.0 entered promiscuous mode Dec 20 00:32:05 srv002 kernel: xenbr0: port 3(vif11.0) entering learning state Dec 20 00:32:05 srv002 kernel: xenbr0: topology change detected, propagating Dec 20 00:32:05 sr
Forums Hosting Security and Technology Error: Domain 'vm101' does not exist. If this is your first visit, be sure to check out the FAQ by clicking http://www.webhostingtalk.com/showthread.php?t=1006301 the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Results 1 to 9 of 9 Thread: Error: Domain 'vm101' does not exist. Tweet Thread Tools Show Printable Version Subscribe to this Thread… Search Thread Advanced Search error device Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 12-16-2010,12:54 AM #1 santosh007 View Profile View Forum Posts View Forum Threads Temporarily Suspended Join Date Sep 2010 Posts 51 Error: Domain 'vm101' does not exist. I have problem with my xen server, I got this error [[emailprotected] ~]# xm reboot vm101 Error: Domain 'vm101' does not exist. Usage: xm reboot [-wa] error device 2049 Reboot a domain. Please suggest me. Reply With Quote 0 12-16-2010,12:59 AM #2 BBGN Brian View Profile View Forum Posts View Forum Threads Visit Homepage Web Hosting Master Join Date Jun 2010 Location Northern Virginia Posts 1,984 Try using: xm create /home/xen/vm101/vm101.cfg Should start it for you. ██ KVM SSD & SATA VPS | Dedicated Servers | Colocation ██ Managed and Self Managed Servers | North Carolina, Washington D.C, London and Texas Data Centers ██ www.bigbrainglobal.com | Big Brain Global Networks Reply With Quote 0 12-16-2010,01:06 AM #3 santosh007 View Profile View Forum Posts View Forum Threads Temporarily Suspended Join Date Sep 2010 Posts 51 I got this error [[emailprotected] ~]# xm create /home/xen/vm101/vm101.cfg Using config file "/home/xen/vm101/vm101.cfg". Error: Device 2049 (vbd) could not be connected. Device /dev/xenserver/vm101_img is mounted in a guest domain, and so cannot be mounted now. Reply With Quote 0 12-16-2010,01:06 AM #4 BBGN Brian View Profile View Forum Posts View Forum Threads Visit Homepage Web Hosting Master Join Date Jun 2010 Location Northern Virginia Posts 1,984 Originally Posted by santosh007 I got this error [[emailprotected] ~]# xm create /hom