From: Juan Quintela <quintela@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: stefanha@redhat.com, owasserm@redhat.com,
Jules Wang <junqing.wang@cs2c.com.cn>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH RFC 2/4] Curling: cmdline interface
Date: Tue, 10 Sep 2013 17:21:39 +0200 [thread overview]
Message-ID: <87eh8w4s8s.fsf@elfo.elfo> (raw)
In-Reply-To: <522F2EDD.2070005@redhat.com> (Paolo Bonzini's message of "Tue, 10 Sep 2013 16:38:21 +0200")
Paolo Bonzini <pbonzini@redhat.com> wrote:
> Il 10/09/2013 18:37, Juan Quintela ha scritto:
>>> I think for the outgoing side it should just be "migrate -f tcp:foo:9999".
>>>
>>> On the incoming side, perhaps you could have a different ID instead of
>>> QEMU_VM_FILE_MAGIC, that triggers fault-tolerance mode automatically?
>>> Then again it would be simply "-incoming tcp:foo:9999".
>>
>> Then how can you distingish between faultolerance and simple migration?
>> You need to diferentiate on both sides.
>>
>> - outgoing side: you need to continue running after sending the whole
>> state
>> - incoming side: after receivinga lot, you apply it, and have to wait
>> for the next one.
>>
>> It is a different thing to do, we need to tell qemu somehow.
>
> You look at the first 4 bytes in the stream and distinguish the two cases.
We need to change how things are handled. Are we sure we don't want
curling over exec/unix/fd?
next prev parent reply other threads:[~2013-09-10 15:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 3:43 [Qemu-devel] [PATCH RFC 0/4] Curling: KVM Fault Tolerance Jules Wang
2013-09-10 3:43 ` [Qemu-devel] [PATCH RFC 1/4] Curling: add doc Jules Wang
2013-09-10 3:43 ` [Qemu-devel] [PATCH RFC 2/4] Curling: cmdline interface Jules Wang
2013-09-10 13:57 ` Juan Quintela
2013-09-10 13:03 ` Paolo Bonzini
2013-09-10 16:37 ` Juan Quintela
2013-09-10 14:38 ` Paolo Bonzini
2013-09-10 15:21 ` Juan Quintela [this message]
2013-09-10 15:22 ` Juan Quintela
2013-09-11 2:51 ` junqing.wang
2013-09-10 3:43 ` [Qemu-devel] [PATCH RFC 3/4] Curling: the sender Jules Wang
2013-09-10 14:05 ` Juan Quintela
2013-09-11 7:31 ` junqing.wang
2013-09-10 3:43 ` [Qemu-devel] [PATCH RFC 4/4] Curling: the receiver Jules Wang
2013-09-10 14:19 ` Juan Quintela
2013-09-11 8:25 ` junqing.wang
2013-09-10 12:27 ` [Qemu-devel] [PATCH RFC 0/4] Curling: KVM Fault Tolerance Orit Wasserman
2013-09-11 1:54 ` junqing.wang
2013-09-12 7:37 ` Orit Wasserman
2013-09-12 8:17 ` junqing.wang
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=87eh8w4s8s.fsf@elfo.elfo \
--to=quintela@redhat.com \
--cc=junqing.wang@cs2c.com.cn \
--cc=owasserm@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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.