blob: b59402392ac6817adf3d0195338ba7ba591d4766 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
|
device: 0.758
graphic: 0.738
vnc: 0.675
semantic: 0.646
register: 0.642
socket: 0.609
risc-v: 0.602
network: 0.602
mistranslation: 0.601
i386: 0.592
performance: 0.581
PID: 0.575
files: 0.574
architecture: 0.561
ppc: 0.548
VMM: 0.535
permissions: 0.522
x86: 0.496
TCG: 0.454
peripherals: 0.434
assembly: 0.422
boot: 0.420
arm: 0.403
kernel: 0.399
user-level: 0.388
hypervisor: 0.372
KVM: 0.362
debug: 0.348
virtual: 0.319
RFE: QMP: report error reason in BLOCK_IO_ERROR message
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
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.
[Expired for QEMU because there has been no activity for 60 days.]
|