Re: [Xen-devel] xen live migration falied

[elahe shekuhi <e.shekuhi@xxxxxxxxx>]

On Thu, Jun 7, 2012 at 7:59 PM, Jan Beulich <jbeulich@xxxxxxxx> wrote:

>>> elahe shekuhi <e.shekuhi@xxxxxxxxx> 06/06/12 8:15 PM >>>

>On Wed, Jun 6, 2012 at 8:41 AM, Jan Beulich <JBeulich@xxxxxxxx> wrote:

>> Does migration fail in both directions? Or perhaps just from the
>> newer to the older system (in which case I would guess you're
>> not masking features properly on the newer one)?
>>
>
>Yes, Migration failed in both directions, but the error in Xend.log is
>different. When I do migrate VM from core 2 quad to core i7 machine the
>error in Xend.log is

Are you certain (i.e. is this really with the VM freshly started on the Core2
system)? I ask because this ...

   Yes I'm certain that the VM freshly started on the Core2 system. When I migrate the VM from Core2 to Core i7 I always see this error(i.e. "Couldn't set eXtended States for vcpu0 (22 = Invalid argument): Internal error" ) in the Xend.log on Core i7 machine.

>[2012-04-23 17:26:41 1405] INFO (XendCheckpoint:487) xc: error: Couldn't
>set eXtended States for vcpu0 (22 = Invalid argument): Internal error

... indicates that XSAVE state was available for the guest, but couldn't
be restored, yet iirc Core2 doesn't know XSAVE yet.

Irrespective of that you could try booting the hypervisors on both sides
with "no-xsave" and see whether that makes things any better (i.e.
work at least in one direction). But generally, if you opened an entry in
our bugzilla for this, we'd tell you that migration is only supported
between feature-identical machines, or at best with features masked
to the common subset on both systems.

   Also, when I migrate a VM freshly started on the Core i7 system to core 2, I get another error in xend.log on core2 system(i.e. destination system). The error is

[2012-06-07 12:03:31 30425] DEBUG (XendDomainInfo:3150) XendDomainInfo.destroy: domid=2

[2012-06-07 12:03:31 30425] DEBUG (XendDomainInfo:2465) Destroying device model

[2012-06-07 12:03:31 30425] INFO (image:711) s1 device model terminated

[2012-06-07 12:03:31 30425] DEBUG (XendDomainInfo:2472) Releasing devices

[2012-06-07 12:03:31 30425] DEBUG (XendDomainInfo:2478) Removing vif/0

[2012-06-07 12:03:31 30425] DEBUG (XendDomainInfo:1278) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0

[2012-06-07 12:03:31 30425] DEBUG (XendDomainInfo:2478) Removing vkbd/0

[2012-06-07 12:03:31 30425] DEBUG (XendDomainInfo:1278) XendDomainInfo.destroyDevice: deviceClass = vkbd, device = vkbd/0

[2012-06-07 12:03:31 30425] DEBUG (XendDomainInfo:2478) Removing console/0

[2012-06-07 12:03:31 30425] DEBUG (XendDomainInfo:1278) XendDomainInfo.destroyDevice: deviceClass = console, device = console/0

[2012-06-07 12:03:32 30425] DEBUG (XendDomainInfo:2478) Removing vbd/51728

[2012-06-07 12:03:32 30425] DEBUG (XendDomainInfo:1278) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/51728

[2012-06-07 12:03:32 30425] DEBUG (XendDomainInfo:2478) Removing vfb/0

[2012-06-07 12:03:32 30425] DEBUG (XendDomainInfo:1278) XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0

[2012-06-07 12:03:32 30425] DEBUG (XendDomainInfo:2470) No device model

[2012-06-07 12:03:32 30425] DEBUG (XendDomainInfo:2472) Releasing devices

[2012-06-07 12:03:32 30425] DEBUG (XendDomainInfo:2478) Removing vif/0

[2012-06-07 12:03:32 30425] DEBUG (XendDomainInfo:1278) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0

[2012-06-07 12:03:32 30425] DEBUG (XendDomainInfo:2478) Removing vbd/51728

[2012-06-07 12:03:32 30425] DEBUG (XendDomainInfo:1278) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/51728

[2012-06-07 12:03:32 30425] ERROR (XendCheckpoint:421) Device 51712 (vbd) could not be connected. losetup /dev/loop0 /home/elahe/xen/images/sles11/disk0.raw failed
Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/xen/xend/XendCheckpoint.py", line 412, in restore
    wait_devs(dominfo)
  File "/usr/lib64/python2.7/site-packages/xen/xend/XendCheckpoint.py", line 277, in wait_devs
    dominfo.waitForDevices() # Wait for backends to set up
  File "/usr/lib64/python2.7/site-packages/xen/xend/XendDomainInfo.py", line 1239, in waitForDevices
    self.getDeviceController(devclass).waitForDevices()
  File "/usr/lib64/python2.7/site-packages/xen/xend/server/DevController.py", line 140, in waitForDevices
    return map(self.waitForDevice, self.deviceIDs())
  File "/usr/lib64/python2.7/site-packages/xen/xend/server/DevController.py", line 168, in waitForDevice
    "%s" % (devid, self.deviceClass, err))
VmError: Device 51712 (vbd) could not be connected. losetup /dev/loop0 /home/elahe/xen/images/sles11/disk0.raw failed

[2012-06-07 12:03:32 30425] ERROR (XendDomain:1200) Restore failed
Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/xen/xend/XendDomain.py", line 1184, in domain_restore_fd
    dominfo = XendCheckpoint.restore(self, fd, paused=paused, relocating=relocating)
  File "/usr/lib64/python2.7/site-packages/xen/xend/XendCheckpoint.py", line 422, in restore
    raise exn
VmError: Device 51712 (vbd) could not be connected. losetup /dev/loop0 /home/elahe/xen/images/sles11/disk0.raw failed

Elahe,

Jan

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel