Bug 2233620
Summary: | [RFE] AMD Genoa - Add libvirt support for EPYC-Genoa CPU Model | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | Bandan Das <bdas> |
Component: | libvirt | Assignee: | Tim Wiederhake <twiederh> |
libvirt sub component: | General | QA Contact: | Luyao Huang <lhuang> |
Status: | CLOSED MIGRATED | Docs Contact: | |
Severity: | medium | ||
Priority: | medium | CC: | coli, jdenemar, jsuchane, lmen, virt-maint, zixchen |
Version: | 9.4 | Keywords: | FutureFeature, MigratedToJIRA, Triaged |
Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-09-22 18:10:55 UTC | Type: | Story |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | 9.8.0 |
Embargoed: |
Description
Bandan Das
2023-08-22 18:17:02 UTC
Bandan - since you set ITR, I assume you will follow-up, but need to assign this to you so that we don't have issues assigned an ITR w/o an owner. (In reply to John Ferlan from comment #2) > Bandan - since you set ITR, I assume you will follow-up, but need to assign > this to you so that we don't have issues assigned an ITR w/o an owner. Unfortunately, I am not the right person to keep track of it. I have unset ITR and reset assignee. Hopefully, someone who is more familiar with libvirt upstream can take a look. commit bfe53e9145cd5996a791c5caff0686572b850f82 Author: Tim Wiederhake <twiederh> AuthorDate: Wed Sep 6 13:13:34 2023 +0200 Commit: Tim Wiederhake <twiederh> CommitDate: Wed Sep 6 20:35:45 2023 +0200 cpu_map: Add cpu model EPYC Genoa This was added in qemu commit 166b174188. No additional features had to be added to libvirt. Signed-off-by: Tim Wiederhake <twiederh> Reviewed-by: Martin Kletzander <mkletzan> v9.7.0-126-gbfe53e9145 Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |