From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
David Vrabel <david.vrabel@citrix.com>
Subject: Re: Is: Xen 4.2 and using 'xl' to save/restore is buggy with PVHVM Linux guests (v3.10 and v3.11 and presumarily earlier as well). Works with Xen 4.3 and Xen 4.4. Was:Re: FAILURE 3.11.0-rc7upstream(x86_64) 3.11.0-rc7upstream(i386)\: 2013-08-26 (tst001)
Date: Mon, 23 Sep 2013 14:40:14 -0400 [thread overview]
Message-ID: <20130923184014.GA2472@phenom.dumpdata.com> (raw)
In-Reply-To: <CAFLBxZZbURoABaD-0=ptAtM4-QCW3hxvNZBXpXG=hTNDim9FaQ@mail.gmail.com>
On Fri, Sep 13, 2013 at 11:54:32AM +0100, George Dunlap wrote:
> On Tue, Aug 27, 2013 at 2:54 PM, Konrad Rzeszutek Wilk
> <konrad.wilk@oracle.com> wrote:
> > After a bit of digging I found out that Xen 4.2 'xl' (but not 'xm')
> > has some badness in it. When "migrating" ('xl' save followed by 'xl' restore')
> > the PVHVM guests (and only PVHVM) end up dying. The best theory I came up
> > with is that they don't have the shared_info setup correctly as the guest
> > is not receiving any events.
>
> [snip]
>
> > Once more I need to stress that it works great when using 'xm' in Xen 4.2
> > but fails over when using 'xl' in Xen 4.2.
> >
> > I can't recall whether 'xl' in Xen 4.2 was considered experiemental or
> > production ready at that point?
>
> I'm pretty sure in 4.2 xl was the favored toolstack -- it was only 4.1
> in which we considered it experimental.
>
> This works in 4.3, though? Maybe there was a fix that didn't get backported?
Yes, it does work there.
And I also make sure to use the same version of QEMU in both places - the
traditional one. Not that it would make a big difference.
>
> Ian J, do we test PVHVM suspend/resume in osstest?
.. Using the traditional or the the SeaBIOS?
>
> -George
prev parent reply other threads:[~2013-09-23 18:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201308262234.r7QMYAvE028854@build-mk2.dumpdata.com>
2013-08-27 13:54 ` Is: Xen 4.2 and using 'xl' to save/restore is buggy with PVHVM Linux guests (v3.10 and v3.11 and presumarily earlier as well). Works with Xen 4.3 and Xen 4.4. Was:Re: FAILURE 3.11.0-rc7upstream(x86_64) 3.11.0-rc7upstream(i386)\: 2013-08-26 (tst001) Konrad Rzeszutek Wilk
2013-09-13 10:54 ` George Dunlap
2013-09-13 11:41 ` Ian Jackson
2013-09-13 18:47 ` Pasi Kärkkäinen
2013-09-23 18:40 ` Konrad Rzeszutek Wilk [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=20130923184014.GA2472@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=ian.jackson@eu.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 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).