[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Xen migration fails

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Virajith Jalaparti <virajith.j@xxxxxxxxx>
  • Date: Tue, 12 Apr 2011 16:40:22 -0500
  • Delivery-date: Tue, 12 Apr 2011 14:49:19 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=v/tO170bnYBmIJSaIGazEm1IlPJib1qjO6F+eHcDKKm+J2seC3hw+jrWxWqFxTvO4C G+xeGOhdtHhG7qT7/7LwCGr3y+C5HTuMWeQDyaG2g9+kGQJl7RjJ0GjpFqwqONvqQglm g5+NufSZG1S01EPJdFIianG/gxSDywjdsNI8Y=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>


I have been getting the following error (logged in /var/log/xen/xend.log) when I try to migrate a VM from one particular host to the other (the reverse migration works fine). My system was working fine for a long time (i did several migrations in both the directions). I am using Xen-3.4.3 (installed from source code) with CentOS 5.4. I am using drbd to replicate the disks.

[2011-04-12 16:22:48,010 16027] ERROR (XendCheckpoint:352) Device 51712 (vbd) could not be connected.
Device /dev/drbd4 is mounted in a guest domain,
and so cannot be mounted now.
Traceback (most recent call last):
  File "usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py", line 350, in restore
    dominfo.waitForDevices() # Wait for backends to set up
  File "usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1069, in waitForDevices
  File "usr/lib64/python2.4/site-packages/xen/xend/server/DevController.py", line 140, in waitForDevices
    return map(self.waitForDevice, self.deviceIDs())
  File "usr/lib64/python2.4/site-packages/xen/xend/server/DevController.py", line 175, in waitForDevice
    raise VmError("Device %s (%s) could not be connected.\n%s" %
VmError: Device 51712 (vbd) could not be connected.
Device /dev/drbd4 is mounted in a guest domain,
and so cannot be mounted now.
The output of mount is:
# mount
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/sda1 on /boot type ext3 (rw)
tmpfs on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
none on /var/lib/xenstored type tmpfs (rw)

Did any one encounter this error before? Searching around, I found some work-arounds people have used (using xenstore-rm to remove the link to that particular vbd http://readlist.com/lists/lists.xensource.com/xen-users/0/4325.html) but none of them work for my case. I tried creating a new VM along with a new drbd drive but even that VM was encountering this error when I try to migrate.
Any help would be greatly appreciated!!

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.