Bug 1612114
| Summary: | Anonymous BlockBackends are missing in query-blockstats | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Kevin Wolf <kwolf> |
| Component: | qemu-kvm-rhev | Assignee: | Kevin Wolf <kwolf> |
| Status: | CLOSED ERRATA | QA Contact: | CongLi <coli> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.6 | CC: | chayang, coli, hhan, juzhang, lmen, michen, ngu, pkrempa, qzhang, virt-maint, xuzhang, yafu, yhong, yisun |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | qemu-kvm-rhev-2.12.0-10.el7 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-11-01 11:13:16 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Kevin Wolf
2018-08-03 13:43:44 UTC
Fix included in qemu-kvm-rhev-2.12.0-10.el7 Verified this bug on: qemu-kvm-rhev-2.12.0-10.el7.x86_64
1. blockstats with -drive if=virtio --> device is virtio, there is filed 'qdev' of virtio device: "qdev": "/machine/peripheral-anon/device[0]/virtio-backend" via 'query-blockstats', which same as 'query-block'.
QEMU CML: -drive driver=null-co,if=virtio
{ "execute": "query-blockstats"}
{
"return": [
{
"device": "virtio0",
"stats": {
"flush_total_time_ns": 0,
"wr_highest_offset": 0,
"wr_total_time_ns": 0,
"failed_wr_operations": 0,
"failed_rd_operations": 0,
"wr_merged": 0,
"wr_bytes": 0,
"timed_stats": [
],
"failed_flush_operations": 0,
"account_invalid": true,
"rd_total_time_ns": 44141,
"flush_operations": 0,
"wr_operations": 0,
"rd_merged": 0,
"rd_bytes": 512,
"invalid_flush_operations": 0,
"account_failed": true,
"idle_time_ns": 38804814834,
"rd_operations": 1,
"invalid_wr_operations": 0,
"invalid_rd_operations": 0
},
"node-name": "#block022",
"qdev": "/machine/peripheral-anon/device[0]/virtio-backend"
},
...}
2. blockstats with -drive if=none --> device is none, the output is same as 'query-block'.
QEMU CML: -drive driver=null-co,if=none
{ "execute": "query-blockstats"}
{
"return": [
{
"device": "none0",
"stats": {
"flush_total_time_ns": 0,
"wr_highest_offset": 0,
"wr_total_time_ns": 0,
"failed_wr_operations": 0,
"failed_rd_operations": 0,
"wr_merged": 0,
"wr_bytes": 0,
"timed_stats": [
],
"failed_flush_operations": 0,
"account_invalid": true,
"rd_total_time_ns": 0,
"flush_operations": 0,
"wr_operations": 0,
"rd_merged": 0,
"rd_bytes": 0,
"invalid_flush_operations": 0,
"account_failed": true,
"rd_operations": 0,
"invalid_wr_operations": 0,
"invalid_rd_operations": 0
},
"node-name": "#block099"
},
...}
3. blockstats with -blockdev --> no device info, which same as 'query-block'.
QEMU CML: -blockdev driver=null-co,node-name=null
{ "execute": "query-blockstats"}
{...}
4. blockstats with -blockdev and -device --> device is null, there is filed 'qdev' of virtio device: "qdev": ""qdev": "/machine/peripheral/virtio0/virtio-backend"" via 'query-blockstats', which same as 'query-block'.
QEMU CML: -blockdev driver=null-co,node-name=null -device virtio-blk,drive=null,id=virtio0
{ "execute": "query-blockstats"}
{
"return": [
...
{
"device": "",
"stats": {
"flush_total_time_ns": 0,
"wr_highest_offset": 0,
"wr_total_time_ns": 0,
"failed_wr_operations": 0,
"failed_rd_operations": 0,
"wr_merged": 0,
"wr_bytes": 0,
"timed_stats": [
],
"failed_flush_operations": 0,
"account_invalid": false,
"rd_total_time_ns": 42959,
"flush_operations": 0,
"wr_operations": 0,
"rd_merged": 0,
"rd_bytes": 512,
"invalid_flush_operations": 0,
"account_failed": false,
"idle_time_ns": 40574708168,
"rd_operations": 1,
"invalid_wr_operations": 0,
"invalid_rd_operations": 0
},
"node-name": "null",
"qdev": "/machine/peripheral/virtio0/virtio-backend"
}
]
}
qemu-iotests of 227 pass.
227
Passed all 1 tests
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:3443 |