Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

We need this fix

https://lists.gnu.org/archive/html/qemu-devel/2016-04/msg03402.html

Actually I just noticed we don't yet have THP enabled on RHELSA, at least not for 7.3. So in the least this can be deferred for that. However Eric found a problem with the patch I point out in comment 0, so that may be changing upstream as well. Anyway, reassigning to Eric and deferring.

We now have https://lists.gnu.org/archive/html/qemu-devel/2016-04/msg03402.html. As for the issue this patch induces on multiple platform device passthrough it should be addressed in a separate BZ I think.

This BZ is being closed as CURRENTRELEASE because it falls
into the following criteria:

o It's an aarch64 virt BZ for RHEL7
o It's on ON_QA or VERIFIED state
o Resolution seems to be in place for some years

If you have objections, please add a comment or re-open the BZ.