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.
Bug 2066824 - Aarch64: Drop unsupported CPU types
Summary: Aarch64: Drop unsupported CPU types
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: qemu-kvm
Version: 9.1
Hardware: aarch64
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 9.1
Assignee: Guowen Shan
QA Contact: Zhenyu Zhang
URL:
Whiteboard:
: 2066823 (view as bug list)
Depends On: 2060839
Blocks: 1924294
TreeView+ depends on / blocked
 
Reported: 2022-03-22 14:32 UTC by Andrew Jones
Modified: 2022-11-15 10:22 UTC (History)
11 users (show)

Fixed In Version: qemu-kvm-7.0.0-8.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2064757
Environment:
Last Closed: 2022-11-15 09:54:33 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gitlab redhat/centos-stream/src qemu-kvm merge_requests 97 0 None opened RHEL-only: AArch64: Drop unsupported CPU types 2022-06-02 08:48:26 UTC
Gitlab redhat/rhel/src/qemu-kvm qemu-kvm merge_requests 192 0 None None None 2022-06-01 17:49:15 UTC
Red Hat Issue Tracker RHELPLAN-116406 0 None None None 2022-03-22 14:46:55 UTC
Red Hat Product Errata RHSA-2022:7967 0 None None None 2022-11-15 09:55:46 UTC

Description Andrew Jones 2022-03-22 14:32:24 UTC 
+++ This bug was initially created as a clone of Bug #2064757 +++

We rebase qemu-kvm regularly to lower backporting costs and to support new features. As QEMU 7.0.0 is release we are going to rebase to this version for RHEL 9.
Comment 1 Andrew Jones 2022-03-22 14:54:58 UTC 
*** Bug 2066823 has been marked as a duplicate of this bug. ***
Comment 3 Andrew Jones 2022-05-30 13:26:52 UTC 
Unfortunately, even though we can drop five CPU types, keeping only three total, because we still keep at least one TCG CPU type, we don't save anything with respect to code size. I tried to remove files that appeared to provide TCG support for 32-bit CPU types, but the TCG code is too intertwined. I was able to remove target/arm/cpu_tcg.c from the build, but it was mostly commented out for RHEL already and its functions are only initializers with almost no logic anyway.

So, the question is, do we still want to remove unsupported CPU types just to make sure nobody uses them?
Comment 6 Andrew Jones 2022-06-01 09:09:27 UTC 
(In reply to Andrew Jones from comment #3)
> So, the question is, do we still want to remove unsupported CPU types just
> to make sure nobody uses them?

We discussed this in our weekly call. We've decided, yes, we want to enforce our decision to not support certain CPU types by removing them.
Comment 7 Nitesh Narayan Lal 2022-06-01 13:26:37 UTC 
(In reply to Andrew Jones from comment #6)
> (In reply to Andrew Jones from comment #3)
> > So, the question is, do we still want to remove unsupported CPU types just
> > to make sure nobody uses them?
> 
> We discussed this in our weekly call. We've decided, yes, we want to enforce
> our decision to not support certain CPU types by removing them.

Luiz, Drew, is it possible to set the DTM for this so that QE can plan the testing accordingly?
Thanks
Comment 22 Guowen Shan 2022-07-05 00:05:38 UTC 
The fix will be merged through bug 2060839 and MR-94. What we need to
do is test it after MR-94 gets merged.

https://bugzilla.redhat.com/show_bug.cgi?id=2060839
https://gitlab.com/redhat/centos-stream/src/qemu-kvm/-/merge_requests/94
Comment 23 Guowen Shan 2022-07-08 00:29:22 UTC 
MR-94 for bug 2060839 is merged to qemu-kvm-7.0.0-8.el9. Move this to ON_QA.
Comment 28 errata-xmlrpc 2022-11-15 09:54:33 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: qemu-kvm security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:7967
Note You need to log in before you can comment on or make changes to this bug.