From: Avi Kivity <avi@redhat.com>
To: Uri Lublin <uri@il.qumranet.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
Uri Lublin <uril@qumranet.com>,
kvm@vger.kernel.org
Subject: Re: [PATCH] qemu: qemu_fopen_fd: differentiate between reader and writer user
Date: Thu, 16 Oct 2008 16:32:24 +0200 [thread overview]
Message-ID: <48F75078.5090604@redhat.com> (raw)
In-Reply-To: <48F74E6C.8070100@il.qumranet.com>
Uri Lublin wrote:
>>>
>>> Weren't there some acks flowing back on the old protocol to let the
>>> source now things are fine?
>>
>> There were, but there aren't now. They don't improve reliability.
>>
>
> Why do you think they don't improve reliability ?
> The Ack/Go messages catch the scenario where SRC finishes sending all
> its state, and DST have a problem loading that state. In that case SRC
> thinks migration was completed successfully (and stay in stopped
> mode), while DST exists.
The management tool is in contact with both, and can arbitrate. Once it
thinks both source and destination are in a good state, it can continue
the destination and quit the source.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-10-16 14:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-12 16:30 [PATCH] qemu: qemu_fopen_fd: differentiate between reader and writer user Uri Lublin
2008-10-12 16:55 ` Avi Kivity
2008-10-12 18:09 ` Anthony Liguori
2008-10-12 18:17 ` Avi Kivity
2008-10-12 22:18 ` Anthony Liguori
2008-10-13 3:03 ` Anthony Liguori
2008-10-16 1:36 ` Uri Lublin
2008-10-16 4:14 ` Anthony Liguori
2008-10-16 8:13 ` Avi Kivity
2008-10-16 12:54 ` Anthony Liguori
2008-10-16 14:23 ` Uri Lublin
2008-10-16 14:32 ` Avi Kivity [this message]
2008-10-16 14:49 ` Uri Lublin
2008-10-17 2:47 ` Anthony Liguori
2008-10-19 13:46 ` Uri Lublin
2008-10-19 22:00 ` Anthony Liguori
2008-10-22 16:23 ` Uri Lublin
2008-10-16 10:52 ` Uri Lublin
2008-10-16 0:13 ` Uri Lublin
2008-10-16 4:10 ` Anthony Liguori
2008-10-16 8:16 ` Avi Kivity
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=48F75078.5090604@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=kvm@vger.kernel.org \
--cc=uri@il.qumranet.com \
--cc=uril@qumranet.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 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.