From: Wei Liu <wei.liu2@citrix.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: Wei Liu <wei.liu2@citrix.com>, xen-devel@lists.xen.org
Subject: Re: xl migrate regression in staging
Date: Thu, 14 Apr 2016 16:31:05 +0100 [thread overview]
Message-ID: <20160414153104.GB19098@citrix.com> (raw)
In-Reply-To: <20160414130301.GA4688@aepfle.de>
On Thu, Apr 14, 2016 at 03:03:01PM +0200, 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
Is there anything in xl dmesg regarding this?
> 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
This is libxl expected libxl stream header (the 0x4cxxx is header
signature) but got something else.
> 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
I feel quite confused why remus is involved.
> 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.
>
Maybe go back to 96ae556569b8eaedc0bb242932842c3277b515d8 and try again?
Then 5cf46a66883ad7a56c5bdee97696373473f80974 and try? So that I can
know if it is related to COLO series. No, don't try to bisect that
because it's broken in the middle.
Also as Andrew suggested if you can reproduce it with a smaller domain
or share the guest image with us, that would be helpful.
Wei.
> Olaf
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-14 15:31 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
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 [this message]
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=20160414153104.GB19098@citrix.com \
--to=wei.liu2@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.