From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:33474) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VMHQJ-0006gr-3A for qemu-devel@nongnu.org; Wed, 18 Sep 2013 09:04:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VMHQB-0004Rv-7z for qemu-devel@nongnu.org; Wed, 18 Sep 2013 09:04:03 -0400 Received: from mx1.redhat.com ([209.132.183.28]:7063) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VMHQA-0004Rj-Ve for qemu-devel@nongnu.org; Wed, 18 Sep 2013 09:03:55 -0400 From: Luiz Capitulino Date: Wed, 18 Sep 2013 09:03:42 -0400 Message-Id: <1379509422-29115-7-git-send-email-lcapitulino@redhat.com> In-Reply-To: <1379509422-29115-1-git-send-email-lcapitulino@redhat.com> References: <1379509422-29115-1-git-send-email-lcapitulino@redhat.com> Subject: [Qemu-devel] [PULL 6/6] QMP: qmp-events.txt: alphabetical order fix and other minor changes List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: anthony@codemonkey.ws Cc: qemu-devel@nongnu.org Signed-off-by: Luiz Capitulino Reviewed-by: Eric Blake --- docs/qmp/qmp-events.txt | 34 +++++++++++++++++----------------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/docs/qmp/qmp-events.txt b/docs/qmp/qmp-events.txt index 4b24ec9..6b87e97 100644 --- a/docs/qmp/qmp-events.txt +++ b/docs/qmp/qmp-events.txt @@ -1,4 +1,4 @@ - QEMU Monitor Protocol Events + QEMU Machine Protocol Events ============================ BALLOON_CHANGE @@ -159,7 +159,7 @@ Note: The "ready to complete" status is always reset by a BLOCK_JOB_ERROR event. DEVICE_DELETED ------------------ +-------------- Emitted whenever the device removal completion is acknowledged by the guest. @@ -194,8 +194,22 @@ Data: }, "timestamp": { "seconds": 1265044230, "microseconds": 450486 } } +GUEST_PANICKED +-------------- + +Emitted when guest OS panic is detected. + +Data: + +- "action": Action that has been taken (json-string, currently always "pause"). + +Example: + +{ "event": "GUEST_PANICKED", + "data": { "action": "pause" } } + NIC_RX_FILTER_CHANGED ------------------ +--------------------- The event is emitted once until the query command is executed, the first event will always be emitted. @@ -486,17 +500,3 @@ Example: Note: If action is "reset", "shutdown", or "pause" the WATCHDOG event is followed respectively by the RESET, SHUTDOWN, or STOP events. - -GUEST_PANICKED --------------- - -Emitted when guest OS panic is detected. - -Data: - -- "action": Action that has been taken (json-string, currently always "pause"). - -Example: - -{ "event": "GUEST_PANICKED", - "data": { "action": "pause" } } -- 1.8.1.4