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 1714745 - Fail to launch AMD SEV VM with assigned PCI device
Summary: Fail to launch AMD SEV VM with assigned PCI device
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: qemu-kvm
Version: 8.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: 8.0
Assignee: Virtualization Maintenance
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1667249
Blocks: 1615620 1731442
TreeView+ depends on / blocked
 
Reported: 2019-05-28 18:33 UTC by Oneata Mircea Teodor
Modified: 2020-02-12 14:56 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1667249
Environment:
Last Closed: 2019-10-03 19:20:11 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 2 Gary R Hook (AMD) 2019-05-30 22:14:31 UTC
I believe this is a duplicate of 1667249. Can you check, please?

Comment 3 Rick Barry 2019-05-31 12:32:36 UTC
(In reply to Gary R Hook from comment #2)
> I believe this is a duplicate of 1667249. Can you check, please?

Hi Gary, this BZ is a z-stream clone requesting the 8.1.0 fix (1667249) be back-ported to 8.0.0.z, if such a back-port is feasible.

Comment 4 Gary R Hook (AMD) 2019-05-31 21:33:34 UTC
There it is... I see that now. My apologies.

Comment 5 Karen Noel 2019-06-01 23:59:52 UTC
I set the Target Release to 8.0 to make it more obvious this BZ is for 8.0 z-stream.

Comment 7 Gary R Hook (AMD) 2019-08-28 19:28:37 UTC
The two patches that make up 1667249 apply cleanly onto the rhel-8.0.0 branch (as of today). So little or no work will be required to accomplish this.

How do we move this along as a z-stream fix? I'm unclear on the next steps.

Comment 8 Gary R Hook (AMD) 2019-09-12 21:22:42 UTC
Posted to rhvirt-patches

Comment 9 Danilo de Paula 2019-09-13 17:04:08 UTC
Last time I've heard, there won't be another RHEL-8.0.0.z update.

With that in mind, I believe this should be closed as WONTFIX. Unless plans changed.

Comment 11 Gary R Hook (AMD) 2019-10-03 19:20:11 UTC
Final decision: there will not be another batch update for 8.0. Therefore, closing as WONTFIX.


Note You need to log in before you can comment on or make changes to this bug.