From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Hao, Xudong" <xudong.hao@intel.com>,
Xen-devel <xen-devel@lists.xenproject.org>
Cc: "Zhang, Haozhong" <haozhong.zhang@intel.com>,
Wei Liu <wei.liu2@citrix.com>
Subject: Re: live migration from new platform to old platform
Date: Tue, 7 Jun 2016 10:46:58 +0100 [thread overview]
Message-ID: <57569812.3030701@citrix.com> (raw)
In-Reply-To: <B8376D2DEA074F45BA033984477C453E034ACC47@shsmsx102.ccr.corp.intel.com>
On 07/06/16 08:02, Hao, Xudong wrote:
> Does anyone experience for HVM live migration from new generation platform to old generation platform? For X86 got a failure from Broadwell to Haswell, both platforms used same Xen version 4.7.0 RC3.
>
> [root@bdw-ep1 feng]# xl migrate 21 hsw-ep1
> ...
> migration target: Ready to receive domain.
> Saving to migration stream new xl format (info 0x3/0x0/1537) Loading new save file <incoming migration stream> (new xl fmt info 0x3/0x0/1537) Savefile contains xl domain config in JSON format Parsing config from <saved>
> xc: info: Saving domain 21, type x86 HVM
> xc: info: Found x86 HVM domain from Xen 4.7
> xc: info: Restoring domain
> xc: error: Unable to restore HVM context (1 = Operation not permitted): Internal error
> xc: error: Restore failed (1 = Operation not permitted): Internal error
> libxl: error: libxl_stream_read.c:852:libxl__xc_domain_restore_done: restoring domain: Operation not permitted
> libxl: error: libxl_create.c:1220:domcreate_rebuild_done: cannot (re-)build domain: -3
> libxl: error: libxl.c:1564:libxl__destroy_domid: non-existant domain 31
> libxl: error: libxl.c:1523:domain_destroy_callback: unable to destroy guest with domid 31
> libxl: error: libxl.c:1452:domain_destroy_cb: destruction of domain 31 failed migration target: Domain creation failed (code -3).
> libxl: error: libxl_utils.c:507:libxl_read_exactly: file/stream truncated reading ready message from migration receiver stream
> libxl: info: libxl_exec.c:118:libxl_report_child_exitstatus: migration transport process [20867] exited with error status 1 Migration failed, resuming at sender.
I see you have a solution to this problem.
In general, `xl dmesg` on hsw-ep1 will provide some information as to
why the restore failed. Given your hardware, I expect the problem was
with CR4.SMAP.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-07 9:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 7:02 live migration from new platform to old platform Hao, Xudong
2016-06-07 7:38 ` Jan Beulich
2016-06-07 8:40 ` Hao, Xudong
2016-06-07 9:46 ` Andrew Cooper [this message]
2016-06-08 2:08 ` Hao, Xudong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57569812.3030701@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=haozhong.zhang@intel.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
--cc=xudong.hao@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.