From: George Dunlap <george.dunlap@eu.citrix.com>
To: "rshriram@cs.ubc.ca" <rshriram@cs.ubc.ca>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH 5/5] X86/vMCE: guest broken page handling when migration
Date: Tue, 20 Nov 2012 16:57:15 +0000 [thread overview]
Message-ID: <50ABB66B.7090004@eu.citrix.com> (raw)
In-Reply-To: <CAP8mzPNYECd_nrO6Y7CL3X+3AFZ-ibSxwPFi1ZTJ75d7h6En1A@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1363 bytes --]
On 22/10/12 20:26, Shriram Rajagopalan wrote:
> On Mon, Oct 22, 2012 at 3:54 AM, Ian Jackson
> <Ian.Jackson@eu.citrix.com <mailto:Ian.Jackson@eu.citrix.com>> wrote:
>
> George Dunlap writes ("Re: [Xen-devel] [PATCH 5/5] X86/vMCE: guest
> broken page handling when migration"):
> > On Fri, Oct 19, 2012 at 4:14 PM, Ian Jackson
> <Ian.Jackson@eu.citrix.com <mailto:Ian.Jackson@eu.citrix.com>> wrote:
> > > This looks plausible to me, as far as the tools go. Can you
> explain
> > > how you have tested this ? Did you manage to do any tests of the
> > > remus codepaths ?
> >
> > I'm pretty sure that this shouldn't cause any problems with
> Remus. If
> > it's difficult for Jinsong to test Remus, I think probably OK to
> > commit it, and then revert it if the Remus guys have any problems.
>
> OK.
>
>
> You can easily test it with Remus. With xl, memory replication
> functionality is already
> in place. so xl remus command should work.
Should "xl remus $domain localhost" work? How would one test the
fail-over mechanism? Are there any other requirements for the guest,
the kernel, &c?
I just ran the above command on xen-unstable, and after 10 minutes or so
the guest crashed with some kind of a kernel double-fault.
Are we running any remus stuff in our testing infrastructure?
-George
[-- Attachment #1.2: Type: text/html, Size: 2895 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-11-20 16:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 14:47 [PATCH 5/5] X86/vMCE: guest broken page handling when migration Liu, Jinsong
2012-10-16 10:44 ` Liu, Jinsong
2012-10-19 15:14 ` Ian Jackson
2012-10-19 17:09 ` George Dunlap
2012-10-19 21:07 ` Liu, Jinsong
2012-10-22 10:54 ` Ian Jackson
2012-10-22 19:26 ` Shriram Rajagopalan
2012-11-20 16:57 ` George Dunlap [this message]
2012-11-26 14:49 ` Shriram Rajagopalan
2013-01-15 15:05 ` George Dunlap
2012-10-19 16:54 ` George Dunlap
-- strict thread matches above, loose matches on Subject: below --
2012-09-19 8:15 Liu, Jinsong
2012-10-10 9:21 ` Ian Campbell
2012-10-10 14:42 ` Liu, Jinsong
2012-09-18 13:18 Liu, Jinsong
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=50ABB66B.7090004@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=rshriram@cs.ubc.ca \
--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).