http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1036

Summary: Live migration for HVM guest fails easily Product: Xen Version: unstable Platform: Other OS/Version: All Status: NEW Severity: normal Priority: P2 Component: HVM AssignedTo: xen-...@lists.xensource.com ReportedBy: jeff...@intel.com

In our nightly test we found live migration for HVM guest is very easy to fail. The reproduce steps: 1. Create HVM guest 2. xm migrate -l <dom-id> localhost

Here is xend.log: ====================================================================== [2007-08-02 15:42:36 7180] ERROR (XendCheckpoint:272) Device 768 (vbd) could not be connected. File /share/xvs/var/ia32_fc4.img is loopback-mounted through /dev/loop0, which is mounted in a guest domain, and so cannot be mounted now. Traceback (most recent call last): File "/usr/lib/python/xen/xend/XendCheckpoint.py", line 270, in restore dominfo.waitForDevices() # Wait for backends to set up File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 559, in waitForDevices self.getDeviceController(devclass).waitForDevices() File "/usr/lib/python/xen/xend/server/DevController.py", line 149, in waitForDevices return map(self.waitForDevice, self.deviceIDs()) File "/usr/lib/python/xen/xend/server/DevController.py", line 184, in waitForDevice raise VmError("Device %s (%s) could not be connected.\n%s" % VmError: Device 768 (vbd) could not be connected. File /share/xvs/var/ia32_fc4.img is loopback-mounted through /dev/loop0, which is mounted in a guest domain, and so cannot be mounted now. ===============================================================