RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Qdev should be able to output which devices are available on the system, and which properties each device have. Our only current option is to parse -help output, which is cumbersome.

-device [dev] ? is a suggestion for command line switch, but the mechanics of it are pretty open.

There's "-device \?" and "-device DRIVER,\?".  But what we really want here is a solution in QMP.

Related bug 647516.

Buttefingers... related bug 557939.

QMP solution is related to (intertwined with?) upstream QAPI schema work.  Moving to RHEL-7.

Some relevant QMP commands have been created since comment#5:

* qom-list-types

* device-list-properties

As far as I can tell, libvirt already uses them.

However, they don't quite cover everything in -device help.  Missing
bits include:

* Bus type: DeviceClass member bus_type

* Alias name: DeviceClass method qdev_class_get_alias()

* Device categories: DeviceClass member categories (new upstream, not
  yet in RHEL-7)

* Description: DeviceClass member desc

* no-user: DeviceClass member no_user

Not sure libvirt really needs all of them.

According to comment #9, close this bug.


qdev structure/properties are defined in qapi-schema.json, the content will be dumped out for management when we finished bz 557939.

*** This bug has been marked as a duplicate of bug 557939 ***