From: Juan Quintela <quintela@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 3/5] QMP: Introduce MIGRATION events
Date: Tue, 25 May 2010 20:38:54 +0200 [thread overview]
Message-ID: <m3pr0jesht.fsf@trasno.mitica> (raw)
In-Reply-To: <20100525152139.2d96e30c@redhat.com> (Luiz Capitulino's message of "Tue, 25 May 2010 15:21:39 -0300")
Luiz Capitulino <lcapitulino@redhat.com> wrote:
> On Tue, 25 May 2010 17:35:53 +0200
> Juan Quintela <quintela@redhat.com> wrote:
>
>> Anthony Liguori <anthony@codemonkey.ws> wrote:
>> > On 05/25/2010 09:21 AM, Juan Quintela wrote:
>>
>> >> +MIGRATION_CANCELED
>> >> +------------------
>> >> +
>> >> +Emitted when migration is canceled. This is emitted in the source.
>> >> +Target will emit MIGRATION_FAILED (no way to differentiate a FAILED
>> >> +and CANCELED migration for target).
>> >>
>> >
>> > But the management tool is the one that cancels so surely, it knows
>> > why already.
>>
>> ok, then that one is ok.
>
> Isn't this one important for the destination instead?
Destination don't know what happened, only that conection/data is not
coming anymore.
>From management prespective, management application knows that it has
canceled the migration, so no need to be told.
Later, Juan.
next prev parent reply other threads:[~2010-05-25 18:39 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 14:21 [Qemu-devel] [PATCH v2 0/5] Add QMP migration events Juan Quintela
2010-05-25 14:21 ` [Qemu-devel] [PATCH 1/5] Exit if incoming migration fails Juan Quintela
2010-05-25 18:01 ` Luiz Capitulino
2010-05-25 18:37 ` [Qemu-devel] " Juan Quintela
2010-05-25 18:52 ` Anthony Liguori
2010-05-25 14:21 ` [Qemu-devel] [PATCH 2/5] Factorize common migration incoming code Juan Quintela
2010-05-25 14:21 ` [Qemu-devel] [PATCH 3/5] QMP: Introduce MIGRATION events Juan Quintela
2010-05-25 15:09 ` Anthony Liguori
2010-05-25 15:35 ` [Qemu-devel] " Juan Quintela
2010-05-25 15:52 ` Daniel P. Berrange
2010-05-25 15:57 ` Anthony Liguori
2010-05-25 16:04 ` Juan Quintela
2010-05-25 16:10 ` Anthony Liguori
2010-05-25 18:13 ` Luiz Capitulino
2010-05-25 16:04 ` Daniel P. Berrange
2010-05-25 16:04 ` Juan Quintela
2010-05-25 16:25 ` Daniel P. Berrange
2010-05-25 16:33 ` Anthony Liguori
2010-05-25 16:43 ` Juan Quintela
2010-05-26 10:33 ` Daniel P. Berrange
2010-05-26 14:54 ` Anthony Liguori
2010-05-26 15:15 ` Daniel P. Berrange
2010-05-26 16:55 ` Anthony Liguori
2010-05-27 13:48 ` Luiz Capitulino
2010-05-27 15:58 ` Juan Quintela
2010-05-27 16:07 ` Luiz Capitulino
2010-05-27 16:07 ` Anthony Liguori
2010-05-26 10:16 ` Daniel P. Berrange
2010-05-25 18:21 ` Luiz Capitulino
2010-05-25 18:38 ` Juan Quintela [this message]
2010-05-25 15:48 ` [Qemu-devel] " Daniel P. Berrange
2010-05-25 18:31 ` Luiz Capitulino
2010-05-25 18:51 ` Anthony Liguori
2010-05-26 13:14 ` Luiz Capitulino
2010-05-25 14:21 ` [Qemu-devel] [PATCH 4/5] QMP: Emit migration events on incoming migration Juan Quintela
2010-05-25 14:21 ` [Qemu-devel] [PATCH 5/5] QMP: Emit migration events on outgoing migration Juan Quintela
-- strict thread matches above, loose matches on Subject: below --
2010-05-24 8:25 [Qemu-devel] [PATCH 0/5] Add QMP migration events Juan Quintela
2010-05-24 8:25 ` [Qemu-devel] [PATCH 3/5] QMP: Introduce MIGRATION events Juan Quintela
2010-05-24 9:04 ` [Qemu-devel] " Paolo Bonzini
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=m3pr0jesht.fsf@trasno.mitica \
--to=quintela@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.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.