xen 3.0 Error: Device 2049 (vbd) could not be connected. Backend device not found.

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

xen 3.0 Error: Device 2049 (vbd) could not be connected. Backend device not found.

路易
Hello:

        I use debian sarge with xen 3.0 changeset 8112, make from source and boot dom0
without problems.

        But when I try to start first domU, it complained
"Error: Device 2049 (vbd) could not be connected. Backend device not found."

drbl:~# xm list
Name                              ID Mem(MiB) VCPUs State  Time(s)
Domain-0                           0      167     2 r-----  7283.9
etch                               1       60     1 --p---     0.0

        Then I check /var/log/xend.log

[2005-11-30 13:44:50 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_devices
    return self.dom.waitForDevices()
  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 1264, in waitForDevices
    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 waitForDevices
    return map(self.waitForDevice, self.deviceIDs())
  File "/usr/lib/python/xen/xend/server/DevController.py", line 137, in waitForDevice
    raise VmError("Device %s (%s) could not be connected. "
VmError: Device 2049 (vbd) could not be connected. Backend device not found.


        I have no idea how it is going on, but when I check /var/log/syslog

Nov 30 13:44:50 drbl udev[3930]: error: unknown bus, please report to <[hidden email]
orge.net> 'xen-backend'
Nov 30 13:44:50 drbl logger: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/1/2049
Nov 30 13:44:50 drbl udev[3936]: error: unknown bus, please report to <[hidden email]
orge.net> 'xen-backend'
Nov 30 13:44:50 drbl logger: /etc/xen/scripts/block: Writing backend/vbd/1/2049/hotplug-status error to
xenstore.
Nov 30 13:44:50 drbl logger: /etc/xen/scripts/vif-bridge: online XENBUS_PATH=backend/vif/1/0
Nov 30 13:44:50 drbl logger: /etc/xen/scripts/block: Failed to find an unused loop device

        So I destroy paused domU, manual "modprobe loop", then "xm create etch" again
        It worked well. Now I can start my domUs well, any thought ??

drbl:/# xm list
Name                              ID Mem(MiB) VCPUs State  Time(s)
Domain-0                           0      167     2 r-----  9126.1
etch                               8       30     1 r-----     9.4

--
                      Louie November 30, 2005   14:35:35

                     `$'         $'
  ,d$$$b,             $          $       "
 ,$P'  `Yb      ,d$$$g$  ,d$$$b. $,d$$$b`$' g$$$$$b $,d$$b
 $' ,$`  $     ,$P'  `$ ,$P' `Y$ $$'  `$ $  "'   `$ $$' `$
 $  `$gg$'     $$     $ $$ggggg$ $     $ $ ,$P""  $ $    $
 `b            `$g. ,$$ `$$._ _. $ _,g$P $ `$b. ,$$ $    $
  `$g_          `Y$$P'$. `Y$$$$P $$$P"' ,$. `Y$$P'$ $.  ,$.

_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xensource.com/xen-users