From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 42635] PCIe passthrough broken with AMD iommu after s2disk / resume
Date: Mon, 23 Jan 2012 15:01:29 GMT [thread overview]
Message-ID: <201201231501.q0NF1Twj030113@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-42635-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=42635
Alex Williamson <alex.williamson@redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alex.williamson@redhat.com
--- Comment #1 from Alex Williamson <alex.williamson@redhat.com> 2012-01-23 15:01:29 ---
Between the first and second paragraph, you seem to be saying that the device
never works in the guest on the second invocation of the guest. Is that true?
What is the device?
--
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 prev parent reply other threads:[~2012-01-23 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 9:35 [Bug 42635] New: PCIe passthrough broken with AMD iommu after s2disk / resume bugzilla-daemon
2012-01-23 15:01 ` bugzilla-daemon [this message]
2012-01-23 16:18 ` [Bug 42635] " 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=201201231501.q0NF1Twj030113@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