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: Sat, 15 Oct 2011 16:12:49 +0100 [thread overview]
Message-ID: <1318691569.11016.42.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <4E996206.4050500@leuphana.de>
On Sat, 2011-10-15 at 11:35 +0100, Andreas Olsowski wrote:
> On 10/15/2011 07:44 AM, Ian Campbell wrote:
> > On Sat, 2011-10-15 at 02:18 +0100, Andreas Olsowski wrote:
> >> It seems this still has not made it into 4.1-testing.
> >
> > I'm afraid I've not had time to "figure out how to automatically select
> > which guests are capable of a cooperative resume and which are not." so
> > it hasn't been fixed in xen-unstable either AFAIK.
> >
> Wouldnt just assuming all of them do fix a bigger percentage of systems
> than leaving it the way it is?
I don't know -- that's really the point.
> > I'm also still interested in confirmation to the question I asked in the
> > mail you just replied to.
> >
>
> Oh, i thought i allready did.
>
> > Are you saying that you don't see the "failed for domain %u" message
> > immediately after the xc_domain_resume call?
> >
> > + if (xc_domain_resume(ctx->xch, domid, 1)) {
> > LIBXL__LOG_ERRNO(ctx, LIBXL__LOG_ERROR,
> > "xc_domain_resume failed for domain %u",
> > domid);
> >
> > That would be pretty odd...
>
> Yes that is what i am saying:
Oh wait, that's right -- as far as the toolstack is concerned the resume
was successful -- the subsequent crash is within the guest.
Ian.
>
> root@memoryana:/var/log/xen# cat xl-testmig.log
> Waiting for domain testmig (domid 2) to die [pid 13349]
> Domain 2 is dead
> Done. Exiting now
>
next prev parent reply other threads:[~2011-10-15 15:12 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
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 [this message]
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=1318691569.11016.42.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).