Error Device 5632 Vbd Could Not Be Connected
create /home/xen/vm747/vm747.cfg Using config file "/home/xen/vm747/vm747.cfg". Error: Device 5632 (vbd) could not be connected. /etc/xen/scripts/block failed; error detected. Checking free loop devices : [root@test ~]# losetup -f losetup: not found any public free loop device Checking status of loop devices : [root@test ~]# hotplug scripts not working oracle vm losetup -a /dev/loop0: [fd1c]:3997699 (/home/solusvm/xen/iso/2003_server.iso) /dev/loop1: [fd1c]:3997700 (/home/solusvm/xen/iso/2008_Spanish_32.iso) /dev/loop2: [fd1c]:3997709 (/home/solusvm/xen/iso/2003server.iso) /dev/loop3: [fd1c]:3997698 (/home/solusvm/xen/iso/2008_Spanish_x64.iso) /dev/loop4: [fd1c]:3997709 error: device 0 (vif) could not be connected. hotplug scripts not working. (/home/solusvm/xen/iso/2003server.iso) Blog Archive ► 2016 (2) ► 09/25 - 10/02 (1) ► 09/11 - 09/18 (1) ► 2015 (3) ► 05/24 - 05/31 (1) ► 02/15 - 02/22 (2) ► 2014 (8) ► 11/30 - 12/07 (1) ► 11/16 - 11/23 (1) ► 10/12 - 10/19 (1) ► 03/09 - 03/16 (2) ► 02/23 - 03/02 (1) ► 02/16 - 02/23 (2) ► 2013 (17) ► 12/15 - 12/22 (2) ► 12/08 - 12/15 (2) ► 11/10 - 11/17 (1) ► 11/03 - 11/10 (1) ► 10/20 - 10/27 (1) ► 09/29 - 10/06 (1) ► 09/15 - 09/22 (1) ► 09/01 - 09/08 (1) ► 08/25 - 09/01 (3) ► 08/18 - 08/25 (1) ► 07/21 - 07/28 (1) ► 03/31 - 04/07 (1) ► 03/24 - 03/31 (1) ► 2012 (67) ► 12/16 - 12/23 (1) ► 10/28 - 11/04 (1) ► 10/14 - 10/21 (1) ► 10/07 - 10/14 (2) ► 09/02 - 09/09 (1) ► 08/05 - 08/12 (2) ► 07/01 - 07/08 (1) ► 06/24 - 07/01 (3) ► 06/03 - 06/10 (1) ► 05/27 - 06/03 (1) ► 05/20 - 05/27 (2) ► 05/13 - 05/20 (1) ► 04/29 - 05/06 (1) ► 04/22 - 04/29 (4) ► 04/15 - 04/22 (4) ► 04/08 - 04/15 (6) ► 04/01 - 04/08 (2) ► 03/25 - 04/01 (1) ► 03/18 - 03/25 (3) ► 03/11 - 03/18 (3) ► 03/04 - 03/11 (4) ► 02/26 - 03/04 (3) ► 02/19 - 02/26 (4) ► 02/12 - 02/19 (3) ► 02/05 - 02/12 (3) ► 01/29 - 02/05 (1) ► 01/22 - 01/29 (2) ► 01/15 - 01/22 (2) ► 01/08 - 01/15 (2) ► 01/01 - 01/08 (2) ▼ 2011 (112) ► 12/25 - 01/01 (1) ► 12/04 - 12/11 (5) ► 11/27 - 12/04 (4) ► 11/20 - 11/27 (2) ► 11/13 - 11/20 (2) ► 11/06 - 11/13 (6) ► 10/30 - 11/06 (4) ► 10/23 - 10/30 (4) ► 10/02 - 10/09 (2) ► 09/25 - 10/02 (2) ► 09/18 - 09/25 (3) ► 09/11 - 09/18 (3) ► 09/04 - 09/11 (6) ► 08/28 - 09/04 (5) ► 08/14 - 08/21 (5) ► 08/07 - 08/14 (3) ► 07/31 - 08/07 (3) ► 0
#1 2012-03-11 05:47:38 jps Member Registered: 2012-03-11 Posts: 3 [SOLVED] Xen "Hotplug scripts not working" Error I've been at this one for two days and hopefully someone can help out. I am trying to get a Xen vm setup (I would use kvm, but this machine doesn't have the vmx extensions), but it is fighting me.I am using LVM for my vm filesystem: --- Logical volume --- LV Path /dev/XenGroup00/lvol-jps-server LV Name lvol-jps-server VG Name XenGroup00 LV UUID gfgYTq-WvIb-OANl-EZwm-zzc0-vfmL-aN3oAn LV Write Access read/write LV Creation host, time jps, 2012-03-09 11:35:54 -0600 http://www.linuxhelp.in/2011/06/error-device-vbd-could-not-be-connected.html LV Status available LV Size 8.00 GiB Current LE 2048 Segments 2 Allocation inherit Read ahead sectors autoMy DomU config looks like this:# -*- mode: python; -*- kernel = "/boot/vmlinuz-linux" ramdisk = "/boot/initramfs-linux.img" memory = 2048 name = "jps-server" vif = [ 'mac=00:16:3e:60:36:ba' ] disk = [ 'phy:/dev/XenGroup00/lvol-jps-server,xvda,w' ] dhcp="dhcp" hostname = "jps.server" root = "/dev/xvda ro" extra = "console=hvc0"When I https://bbs.archlinux.org/viewtopic.php?id=137415 run xm create -c dom01 I get the following error:Error: Device 51712 (vbd) could not be connected. Hotplug scripts not working.The xend.log outputs:[2012-03-10 23:05:10 790] DEBUG (XendDomainInfo:1881) XendDomainInfo.handleShutdownWatch [2012-03-10 23:05:10 790] DEBUG (DevController:139) Waiting for devices vif. [2012-03-10 23:05:10 790] DEBUG (DevController:139) Waiting for devices vkbd. [2012-03-10 23:05:10 790] DEBUG (DevController:139) Waiting for devices ioports. [2012-03-10 23:05:10 790] DEBUG (DevController:139) Waiting for devices tap. [2012-03-10 23:05:10 790] DEBUG (DevController:139) Waiting for devices vif2. [2012-03-10 23:05:10 790] DEBUG (DevController:139) Waiting for devices console. [2012-03-10 23:05:10 790] DEBUG (DevController:144) Waiting for 0. [2012-03-10 23:05:10 790] DEBUG (DevController:139) Waiting for devices vscsi. [2012-03-10 23:05:10 790] DEBUG (DevController:139) Waiting for devices vbd. [2012-03-10 23:05:10 790] DEBUG (DevController:144) Waiting for 51712. [2012-03-10 23:05:10 790] DEBUG (DevController:628) hotplugStatusCallback /local/domain/0/backend/vbd/1/51712/hotplug-status.and hangs there before giving me the error and then breaking down the vm.I can use xl create /etc/xen/dom01 -c and it gives me this output:Parsing config file /etc/xen/dom01 Unable to attach console Daemon running with PID 921Trying to get a console with `xl` errors:# xl console jps-server Unable to attach consoleBUT, using `xm console` drops me into
limited in one physical machines above Xen Eucalyptus Issues related to software problems. Post Reply Print view http://www.centos.org/forums/viewtopic.php?t=22185 Search Advanced search 9 posts • Page 1 of 1 liriarte http://serverfault.com/questions/40947/xen-cant-create-domain-because-vdb-could-not-be-connected Posts: 12 Joined: 2011/02/09 15:53:15 Contact: Contact liriarte Website Two virtual machines limited in one physical machines above Xen Eucalyptus Quote Postby liriarte » 2012/01/26 11:55:14 I have an Eucalyptus-based cloud using Xen with 3 nodes. When I run a VM more could not than twice the number of physical machines in the xen cluster, the extra VMs never boot up, they always change state from pending to terminate, and the log file shows the node controller shutoff the extra VM after it check the instances number. When I manually shutdown some VM, then I can easily start could not be up some VM exactly as the number I've shutdown.The log shows this error:ERROR:[Tue Jan 17 12:51:05 2012][004231][EUCAERROR ] libvirt: POST operation failed: xend_post: error from xen daemon: (xend.err 'Device 2049 (vbd) could not be connected. /etc/xen/scripts/block failed; error detected.') (code=11)[Tue Jan 17 12:51:05 2012][004231][EUCADEBUG ] doDescribeResource() invoked[Tue Jan 17 12:51:06 2012][004231][EUCADEBUG ] doDescribeInstances() invoked[Tue Jan 17 12:51:06 2012][004231][EUCADEBUG ] doDescribeInstances(): instanceId=i-3BB00757 publicIp=192.168.4.165 privateIp=192.168.4.165 mac=d0:0d:3B:B0:07:57 vlan=-1 networkIndex=-1[Tue Jan 17 12:51:06 2012][004231][EUCADEBUG ] doDescribeInstances(): instanceId=i-473807EE publicIp=192.168.4.112 privateIp=192.168.4.112 mac=d0:0d:47:38:07:EE vlan=-1 networkIndex=-1[Tue Jan 17 12:51:06 2012][004231][EUCADEBUG ] doDescribeInstances(): instanceId=i-348A06AE publicIp=0.0.0.0 privateIp=0.0.0.0 mac=d0:0d:34:8A:06:AE vlan=-1 networkIndex=-1[Tue Jan 17 12:51:06 2012][004231][EUCAERROR ] libvirt: POST operation failed: xend_post: error from xen daemon: (xend.err 'Device 2049 (vbd) could not be connected. /etc/xen/scripts/block failed; error detected.') (code=11)[Tue Jan 17 12:51:08 2012][004231][EUCAERROR ] libvirt: POST operation failed: xend_post: error from xen daemon: (xend.err 'Device 2049 (vbd) could not be connected. /etc/xen/scripts/block failed; error detected.') (code=11)[Tue Jan 17 12:51:09 2012][004231][EUCAERROR ] libvirt: POST operation failed: xend_post: error from xen daemo
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Xen - can't create domain because 'vdb could not be connected' up vote 1 down vote favorite I'm trying to start up a Xen VM, however I'm getting the following error: Error: Device 2049 (vbd) could not be connected. Hotplug scripts not working. what does this mean? The dom0 is CentOS and the guest OS is Debian Lenny. The network interfaces I'm using are: vif = [ 'mac=00:16:3e:3e:53:5f, bridge=xenbr0', 'mac=00:16:3e:18:16:e5, bridge=xenbr1' ] The root filesystem of the guest OS is set to mount over NFS from the dom0, this is working for other guest OSs on the same host. The swap (and /var) is mounted from a local LVM logical volume UPDATE My fault. I hadn't written the config correctly, and hadn't set up the filesystems correctly. I was able to look at /var/log/xen/xen-hotplug.log to see that it was accessing the wrong device. linux xen virtual-machines share|improve this question edited Jul 15 '09 at 9:55 asked Jul 15 '09 at 9:47 Rory 11k36117196 That's much simpler :) Oh well, my answer might be of use to somebody else with the same error. –Dan Carley Jul 15 '09 at 10:37 add a comment| 2 Answers 2 active oldest votes up vote 2 down vote Short version: Check that you have /etc/udev/rules.d/xen-backend.rules. The file may or may not be prefixed by a number. If not, check whether you have /etc/udev/xen-backend.rules and create a symlink from that to /etc/udev/rules.d/xen-backend.rules. Long version: I've seen this with a Gentoo 3.3 dom0, not CentOS. But I suspect