All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hongyang Yang <yanghy@cn.fujitsu.com>
To: Wen Congyang <wency@cn.fujitsu.com>, xen-devel@lists.xen.org
Cc: Shriram Rajagopalan <rshriram@cs.ubc.ca>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [PATCH] fix Remus failover regression
Date: Mon, 28 Jul 2014 12:20:25 +0800	[thread overview]
Message-ID: <53D5CF89.3050108@cn.fujitsu.com> (raw)
In-Reply-To: <53D5CBFB.30701@cn.fujitsu.com>



On 07/28/2014 12:05 PM, Wen Congyang wrote:
> At 07/28/2014 11:35 AM, Yang Hongyang Write:
>> commit: c2ba706c
>> tools/libxc: goto correct label on error paths by Andrew broke
>> Remus in Xen 4.4 or earlier versions that has this commit backported.
>>
>> With Remus, this jump essentially discards the last incomplete
>> checkpoint received by the backup.
>> This is required for Remus to work and this does not break live
>> migration.
>>
>> CC: Ian Jackson <ian.jackson@eu.citrix.com>
>> CC: Ian Campbell <ian.campbell@citrix.com>
>> CC: 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 | 4 ++--
>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/tools/libxc/xc_domain_restore.c b/tools/libxc/xc_domain_restore.c
>> index e73e0a2..5d2fbd6 100644
>> --- a/tools/libxc/xc_domain_restore.c
>> +++ b/tools/libxc/xc_domain_restore.c
>> @@ -1783,14 +1783,14 @@ 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;
>> +        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;
>> +        goto finish;
>>       }
>>       tailbuf_free(&tailbuf);
>>       memcpy(&tailbuf, &tmptail, sizeof(tailbuf));
>>
>
> The mail is here:
> http://lists.xenproject.org/archives/html/xen-devel/2014-01/msg02299.html
>
>> Both of these errors have been discovered by xc_domain_restore() returning
>> success after suffering a fatal error during migration, leading to the
>> toolstack believing that the VM migrated successfully.
>
> These codes are only for Remus. So, why these codes are executed by migration?

I was confused also, without Remus, these two error path will not be hitted I
think, without Remus, migration will ended at:
1776     if ( ctx->last_checkpoint )
1777     {
1778         // DPRINTF("Last checkpoint, finishing\n");
1779         goto finish;
1780     }

>
> Thanks
> Wen Congyang
>
>
> .
>

-- 
Thanks,
Yang.

  reply	other threads:[~2014-07-28  4:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-28  3:35 [PATCH] fix Remus failover regression Yang Hongyang
2014-07-28  3:44 ` Shriram Rajagopalan
2014-07-28  4:05 ` Wen Congyang
2014-07-28  4:20   ` Hongyang Yang [this message]
2014-07-28  4:50     ` Shriram Rajagopalan

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=53D5CF89.3050108@cn.fujitsu.com \
    --to=yanghy@cn.fujitsu.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=rshriram@cs.ubc.ca \
    --cc=wency@cn.fujitsu.com \
    --cc=xen-devel@lists.xen.org \
    /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.