]> Git Repo - qemu.git/commitdiff
qmp-events: move 'BLOCK_IO_ERROR' doc to schema
authorMarc-André Lureau <[email protected]>
Thu, 23 Jun 2016 13:52:10 +0000 (15:52 +0200)
committerMarkus Armbruster <[email protected]>
Mon, 16 Jan 2017 08:19:48 +0000 (09:19 +0100)
Signed-off-by: Marc-André Lureau <[email protected]>
Signed-off-by: Markus Armbruster <[email protected]>
docs/qmp-events.txt
qapi/block-core.json

index f3ea933f87ecdce302e365a07ed863e4abeb6912..dc5bce111b39ca8ef551ad88c0a99bde489e3153 100644 (file)
@@ -30,37 +30,6 @@ Example:
 
 Note: this event is rate-limited.
 
-BLOCK_IO_ERROR
---------------
-
-Emitted when a disk I/O error occurs.
-
-Data:
-
-- "device": device name. This is always present for compatibility
-            reasons, but it can be empty ("") if the image does not
-            have a device name associated. (json-string)
-- "node-name": node name. Note that errors may be reported for the root node
-               that is directly attached to a guest device rather than for the
-               node where the error occurred. (json-string)
-- "operation": I/O operation (json-string, "read" or "write")
-- "action": action that has been taken, it's one of the following (json-string):
-    "ignore": error has been ignored
-    "report": error has been reported to the device
-    "stop": the VM is going to stop because of the error
-
-Example:
-
-{ "event": "BLOCK_IO_ERROR",
-    "data": { "device": "ide0-hd1",
-              "node-name": "#block212",
-              "operation": "write",
-              "action": "stop" },
-    "timestamp": { "seconds": 1265044230, "microseconds": 450486 } }
-
-Note: If action is "stop", a STOP event will eventually follow the
-BLOCK_IO_ERROR event.
-
 BLOCK_JOB_CANCELLED
 -------------------
 
index cfae11f54c7d282438cc1c5cfa80f1f5e2fa04f5..89af577625e8edeb6779ae8622e28fdfada63412 100644 (file)
 #        event and must be repaired (Since 2.2; before, every
 #        BLOCK_IMAGE_CORRUPTED event was fatal)
 #
+# Note: If action is "stop", a STOP event will eventually follow the
+#       BLOCK_IO_ERROR event.
+#
 # Example:
 #
 # <- { "event": "BLOCK_IMAGE_CORRUPTED",
 # BLOCK_IO_ERROR event
 #
 # Since: 0.13.0
+#
+# Example:
+#
+# <- { "event": "BLOCK_IO_ERROR",
+#      "data": { "device": "ide0-hd1",
+#                "node-name": "#block212",
+#                "operation": "write",
+#                "action": "stop" },
+#      "timestamp": { "seconds": 1265044230, "microseconds": 450486 } }
+#
 ##
 { 'event': 'BLOCK_IO_ERROR',
   'data': { 'device': 'str', 'node-name': 'str', 'operation': 'IoOperationType',
This page took 0.031861 seconds and 4 git commands to generate.