[Xen-devel] more than two loopback device is not connected.

["Satoshi Uchida" <s-uchida@xxxxxxxxxxxxx>]

Hi.

I use xen-unstable and update xen-unstable.hp on Monday.
(In this time,  I update now, so changeset is 8090.)
For flexible constructions, I separate many image.file like / , /usr,
/home and swap.

In this week, VM cannot be started up, because vbd divices is not
connected.
 Error msg :  Device 2054 (vbd) could not be connected. Backend device
not found.
In /sys information, I see that vbd is created.

And, In the case that starting up only one image.file, VM is runnning.

I try to find causes of this problem, but not now.

Do anyone have any hints?



xend.log is following

[2005-11-29 11:33:04 xend] ERROR (SrvBase:87) Request wait_for_devices
failed.
Traceback (most recent call last):
  File "/usr/lib/python/xen/web/SrvBase.py", line 85, in perform
    return op_method(op, req)
  File "/usr/lib/python/xen/xend/server/SrvDomain.py", line 68, in
op_wait_for_d
evices
    return self.dom.waitForDevices()
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 1264, in
waitForDevice
s
    self.waitForDevices_(c)
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 912, in
waitForDevices
_
    return self.getDeviceController(deviceClass).waitForDevices()
  File "/usr/lib/python/xen/xend/server/DevController.py", line 121, in
waitForD
evices
    return map(self.waitForDevice, self.deviceIDs())
  File "/usr/lib/python/xen/xend/server/DevController.py", line 137, in
waitForD
evice
    raise VmError("Device %s (%s) could not be connected. "
VmError: Device 2049 (vbd) could not be connected. Backend device not
found.


============================
Satoshi UCHIDA

Attachment: smime.p7s
Description: S/MIME cryptographic signature

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