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:
QEMU is a large, complex program with many features.  Not all of them are sufficiently useful to customers to justify their support cost. To avoid "you shipped it, you support it" SNAFUs, we must choose the features to ship carefully.

My shot-from-the-hip take on what needs to be done:

1. Identify what exactly to support.

2. Compile out as much of the unsupported stuff as possible.  This may require significant upstream work to improve modularity and compile-time configurability.  Any leftovers will either require non-upstream patches (bad), or "this is not supported" user documentation (worse).

3. Tests to verify the unwanted stuff is gone.

This is almost certainly too much for a single person.  Whoever gets assigned this bug should coordinate a team effort.

Changed the title to be more specific, amidst the rest of the BZs.

Consulted Avi:

> More like an unfeature request. I'm in favour.

> It will take some effort to discover exactly
what's in qemu and what we can safely disable.  We can then evaluate
customer requests to re-enable stuff that we've disabled, in case they
need it.

*** Bug 895240 has been marked as a duplicate of this bug. ***