From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 81841] amd-iommu: kernel BUG & lockup after shutting down KVM guest using PCI passthrough/PCIe bridge
Date: Tue, 12 Aug 2014 10:30:30 +0000 [thread overview]
Message-ID: <bug-81841-28872-ROcN4XOAyN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-81841-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=81841
--- Comment #13 from Marti Raudsepp <marti@juffo.org> ---
(In reply to Joerg Roedel from comment #12)
> Thanks, Joerg
Indeed. Thanks, Joerg. And thanks everyone else too, you have been very
helpful!
I didn't have v3.13 sources handy, but I applied the attachment 146311 patch to
3.16.0 and it fixes the problem. (I verified that unpatched 3.16.0 also
crashes).
I can start & shut down the VM multiple times without crashing the host and PCI
passthrough works as expected.
Feel free to add
Tested-by: Marti Raudsepp <marti@juffo.org>
(In reply to Alex Williamson from comment #7)
> Note that it's not required to assign all the devices, they simply need to
> be detached from host drivers (ie. bound to pci-stub or vfio-pci).
This approach also works; I think I will go this route for the production
setup. Seems that we don't actually need any of the devices in the same IOMMU
group.
(In reply to Joel Schopp from comment #10)
> > AMD would need to confirm it.
>
> I don't have an answer for you offhand. Let me do some digging and get you
> an answer.
I am sorry if I sounded frustrated or arrogant earlier. Any update on this?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-08-12 10:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 14:45 [Bug 81841] New: amd-iommu: kernel BUG & lockup after shutting down KVM guest using PCI passthrough/PCIe bridge bugzilla-daemon
2014-08-07 14:46 ` [Bug 81841] " bugzilla-daemon
2014-08-07 14:47 ` bugzilla-daemon
2014-08-07 14:47 ` bugzilla-daemon
2014-08-07 15:30 ` bugzilla-daemon
2014-08-07 16:25 ` bugzilla-daemon
2014-08-07 17:56 ` bugzilla-daemon
2014-08-07 18:11 ` bugzilla-daemon
2014-08-07 18:53 ` bugzilla-daemon
2014-08-07 19:47 ` bugzilla-daemon
2014-08-08 2:48 ` bugzilla-daemon
2014-08-08 10:19 ` bugzilla-daemon
2014-08-12 9:36 ` bugzilla-daemon
2014-08-12 10:30 ` bugzilla-daemon [this message]
2014-08-12 10:42 ` bugzilla-daemon
2014-08-12 14:53 ` bugzilla-daemon
2014-08-12 15:09 ` bugzilla-daemon
2014-08-12 15:20 ` bugzilla-daemon
2014-09-01 9:30 ` bugzilla-daemon
2014-09-09 7:39 ` bugzilla-daemon
2014-09-09 14:58 ` bugzilla-daemon
2014-09-09 15:25 ` bugzilla-daemon
2014-10-02 13:30 ` bugzilla-daemon
2014-10-10 15:58 ` bugzilla-daemon
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-81841-28872-ROcN4XOAyN@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.