From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 105311] AMD-Vi: Event logged [INVALID_DEVICE_REQUEST device=00:14.0 address=0x000000fdf9103300 flags=0x0600]
Date: Sat, 03 Oct 2015 22:51:19 +0000 [thread overview]
Message-ID: <bug-105311-28872-gbMLrolaLa@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-105311-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=105311
Alex Williamson <alex.williamson@redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alex.williamson@redhat.com
--- Comment #8 from Alex Williamson <alex.williamson@redhat.com> ---
Unless you're trying to do PCI device assignment, KVM doesn't have any
dependency or interaction with the IOMMU. General IOMMU issues would probably
be better served reporting them to the IOMMU mailing list:
https://lists.linuxfoundation.org/mailman/listinfo/iommu
If you are attempting to do PCI device assignment, please provide details
including VM configuration (XML or qemu launch scripts) and dmesg prior to the
AMD-Vi spew.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2015-10-03 22:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 15:53 [Bug 105311] New: AMD-Vi: Event logged [INVALID_DEVICE_REQUEST device=00:14.0 address=0x000000fdf9103300 flags=0x0600] bugzilla-daemon
2015-10-01 15:54 ` [Bug 105311] " bugzilla-daemon
2015-10-01 15:54 ` bugzilla-daemon
2015-10-01 15:55 ` bugzilla-daemon
2015-10-01 15:55 ` bugzilla-daemon
2015-10-03 17:39 ` bugzilla-daemon
2015-10-03 17:42 ` bugzilla-daemon
2015-10-03 17:48 ` bugzilla-daemon
2015-10-03 22:51 ` bugzilla-daemon [this message]
2015-10-03 23:39 ` bugzilla-daemon
2015-10-03 23:55 ` bugzilla-daemon
2015-10-04 0:20 ` bugzilla-daemon
2015-10-04 7:24 ` bugzilla-daemon
2015-10-04 7:25 ` bugzilla-daemon
2016-09-24 19:40 ` 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-105311-28872-gbMLrolaLa@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).