Re: [Xen-devel] xl migrate regression in staging

[Andrew Cooper <andrew.cooper3@xxxxxxxxxx>]

On 14/04/16 14:03, Olaf Hering wrote:
> Migration from staging-4.5.3f802a5 to staging-4-7.3dac42f fails with a HVM 
> guest:
>
>
> root@anonymi:~ # xl migrate domU host
> migration target: Ready to receive domain.
> Saving to migration stream new xl format (info 0x1/0x0/2677)
> xc: error: error polling suspend notification channel: -1: Internal error
> Loading new save file <incoming migration stream> (new xl fmt info 
> 0x1/0x0/2677)
>  Savefile contains xl domain config in JSON format
> Parsing config from <saved>
> libxl: error: libxl_stream_read.c:327:stream_header_done: Invalid ident: 
> expected 0x4c6962786c466d74, got 0x01f00f0000000000
> libxl: error: libxl_utils.c:430:libxl_read_exactly: file/stream truncated 
> reading ipc msg header from domain 1 save/restore helper stdout pipe
> libxl: error: libxl_exec.c:129:libxl_report_child_exitstatus: domain 1 
> save/restore helper [-1] died due to fatal signal Broken pipe
> libxl: error: libxl_dom.c:2036:remus_teardown_done: Remus: failed to teardown 
> device for guest with domid 1, rc -3
> migration sender: libxl_domain_suspend failed (rc=-3)
> libxl: info: libxl_exec.c:118:libxl_report_child_exitstatus: migration 
> transport process [2000] exited with error status 255
> Migration failed, resuming at sender.
> xc: error: Dom 1 not suspended: (shutdown 0, reason 255): Internal error
> libxl: error: libxl.c:515:libxl__domain_resume: xc_domain_resume failed for 
> domain 1: Invalid argument
>
>
> I think this regression was introduced in the last 3-4 weeks.

Over that time, the COLO support has been added to libxl, which seems
like a likely candidate.

This looks like it isn't kicking off the legacy conversion script on the
destination side.

Can you do an `xl save` to file on the source side, and on the
destination side manually invoke convert-legacy-stream and
verify-stream-v2 (both of which are also specifically usable on the
command line as well as automatically) ?  This will identify if it is a
"content of the stream" error, or a plumbing error.

~Andrew

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