All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Olaf Hering <olaf@aepfle.de>, xen-devel@lists.xen.org
Subject: Re: xl migrate regression in staging
Date: Thu, 14 Apr 2016 14:08:54 +0100	[thread overview]
Message-ID: <570F9666.4040502@citrix.com> (raw)
In-Reply-To: <20160414130301.GA4688@aepfle.de>

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@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2016-04-14 13:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-14 13:03 xl migrate regression in staging Olaf Hering
2016-04-14 13:08 ` Andrew Cooper [this message]
2016-04-14 13:52   ` Olaf Hering
2016-04-14 13:54     ` Olaf Hering
2016-04-14 14:04     ` Andrew Cooper
2016-04-14 14:15       ` Olaf Hering
2016-04-14 15:00         ` Andrew Cooper
2016-04-14 13:32 ` Olaf Hering
2016-04-14 15:31 ` Wei Liu
2016-04-14 15:36   ` Olaf Hering
2016-06-02 15:18     ` annie li
2016-06-02 15:21       ` Wei Liu
2016-06-02 16:18         ` annie li

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=570F9666.4040502@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=olaf@aepfle.de \
    --cc=xen-devel@lists.xen.org \
    /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.