diff options
author | Luiz Capitulino <lcapitulino@redhat.com> | 2014-09-11 10:25:48 -0400 |
---|---|---|
committer | Kevin Wolf <kwolf@redhat.com> | 2014-09-11 17:14:13 +0200 |
commit | 624ff5736ef9245bb8070400ccaf65857b6d1c38 (patch) | |
tree | c7c92007710a861fc6d8f75f7f17261688ddc558 /block.c | |
parent | 745a9bb9cdcdcc50219d14704477c5cd678c4a7e (diff) | |
download | qemu-624ff5736ef9245bb8070400ccaf65857b6d1c38.zip |
block: extend BLOCK_IO_ERROR with reason string
BLOCK_IO_ERROR events are logged by libvirt, which helps with
post mortem analysis of guests. However, one information that
we miss today is a human readable string describing the cause
of the I/O error.
This commit adds that string it to BLOCK_IO_ERROR. Note that
this string is a debugging aid for humans, meaning that it
should not parsed by applications.
Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'block.c')
-rw-r--r-- | block.c | 3 |
1 files changed, 2 insertions, 1 deletions
@@ -3647,7 +3647,8 @@ static void send_qmp_error_event(BlockDriverState *bs, ac = is_read ? IO_OPERATION_TYPE_READ : IO_OPERATION_TYPE_WRITE; qapi_event_send_block_io_error(bdrv_get_device_name(bs), ac, action, bdrv_iostatus_is_enabled(bs), - error == ENOSPC, &error_abort); + error == ENOSPC, strerror(error), + &error_abort); } /* This is done by device models because, while the block layer knows |