From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 203957] New: AGESA 0.0.7.2. based BIOS update broke IOMMU redirection
Date: Sun, 23 Jun 2019 00:22:56 +0000 [thread overview]
Message-ID: <bug-203957-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=203957
Bug ID: 203957
Summary: AGESA 0.0.7.2. based BIOS update broke IOMMU
redirection
Product: Virtualization
Version: unspecified
Kernel Version: 5.1.12
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: anjan@momi.ca
Regression: No
Created attachment 283395
--> https://bugzilla.kernel.org/attachment.cgi?id=283395&action=edit
pci patch that fixes pci passthrough for newer AMD Bios
Hello,
I am using a "AMD Ryzen 7 1700" on a "GA-AX370-Gaming 5". I recently updated to
the latest BIOS from an older BIOS. Updating my bios broke PCI passthrough.
Everytime I would try to start my virtual machine from virt-manager, I would
get "Unknown PCI header type '127'" and my virtual machines would refuse to
boot.
It seems this is a common issue:
1.
https://forum.manjaro.org/t/solved-agesa-0-0-7-2-based-bios-update-broke-iommu-redirection/88909
2. https://www.reddit.com/r/Amd/comments/bh3qqz/agesa_0072_pci_quirk/
However, following the solution in thread 1, I was able to fix pci passthrough.
I simply applied this patch:
https://clbin.com/VCiYJ
to kernel 5.1.12 and it fixed PCI passthrough. This patch is also attached to
this bug as a mirror.
It would be great if this patch could get merged into upstream. Please let me
know if I can provide any further information or assist in any way to make this
happen.
Thank you.
--
You are receiving this mail because:
You are watching the assignee of the bug.
reply other threads:[~2019-06-23 0:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-203957-28872@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).