qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 3/5] QMP: Introduce MIGRATION events
Date: Mon, 24 May 2010 11:04:29 +0200	[thread overview]
Message-ID: <htdfet$och$1@dough.gmane.org> (raw)
In-Reply-To: <d93b6fadfc42b87b34a8c86674a9a8edb37ae5f3.1274688090.git.quintela@redhat.com>

On 05/24/2010 10:25 AM, Juan Quintela wrote:
> +MIGRATION_CANCELED
> +------------------
> +
> +Emitted when migration is canceled.  This is emitted in the source.
> +Target will emit MIGRATION_CANCELED (no way to differentiate a FAILED
> +and CANCELED migration).

Copy-paste error? (or if not, parse error on my side).

> +Data: None
> +
> +Example:
> +
> +{ "event": "MIGRATION_CANCELED",
> +    "timestamp": {"seconds": 1274687575, "microseconds": 592483} }
> +
> +MIGRATION_ENDED
> +---------------
> +
> +Emitted when migration starts (both in source and target)

Likewise.

Paolo

  reply	other threads:[~2010-05-24  9:04 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-24  8:25 [Qemu-devel] [PATCH 0/5] Add QMP migration events Juan Quintela
2010-05-24  8:25 ` [Qemu-devel] [PATCH 1/5] Exit if incoming migration fails Juan Quintela
2010-05-24  9:02   ` [Qemu-devel] " Paolo Bonzini
2010-05-24 11:53   ` Michael S. Tsirkin
2010-05-24  8:25 ` [Qemu-devel] [PATCH 2/5] Factorize common migration incoming code Juan Quintela
2010-05-24  8:25 ` [Qemu-devel] [PATCH 3/5] QMP: Introduce MIGRATION events Juan Quintela
2010-05-24  9:04   ` Paolo Bonzini [this message]
2010-05-24  8:25 ` [Qemu-devel] [PATCH 4/5] QMP: Emit migration events on incoming migration Juan Quintela
2010-05-24  8:25 ` [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-25 14:21 [Qemu-devel] [PATCH v2 0/5] Add QMP migration events 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

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='htdfet$och$1@dough.gmane.org' \
    --to=pbonzini@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 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).