Re: [Xen-devel] xen live migration falied

["Jan Beulich" <jbeulich@xxxxxxxx>]

>>> 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 ...

>[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.

Jan


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