Re: [Xen-devel] live migration from new platform to old platform

["Hao, Xudong" <xudong.hao@xxxxxxxxx>]

> -----Original Message-----
> From: Andrew Cooper [mailto:andrew.cooper3@xxxxxxxxxx]
> Sent: Tuesday, June 7, 2016 5:47 PM
> To: Hao, Xudong <xudong.hao@xxxxxxxxx>; Xen-devel <xen-
> devel@xxxxxxxxxxxxxxxxxxxx>
> Cc: Zhang, Haozhong <haozhong.zhang@xxxxxxxxx>; Wei Liu
> <wei.liu2@xxxxxxxxxx>
> Subject: Re: [Xen-devel] live migration from new platform to old platform
> 
> 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.
> 
Yes.

> 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.
> 
Actually, it report bad CR4 but not show SMAP explicitly, of course the CR4 
include SMAP control bit in below error log.
(XEN) HVM4 restore: bad CR4 0x3406f0

Thanks,
-Xudong

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