[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug 1284090] Re: RFE: QMP: report error reason in BLOCK_IO_ERROR messag
From: |
Thomas Huth |
Subject: |
[Bug 1284090] Re: RFE: QMP: report error reason in BLOCK_IO_ERROR message |
Date: |
Fri, 20 Nov 2020 18:37:55 -0000 |
The QEMU project is currently considering to move its bug tracking to another
system. For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting older bugs to "Incomplete" now.
If you still think this bug report here is valid, then please switch the state
back to "New" within the next 60 days, otherwise this report will be marked as
"Expired". Or mark it as "Fix Released" if the problem has been solved with a
newer version of QEMU already. Thank you and sorry for the inconvenience.
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1284090
Title:
RFE: QMP: report error reason in BLOCK_IO_ERROR message
Status in QEMU:
Incomplete
Bug description:
when a disk drive is configured with the error policy enospc for write
errors, the monitoring client needs a way to distinguish
betwwen generic I/O error and the I/O error for space exausted.
The JSON QMP protocol lacks this information: the BLOCK_IO_ERROR
message does not provide a reason or code for the error verified, so
the monitoring client cannot distinguish the source of the errors.
verified against git 105a060188dc6fdd4551571a966514d1a5f6815a
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1284090/+subscriptions
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Bug 1284090] Re: RFE: QMP: report error reason in BLOCK_IO_ERROR message,
Thomas Huth <=