All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Olsowski <andreas.olsowski@leuphana.de>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: pv guests die after failed migration
Date: Thu, 29 Dec 2011 15:08:04 +0100	[thread overview]
Message-ID: <4EFC7444.2040502@leuphana.de> (raw)
In-Reply-To: <1318691569.11016.42.camel@dagon.hellion.org.uk>


[-- Attachment #1.1: Type: text/plain, Size: 1441 bytes --]

Has any progress been made regarding this issue?



> 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.
>
Andreas


[-- Attachment #1.2: S/MIME Kryptografische Unterschrift --]
[-- Type: application/pkcs7-signature, Size: 5144 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

      reply	other threads:[~2011-12-29 14:08 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
2011-12-29 14:08                   ` Andreas Olsowski [this message]

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=4EFC7444.2040502@leuphana.de \
    --to=andreas.olsowski@leuphana.de \
    --cc=Ian.Campbell@citrix.com \
    --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 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.