From: Ian Campbell <Ian.Campbell@citrix.com>
To: Andreas Olsowski <andreas.olsowski@leuphana.de>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: pv guests die after failed migration
Date: Tue, 20 Sep 2011 20:27:59 +0100 [thread overview]
Message-ID: <1316546879.5182.26.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <4E786015.80603@leuphana.de>
On Tue, 2011-09-20 at 10:42 +0100, Andreas Olsowski wrote:
> When xm failed to do a live migration the system was resumed on the
> sending host.
> Xl does not do that it TRIES to, but just crashes the guest:
> kernel BUG at drivers/xen/events.c:1466!
> (In this example the target host didnt have the logical volume activated.)
>
> Now that cant be right.
No, it's a bug, perhaps in the kernel but likely in the toolstack.
Please can you provide full logs from /var/log/xen on both ends. Running
"xl -vvv migrate" will also produce more stuff on stdout, some of which
may be useful.
Also please capture the complete guest log in case it is an issue there.
> Imho xl should do some checking if the target is a viable migration
> target (are the disks and vifs there, is there enough memory available)
> and preserve a safe state on the sender until the guest has properly
> started on the receiver.
xl does have some checks and does preserve the sender side until it gets
confirmation of correct restart, but obviously something is wrong with
the bit which restarts the old guest. I'm sure it worked at one point
though.
Thanks,
Ian.
next prev parent reply other threads:[~2011-09-20 19:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 9:42 pv guests die after failed migration Andreas Olsowski
2011-09-20 19:27 ` Ian Campbell [this message]
2011-09-23 7:39 ` Andreas Olsowski
2011-09-23 7:47 ` Ian Campbell
2011-09-23 9:15 ` Andreas Olsowski
2011-09-28 15:52 ` Ian Campbell
2011-10-15 1:18 ` Andreas Olsowski
2011-10-15 5:44 ` Ian Campbell
2011-10-15 10:35 ` Andreas Olsowski
2011-10-15 15:12 ` Ian Campbell
2011-12-29 14:08 ` Andreas Olsowski
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=1316546879.5182.26.camel@dagon.hellion.org.uk \
--to=ian.campbell@citrix.com \
--cc=andreas.olsowski@leuphana.de \
--cc=xen-devel@lists.xensource.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).