aboutsummaryrefslogtreecommitdiff
path: root/QMP
diff options
context:
space:
mode:
authorMichael S. Tsirkin <mst@redhat.com>2013-03-06 14:58:59 +0200
committerMichael S. Tsirkin <mst@redhat.com>2013-03-17 13:27:27 +0200
commit0402a5d65ec004df5345d1f736e2ddaa7aee6665 (patch)
tree585662c4509f2033a15c317a576d2473b4dbb8dc /QMP
parentb1999e87b4d42305419329cae459e1b43f706d96 (diff)
downloadqemu-0402a5d65ec004df5345d1f736e2ddaa7aee6665.zip
qemu-0402a5d65ec004df5345d1f736e2ddaa7aee6665.tar.gz
qemu-0402a5d65ec004df5345d1f736e2ddaa7aee6665.tar.bz2
qdev: DEVICE_DELETED event
libvirt has a long-standing bug: when removing the device, it can request removal but does not know when the removal completes. Add an event so we can fix this in a robust way. Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Diffstat (limited to 'QMP')
-rw-r--r--QMP/qmp-events.txt16
1 files changed, 16 insertions, 0 deletions
diff --git a/QMP/qmp-events.txt b/QMP/qmp-events.txt
index b2698e4..24cf3e8 100644
--- a/QMP/qmp-events.txt
+++ b/QMP/qmp-events.txt
@@ -136,6 +136,22 @@ Example:
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.
+At this point, it's safe to reuse the specified device ID.
+Device removal can be initiated by the guest or by HMP/QMP commands.
+
+Data:
+
+- "device": device name (json-string, optional)
+
+{ "event": "DEVICE_DELETED",
+ "data": { "device": "virtio-net-pci-0" },
+ "timestamp": { "seconds": 1265044230, "microseconds": 450486 } }
+
DEVICE_TRAY_MOVED
-----------------