Bug 1664302 - RFE: Make device options QAPI introspectable
Summary: RFE: Make device options QAPI introspectable
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux Advanced Virtualization
Classification: Red Hat
Component: qemu-kvm
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Markus Armbruster
QA Contact: Yiqian Wei
URL:
Whiteboard:
Depends On:
Blocks: 1498955
TreeView+ depends on / blocked
 
Reported: 2019-01-08 11:28 UTC by Erik Skultety
Modified: 2022-11-01 02:56 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-15 07:32:50 UTC
Type: Feature Request
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Erik Skultety 2019-01-08 11:28:39 UTC
Description of problem:
QAPI lacks the definition of the return object type for the device_add command, thus making it impossible for libvirt to traverse the schema and use appropriate device feature flags.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Markus Armbruster 2019-01-09 09:46:58 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')

Comment 3 Ademar Reis 2020-02-05 22:53:39 UTC
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

Comment 6 RHEL Program Management 2021-03-15 07:32:50 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.