From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58957) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YyIjF-0001QN-2M for qemu-devel@nongnu.org; Fri, 29 May 2015 07:45:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YyIjB-0000Yv-SD for qemu-devel@nongnu.org; Fri, 29 May 2015 07:45:32 -0400 Received: from mx1.redhat.com ([209.132.183.28]:49411) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YyIjB-0000Yr-N1 for qemu-devel@nongnu.org; Fri, 29 May 2015 07:45:29 -0400 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (Postfix) with ESMTPS id C01CB19CBCB for ; Fri, 29 May 2015 11:45:28 +0000 (UTC) Date: Fri, 29 May 2015 13:45:27 +0200 From: Jiri Denemark Message-ID: <20150529114527.GA3525@orkuz.home> References: <1432136124-24572-1-git-send-email-quintela@redhat.com> <1432136124-24572-3-git-send-email-quintela@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1432136124-24572-3-git-send-email-quintela@redhat.com> Subject: Re: [Qemu-devel] [PATCH 2/3] migration: create migration event List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Juan Quintela Cc: amit.shah@redhat.com, qemu-devel@nongnu.org On Wed, May 20, 2015 at 17:35:23 +0200, Juan Quintela wrote: > We have one argument that tells us what event has happened. > > Signed-off-by: Juan Quintela > --- > docs/qmp/qmp-events.txt | 16 ++++++++++++++++ > migration/migration.c | 12 ++++++++++++ > qapi/event.json | 14 ++++++++++++++ > 3 files changed, 42 insertions(+) Hi Juan, I patched libvirt to be able to consume this event and it all seems to work fine except for events sent after migrate_cancel command: {"execute":"migrate_cancel","id":"libvirt-33"} {"timestamp": {"seconds": 1432899178, "microseconds": 844907}, "event": "MIGRATION", "data": {"status": "cancelling"}} {"return": {}, "id": "libvirt-33"} {"timestamp": {"seconds": 1432899178, "microseconds": 845625}, "event": "MIGRATION", "data": {"status": "failed"}} {"timestamp": {"seconds": 1432899178, "microseconds": 846432}, "event": "MIGRATION", "data": {"status": "cancelled"}} In other words, the status first changes to "failed" and then it changes correctly "cancelled". Can you fix this weird behavior in QEMU or do we have to work around it in libvirt? Jirka