Error Device 51713 Vbd Could Not Be Connected
#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 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 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 a recovery shell with this output:[ 0.141322] i8042: No controller
to Milestone xen-3.2 (Ubuntu) Edit Confirmed Undecided Unassigned Edit You need to log in to change this bug's status. Affecting: xen-3.2 (Ubuntu) Filed here by: Andrew Shugg When: 2008-03-23 Confirmed: 2008-03-24 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Confirmed Undecided Assigned to Nobody Me Comment on this change (optional) Email me about changes to this bug report https://bbs.archlinux.org/viewtopic.php?id=137415 xen-tools (Ubuntu) Edit Confirmed Undecided Unassigned Edit You need to log in to change this bug's status. Affecting: xen-tools (Ubuntu) Filed here by: Todd Deshane When: 2008-03-24 Confirmed: 2013-01-03 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) https://bugs.launchpad.net/bugs/205450 Status Importance Confirmed Undecided Assigned to Nobody Me Comment on this change (optional) Email me about changes to this bug report Also affects project (?) Also affects distribution/package Nominate for series Bug Description I have been having troubles with Xen simply being unable to run paravirt domUs since I built a gutsy server a while ago. When booting a domU it would bomb out to the initrd busybox shell because it could not find its root device. (The same config works fine on an Ubuntu 7.04 Xen server.) Used dist-upgrade to track hardy, trying xen-3.1 and then xen-3.2 packges. After a while I blamed the problems on EVMS because I was using EVMS volumes for the root and swap devices for domUs. However then after trying the loopback file method I couldn't get the domU to start either. The error message is the same that is posted in another bug report: https://bugs.launchpad.net/ubuntu/+source/xen-3.2/+bug/199533/comments/31 So, today I put in a new system disk into this problem server and installed from scratch using hardy i386 alpha 2008-03-16 C
Arroyo] [PermanentLink][Original] To: Muriel