From: Shriram Rajagopalan <rshriram@cs.ubc.ca>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
FNST-Yang Hongyang <yanghy@cn.fujitsu.com>,
xen-devel@lists.xen.org
Subject: Re: Remus failover broken in Xen 4.4 due to code cleanup in libxc
Date: Sun, 27 Jul 2014 23:31:33 -0400 [thread overview]
Message-ID: <CAP8mzPMjvJ1XDnhfWFaMau=z2FoZMvpTRYUNcCWSOCB_F_XC9g@mail.gmail.com> (raw)
In-Reply-To: <CAP8mzPO0V0hXBao3zf+YCmFGai29OU3DT3HN+oAYBNYffoWr5w@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 605 bytes --]
Correction. Its commit c2ba706c
On Jul 27, 2014 11:10 PM, "Shriram Rajagopalan" <rshriram@cs.ubc.ca> wrote:
> Commit c5f2a9a7
> tools/libxc: goto correct label on error paths
> by Andrew Cooper totally broke Remus in Xen 4.4 (even the simple memory
> replication part). Anyone who wants to use Remus with xend won't be able to
> either. :(
> Andrew, any specific reason for this patch or was it just trying to decode
> the live migration control flow, and fixing a potential error along the
> way? Sigh..
> Anyway, will send a patch fixing this and adding comments on why it is
> required.
>
> Shriram
>
[-- Attachment #1.2: Type: text/html, Size: 886 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2014-07-28 3:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 3:10 Remus failover broken in Xen 4.4 due to code cleanup in libxc Shriram Rajagopalan
2014-07-28 3:31 ` Shriram Rajagopalan [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='CAP8mzPMjvJ1XDnhfWFaMau=z2FoZMvpTRYUNcCWSOCB_F_XC9g@mail.gmail.com' \
--to=rshriram@cs.ubc.ca \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=yanghy@cn.fujitsu.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).