-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
rhel-9.6
-
None
-
None
-
Moderate
-
rhel-virt-storage
-
None
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
-
x86_64
-
None
What were you trying to do that didn't work?
Try to use block latency histgram
$ virsh qemu-monitor-command rhel9 --pretty '{"execute": "query-block" }' | grep virtio-backend $ virsh qemu-monitor-command rhel9 --pretty '{ "execute": "block-latency-histogram-set", "arguments": { "id": "/machine/peripheral/virtio-disk0/virtio-backend", "boundaries-read": [10000000, 100000000, 1000000000, 10000000000, 60000000000], "boundaries-write": [10000000, 100000000, 1000000000, 10000000000, 60000000000], "boundaries-flush": [10000000, 100000000, 1000000000, 10000000000, 60000000000] } }' $ sleep 30 $ virsh qemu-monitor-command rhel9 --pretty '{ "execute": "block-latency-histogram-set", "arguments": { "id": "/machine/peripheral/virtio-disk0/virtio-backend", "boundaries-read": [], "boundaries-write": [], "boundaries-flush": [] } }'
What is the impact of this issue to you?
The feature is not supported officially for customer use, but its useful for suport when troubleshooting issues.
Please provide the package NVR for which the bug is seen:
9.1.0-15.el9_6.9
How reproducible is this bug?:
Always
Expected results
Be able to collect statistics without crashing the VM 
Actual results
The command itself works, I can collect the data even. But shortly after qemu segfaults.
- blocks
-
RHEL-131335 [RFE] Add libvirt API for block latency histograms
-
- New
-
- is related to
-
-
- New
-
