John S Little
2006-Feb-09 14:02 UTC
[Xen-users] Error: Device 2049 (vbd) could not be connected (only when in auto/)
Hi all When I have a domU that resides in the auto directory I get ''Error: Device 2049 (vbd) could not be connected'' and the domain starts in a paused mode. Shutting it down and restarting has the same effect. Following is some output from the xm log and an attempted restart. Directly after dom0 reboot: xen0:/etc/xen/scripts # xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 251 4 r----- 329.4 xen0vm0-64 4 256 1 --p--- 0.0?>From the logs after dom0 reboot:[2006-02-08 12:03:00 xend] ERROR (SrvBase:87) Request wait_for_devices failed. Traceback (most recent call last): File "/usr/lib64/python/xen/web/SrvBase.py", line 85, in perform return op_method(op, req) File "/usr/lib64/python/xen/xend/server/SrvDomain.py", line 72, in op_wait_for_devices return self.dom.waitForDevices() File "/usr/lib64/python/xen/xend/XendDomainInfo.py", line 1350, in waitForDevices self.waitForDevices_(c) File "/usr/lib64/python/xen/xend/XendDomainInfo.py", line 979, in waitForDevices_ return self.getDeviceController(deviceClass).waitForDevices() File "/usr/lib64/python/xen/xend/server/DevController.py", line 134, in waitForDevices return map(self.waitForDevice, self.deviceIDs()) File "/usr/lib64/python/xen/xend/server/DevController.py", line 169, in waitForDevice raise VmError("Device %s (%s) could not be connected.\n%s" % VmError: Device 2049 (vbd) could not be connected. Device /dev/xensan/xenvm1-64 is mounted in a guest domain, and so cannot be mounted now. And an attempt at shutting down the domU and restarting: xen0:/etc/xen/scripts # xm unpause xen0vm0-64 xen0:/etc/xen/scripts # xm shutdown xen0vm0-64 xen0:/etc/xen/scripts # xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 251 4 r----- 326.4 xen0:/etc/xen/scripts # xm create -c ../auto/xen0vm0-64 Using config file "../auto/xen0vm0-64". Error: Device 2049 (vbd) could not be connected. Device /dev/xensan/xenvm1-64 is mounted in a guest domain, and so cannot be mounted now. xen0:/etc/xen/scripts # The system setup OS: xen0:~ # SPident CONCLUSION: System is up-to-date! found SLES-9-x86_64-SP3 + "online updates" Hardware: Sun V20z, dual cpu AMD64 The virtual machine resides on EMC San space setup with LVM (/dev/sdc setup as volume group /dev/xensan) I''ve tried various settings in the /etc/sysconfig/xendomains file but without any luck. Can anyone steer me in the right direction to getting this resolved? Regards, John Little Hendricks Regional Health IS Department 317-718-4752 jslittl@hendricks.org http://www.hendrickshospital.org _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Possibly Parallel Threads
- Strange problem with guest having more than 3 virtual interfaces.
- Error: Device 768 (vbd) could not be connected. Backend device not found.
- Loop Mounted Device Issue?
- Device 0 (vif) could nto be connected: backend device not found
- Working hotplug, but still timing out waiting for vbd device