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.

Description of problem:

In the near future QMP will have self-description support, which basically means that it will be able to dump all protocol related information such as command names, arguments, types, errors, etc.

Libvirt will have to use that feature so that it fully offers back compatibility support.

I don't see any need to use this feature at this point in time, since there are no backwards incompatible changes in QMP that we need to detect.

Yes, this is a future feature, likely to be included only in rhel7.0.

We have bug 557939 for QMP, so I figured that it would be good to have a BZ for libvirt too, so that you can track progress and update libvirt when time comes.

Not sure if this is the best way to handle future features.

Closing because there's no actionable work todo be done. libvirt upstream will make use of QMP self-description, as & when a particular need arises. No obvious need is visible at this time.