aboutsummaryrefslogtreecommitdiff
path: root/qapi
diff options
context:
space:
mode:
authorKevin Wolf <kwolf@redhat.com>2016-09-29 16:47:58 +0200
committerKevin Wolf <kwolf@redhat.com>2016-10-07 13:34:22 +0200
commit2bf7e10f78ebf67fbef364dce37ae844ba3c7a62 (patch)
treeba6e52cc41342bcf277d5c1702ad0293d8769532 /qapi
parentc5f3014b82adc0e8f50bf5052031503d3467bea3 (diff)
downloadqemu-2bf7e10f78ebf67fbef364dce37ae844ba3c7a62.zip
qemu-2bf7e10f78ebf67fbef364dce37ae844ba3c7a62.tar.gz
qemu-2bf7e10f78ebf67fbef364dce37ae844ba3c7a62.tar.bz2
block: Add node name to BLOCK_IO_ERROR event
The event currently only contains the BlockBackend name. However, with anonymous BlockBackends, this is always the empty string. Add the node name so that the user can still see which block device caused the event. Signed-off-by: Kevin Wolf <kwolf@redhat.com> Reviewed-by: Max Reitz <mreitz@redhat.com>
Diffstat (limited to 'qapi')
-rw-r--r--qapi/block-core.json10
1 files changed, 8 insertions, 2 deletions
diff --git a/qapi/block-core.json b/qapi/block-core.json
index 9d797b8..3d3c0be 100644
--- a/qapi/block-core.json
+++ b/qapi/block-core.json
@@ -2545,7 +2545,13 @@
#
# Emitted when a disk I/O error occurs
#
-# @device: device name
+# @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.
+#
+# @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. (Since: 2.8)
#
# @operation: I/O operation
#
@@ -2566,7 +2572,7 @@
# Since: 0.13.0
##
{ 'event': 'BLOCK_IO_ERROR',
- 'data': { 'device': 'str', 'operation': 'IoOperationType',
+ 'data': { 'device': 'str', 'node-name': 'str', 'operation': 'IoOperationType',
'action': 'BlockErrorAction', '*nospace': 'bool',
'reason': 'str' } }