[Xen-users] domU suddenly stops working with error after machine restart

[David Koski <david@xxxxxxxxxxxxxxxx>]

I have five domU's that have been working. After a complete shutdown and
restart of the machine one of the domUs will not start but produces a message:

# xm create bc.cfg -c
Using config file "/etc/xen/bc.cfg".
Error: Device 2049 (vbd) could not be connected. Backend device not found.

I then have to "xm destroy bc" as it creates an unresponsive domU.

The log file reveals:

Jun  7 23:00:44 xen logger: /etc/xen/scripts/vif-bridge: online 
XENBUS_PATH=backend/vif/18/0
Jun  7 23:00:44 xen logger: /etc/xen/scripts/block: add 
XENBUS_PATH=backend/vbd/18/2050
Jun  7 23:00:44 xen logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge 
online for vif18.0, bridge xenbr0.
Jun  7 23:00:44 xen logger: /etc/xen/scripts/vif-bridge: Writing 
backend/vif/18/0/hotplug-status connected to xenstore.
Jun  7 23:00:44 xen logger: /etc/xen/scripts/block: add 
XENBUS_PATH=backend/vbd/18/2049
Jun  7 23:00:44 xen logger: /etc/xen/scripts/vif-bridge: online 
XENBUS_PATH=backend/vif/18/1
Jun  7 23:00:44 xen logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge 
online for vif18.1, bridge xenbr1.
Jun  7 23:00:44 xen logger: /etc/xen/scripts/vif-bridge: Writing 
backend/vif/18/1/hotplug-status connected to xenstore.
Jun  7 23:00:48 xen logger: /etc/xen/scripts/block: Forced to steal lock on 
/var/run/xen-hotplug/block from 15296: /etc/xen/scripts/block!
Jun  7 23:00:48 xen logger: /etc/xen/scripts/block: Forced to steal lock on 
/var/run/xen-hotplug/block from 15935: /etc/xen/scripts/block!
Jun  7 23:00:48 xen logger: /etc/xen/scripts/block: Writing 
backend/vbd/18/2050/hotplug-status error to xenstore.
Jun  7 23:00:48 xen logger: /etc/xen/scripts/block: Backend device does not 
exist
Jun  7 23:00:48 xen logger: /etc/xen/scripts/block: Writing 
backend/vbd/18/2049/hotplug-status error to xenstore.
Jun  7 23:00:48 xen logger: /etc/xen/scripts/block: Backend device does not 
exist

Where do I begin?

xen:

ii  libxen-python                 3.0.1-0tha2                   python wrapper 
around libxc, the control library for XEN
ii  libxen3.0                     3.0.1-0tha2                   control library 
for XEN, a Virtual Machine Monitor
ii  linux-xen0-2.6                2.6.12+xen3.0.1-0tha1         a xenified 
kernel for domain0 & domainUs.
ii  linux-xen0-2.6.12.6-xen       tha1                          Linux xen 
kernel binary image for version 2.6.12.6-xen
ii  xen                           3.0.1-0tha2                   a Virtual 
Machine Monitor like VMWare or plex86
ii  xen-docs                      3.0.1-0tha2                   documentation 
for XEN, a Virtual Machine Monitor

bc.cfg:

      1 name = "bc"
      2 kernel = "/boot/xen-linux-2.6.12.6-xen"
      3 root = "/dev/sda1 ro"
      4 memory = 256
      5 disk = [ 
'phy:/dev/mapper/main-guest.bcapp,sda1,w','phy:/dev/mapper/main-guest.bcapp.swap,sda2,w'
 ]
      6 vif = [ 'bridge=xenbr0', 'bridge=xenbr1' ]
      7 extra = "3"

The other cfg files that work are almost the same.

Regards,
David Koski
david.nospham@xxxxxxxxxxxxxxxx

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