WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] more than two loopback device is not connected.
From: "Satoshi Uchida" <s-uchida@xxxxxxxxxxxxx>
Date: Tue, 29 Nov 2005 16:59:56 +0900
Delivery-date: Tue, 29 Nov 2005 08:00:50 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcX0uuF4Z9r3VJQ/Q5SDmmGXqnTjLA==
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
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] more than two loopback device is not connected., Satoshi Uchida <=