Bug 1281407
Summary: | Memdev id is not specified when query memdev via QMP | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Yumei Huang <yuhuang> |
Component: | qemu-kvm-rhev | Assignee: | Igor Mammedov <imammedo> |
Status: | CLOSED ERRATA | QA Contact: | Yumei Huang <yuhuang> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | CC: | hhuang, huding, juzhang, michen, mrezanin, qzhang, virt-maint, xfu |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | qemu-kvm-rhev-2.9.0-1.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-08-01 23:29:42 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
Yumei Huang
2015-11-12 12:57:43 UTC
not 7.3 material by now, moving to 7.4 as feature improvement posted fix upstream: https://www.mail-archive.com/qemu-devel@nongnu.org/msg419924.html Upstream commits: e1ff3c6 monitor: fix qmp/hmp query-memdev not reporting IDs of memory backends 3a46410 monitor: reuse user_creatable_add_opts() instead of user_creatable_add() 8a00025 qom: remove unused header Verify: qemu-kvm-rhev-2.9.0-1.el7 kernel-3.10.0-655.el7.x86_64 1. Boot guest with two pc-dimm # /usr/libexec/qemu-kvm -m 4G,slots=40,maxmem=40G \ -drive file=rhel74.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 \ -netdev tap,id=idinWyYp -device virtio-net-pci,mac=42:ce:a9:d2:4d:d7,id=idlbq7eA,netdev=idinWyYp \ -vnc :0 -monitor stdio \ -object memory-backend-ram,id=mem0,size=1G -device pc-dimm,id=dimm0,memdev=mem0\ -object memory-backend-ram,id=mem1,size=1G -device pc-dimm,id=dimm1,memdev=mem1\ -qmp tcp:0:4444,server,nowait 2. Hotplug memory to guest (qemu) object_add memory-backend-ram,id=mem3,host-nodes=1,size=1G,policy=bind (qemu) device_add pc-dimm,id=dimm3,memdev=mem3 3. Check memdev via qmp {'execute': 'qmp_capabilities'} {"return": {}} { "execute": "query-memdev" } {"return": [{"prealloc": false, "host-nodes": [], "size": 1073741824, "merge": true, "dump": true, "policy": "default", "id": "mem1"}, {"prealloc": false, "host-nodes": [], "size": 1073741824, "merge": true, "dump": true, "policy": "default", "id": "mem0"}, {"prealloc": false, "host-nodes": [1], "size": 1073741824, "merge": true, "dump": true, "policy": "bind", "id": "mem3"}]} The memdev id is explicit and correct in qmp. So the bug is fixed. 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/RHSA-2017:2392 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/RHSA-2017:2392 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/RHSA-2017:2392 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/RHSA-2017:2392 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/RHSA-2017:2392 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/RHSA-2017:2392 |