From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Hongyang Yang <yanghy@cn.fujitsu.com>, xen-devel@lists.xen.org
Cc: Shriram Rajagopalan <rshriram@cs.ubc.ca>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [PATCH v2] fix Remus failover regression
Date: Thu, 07 Aug 2014 08:43:12 +0100 [thread overview]
Message-ID: <53E32E10.5090306@citrix.com> (raw)
In-Reply-To: <53E2D37D.4070503@cn.fujitsu.com>
On 07/08/2014 02:16, Hongyang Yang wrote:
> Ping!
>
> 在 07/28/2014 12:03 PM, Yang Hongyang 写道:
>> commit: c2ba706c
>> tools/libxc: goto correct label on error paths by Andrew Cooper
>> broke Remus in Xen 4.4 or earlier versions that has this commit
>> backported.
>>
>> With Remus, this jump essentially discards the current incomplete
>> checkpoint received by the backup and restore backup from the
>> last complete checkpoint.
>> This is required for Remus to work and this does not break live
>> migration.
>> It has been around since Xen 4.0.
>>
>> CC: Ian Jackson <ian.jackson@eu.citrix.com>
>> CC: Ian Campbell <ian.campbell@citrix.com>
>>
It is elsewhere in this thread, but Reviewed-by: Andrew Cooper
<andrew.cooper3@citrix.com>
>> CC: Shriram Rajagopalan <rshriram@cs.ubc.ca>
>> Signed-off-by: Yang Hongyang <yanghy@cn.fujitsu.com>
>> ---
>> tools/libxc/xc_domain_restore.c | 13 +++++++++++--
>> 1 file changed, 11 insertions(+), 2 deletions(-)
>>
>> diff --git a/tools/libxc/xc_domain_restore.c
>> b/tools/libxc/xc_domain_restore.c
>> index e73e0a2..b9a56d5 100644
>> --- a/tools/libxc/xc_domain_restore.c
>> +++ b/tools/libxc/xc_domain_restore.c
>> @@ -1783,20 +1783,29 @@ int xc_domain_restore(xc_interface *xch, int
>> io_fd, uint32_t dom,
>>
>> if ( pagebuf_get(xch, ctx, &pagebuf, io_fd, dom) ) {
>> PERROR("error when buffering batch, finishing");
>> - goto out;
>> + /*
>> + * Remus: discard the current incomplete checkpoint and restore
>> + * backup from the last complete checkpoint.
>> + */
>> + goto finish;
>> }
>> memset(&tmptail, 0, sizeof(tmptail));
>> tmptail.ishvm = hvm;
>> if ( buffer_tail(xch, ctx, &tmptail, io_fd, max_vcpu_id, vcpumap,
>> ext_vcpucontext, vcpuextstate_size) < 0 ) {
>> ERROR ("error buffering image tail, finishing");
>> - goto out;
>> + /*
>> + * Remus: discard the current incomplete checkpoint and restore
>> + * backup from the last complete checkpoint.
>> + */
>> + goto finish;
>> }
>> tailbuf_free(&tailbuf);
>> memcpy(&tailbuf, &tmptail, sizeof(tailbuf));
>>
>> goto loadpages;
>>
>> + /* With Remus: restore from last complete checkpoint */
>> finish:
>> if ( hvm )
>> goto finish_hvm;
>>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-08-07 7:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 4:03 [PATCH v2] fix Remus failover regression Yang Hongyang
2014-07-28 4:05 ` Shriram Rajagopalan
2014-07-28 9:24 ` Andrew Cooper
2014-07-28 9:29 ` Hongyang Yang
2014-07-28 10:11 ` Andrew Cooper
2014-08-07 1:16 ` Hongyang Yang
2014-08-07 7:43 ` Andrew Cooper [this message]
2014-08-21 8:12 ` Hongyang Yang
2014-08-21 22:49 ` Ian Campbell
2014-08-21 22:50 ` Ian Campbell
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=53E32E10.5090306@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=rshriram@cs.ubc.ca \
--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).