aboutsummaryrefslogtreecommitdiff
path: root/QMP
diff options
context:
space:
mode:
authorPaolo Bonzini <pbonzini@redhat.com>2012-07-23 15:15:47 +0200
committerKevin Wolf <kwolf@redhat.com>2012-10-24 10:26:19 +0200
commita66a2a368383e627b929bf42d1b972822491404b (patch)
treefcec5bb544b797dcb2e7b40929bf304311e0c86a /QMP
parentaeae883baf2377b714a41529f94905046fa058f3 (diff)
downloadqemu-a66a2a368383e627b929bf42d1b972822491404b.zip
qemu-a66a2a368383e627b929bf42d1b972822491404b.tar.gz
qemu-a66a2a368383e627b929bf42d1b972822491404b.tar.bz2
block: introduce BLOCK_JOB_READY event
Even for jobs that need to be manually completed, management may want to take care itself of the completion, not requiring the user to issue a command to terminate the job. In this case we want to avoid that they poll us continuously, waiting for completion to become available. Thus, add a new event that signals the phase switch and the availability of the block-job-complete command. Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'QMP')
-rw-r--r--QMP/qmp-events.txt18
1 files changed, 18 insertions, 0 deletions
diff --git a/QMP/qmp-events.txt b/QMP/qmp-events.txt
index 987c575..b2698e4 100644
--- a/QMP/qmp-events.txt
+++ b/QMP/qmp-events.txt
@@ -118,6 +118,24 @@ Example:
"action": "stop" },
"timestamp": { "seconds": 1265044230, "microseconds": 450486 } }
+BLOCK_JOB_READY
+---------------
+
+Emitted when a block job is ready to complete.
+
+Data:
+
+- "device": device name (json-string)
+
+Example:
+
+{ "event": "BLOCK_JOB_READY",
+ "data": { "device": "ide0-hd1" },
+ "timestamp": { "seconds": 1265044230, "microseconds": 450486 } }
+
+Note: The "ready to complete" status is always reset by a BLOCK_JOB_ERROR
+event.
+
DEVICE_TRAY_MOVED
-----------------