Bug 1664302
| Summary: | RFE: Make device options QAPI introspectable | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux Advanced Virtualization | Reporter: | Erik Skultety <eskultet> |
| Component: | qemu-kvm | Assignee: | Markus Armbruster <armbru> |
| qemu-kvm sub component: | QMP Monitor and CLI | QA Contact: | Yiqian Wei <yiwei> |
| Status: | CLOSED WONTFIX | Docs Contact: | |
| Severity: | medium | ||
| Priority: | unspecified | CC: | chayang, coli, jinzhao, juzhang, rbalakri, virt-maint, yhong |
| Version: | --- | Keywords: | FutureFeature, Triaged |
| Target Milestone: | rc | Flags: | ribarry:
mirror+
|
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-03-15 07:32:50 UTC | Type: | Feature Request |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1498955 | ||
|
Description
Erik Skultety
2019-01-08 11:28:39 UTC
Known gap in QMP introspection, see slide 39 of http://www.linux-kvm.org/images/7/7a/02x05-Aspen-Markus_Armbruster-QEMU_interface_introspection.pdf Related gaps: netdev_add (slide 38), and QAPI type 'any' used for qom-get, qom-set, object-add, query-cpu-model-expansion & friends (type CpuModelInfo member 'props') QEMU has been recently split into sub-components and as a one-time operation to avoid breakage of tools, we are setting the QEMU sub-component of this BZ to "General". Please review and change the sub-component if necessary the next time you review this BZ. Thanks After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened. |