[Xen-bugs] [Bug 526] New: Error: Device 2049 (vbd) could not be connected.

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=526

           Summary: Error: Device 2049 (vbd) could not be connected.
           Product: Xen
           Version: 3.0.1
          Platform: x86-64
        OS/Version: Linux-2.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: jslittl@xxxxxxxxxxxxx
                CC: ewan@xxxxxxxxxxxxx


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.

-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs