From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 42635] New: PCIe passthrough broken with AMD iommu after s2disk / resume
Date: Mon, 23 Jan 2012 09:35:19 GMT [thread overview]
Message-ID: <bug-42635-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=42635
Summary: PCIe passthrough broken with AMD iommu after s2disk /
resume
Product: Virtualization
Version: unspecified
Kernel Version: 3.1
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
AssignedTo: virtualization_kvm@kernel-bugs.osdl.org
ReportedBy: kmueller@justmail.de
Regression: No
A PCIe ethernet device is passed through to the guest and runs fine. Some time
later, the guest is shutdown (e.g. virsh shutdown guest) and the host is
suspended (s2disk) and resumed again. The guest is started again (and it starts
fine), but the device in the guest isn't working any more (it can be seen, it
can be pinged itself but nothing is reachable outside the device. The rx or tx
counters of the ifconfig output are always 0.
If the guest is shutdown and the device is bound to the host, it's working as
expected. If the device is afterwards bound to the guest again, it doesn't work
as before in the guest after resume.
kernel: 3.1 / 64bit / smp
kvm: 1.0
board: GA-990XA-UD3
If you need more information, I can provide them - feel free to ask!
Regards,
Klaus
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next reply other threads:[~2012-01-23 9:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 9:35 bugzilla-daemon [this message]
2012-01-23 15:01 ` [Bug 42635] PCIe passthrough broken with AMD iommu after s2disk / resume bugzilla-daemon
2012-01-23 16:18 ` bugzilla-daemon
2012-04-03 7:27 ` 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-42635-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