From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=48565 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OGz1o-0003pc-5m
	for qemu-devel@nongnu.org; Tue, 25 May 2010 14:39:01 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <quintela@redhat.com>) id 1OGz1m-0003p5-Hn
	for qemu-devel@nongnu.org; Tue, 25 May 2010 14:38:59 -0400
Received: from mx1.redhat.com ([209.132.183.28]:2000)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <quintela@redhat.com>) id 1OGz1m-0003or-A0
	for qemu-devel@nongnu.org; Tue, 25 May 2010 14:38:58 -0400
From: Juan Quintela <quintela@redhat.com>
In-Reply-To: <20100525152139.2d96e30c@redhat.com> (Luiz Capitulino's message
	of "Tue, 25 May 2010 15:21:39 -0300")
References: <cover.1274796992.git.quintela@redhat.com>
	<9b6575587d22a5c85ec536172810520ee3b945d5.1274796992.git.quintela@redhat.com>
	<4BFBE843.5070202@codemonkey.ws> <m34ohwhu3q.fsf@trasno.mitica>
	<20100525152139.2d96e30c@redhat.com>
Date: Tue, 25 May 2010 20:38:54 +0200
Message-ID: <m3pr0jesht.fsf@trasno.mitica>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Qemu-devel] Re: [PATCH 3/5] QMP: Introduce MIGRATION events
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: qemu-devel@nongnu.org

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.