From: Chris Wright <chrisw@sous-sol.org>
To: James Neave <roboj1m@gmail.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
kvm@vger.kernel.org, "Roedel, Joerg" <Joerg.Roedel@amd.com>
Subject: Re: PCI Passthrough, error: The driver 'pci-stub' is occupying your device 0000:08:06.2
Date: Mon, 21 Feb 2011 17:51:19 -0800 [thread overview]
Message-ID: <20110222015119.GY9869@sequoia.sous-sol.org> (raw)
In-Reply-To: <AANLkTi=8RCwjkkT-q7HNBKRCZzRqZqH-QFe6GykEcZBC@mail.gmail.com>
* James Neave (roboj1m@gmail.com) wrote:
> Finally, here is the very latest dmesg:
> http://pastebin.com/9HE61K62
OK, this is an AMD IOMMU box.
[ 0.000000] ACPI: IVRS 00000000cfcf9830 000E0 (v01 AMD RD890S 00202031 AMD 00000000)
It's discovered and enalbed properly:
[ 0.698992] AMD-Vi: Enabling IOMMU at 0000:00:00.2 cap 0x40
[ 0.710287] AMD-Vi: Lazy IO/TLB flushing enabled
> Does anybody know the debug kernel switches for iommu?
Two helpful kernel commandline options are:
amd_iommu_dump debug (and drop "quiet")
The problem is when you attach the device (function) you're getting
stuck up in conflicts with the existing domain for that function.
My guess is that all the functions are behind a PCI to PCI bridge, so the alias
lookup is finding a conflict.
thanks,
-chris
next prev parent reply other threads:[~2011-02-22 1:52 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-05 16:34 PCI Passthrough, error: The driver 'pci-stub' is occupying your device 0000:08:06.2 James Neave
2011-02-07 13:26 ` Daniel P. Berrange
2011-02-08 9:13 ` James Neave
2011-02-08 9:59 ` Kenni Lund
2011-02-08 10:17 ` James Neave
2011-02-12 16:04 ` James Neave
2011-02-14 17:48 ` Alex Williamson
2011-02-21 20:31 ` James Neave
2011-02-21 21:01 ` Alex Williamson
2011-02-21 22:25 ` James Neave
2011-02-21 22:49 ` James Neave
2011-02-21 22:55 ` James Neave
2011-02-21 23:05 ` James Neave
2011-02-22 1:51 ` Chris Wright [this message]
2011-02-22 9:18 ` James Neave
2011-02-22 9:53 ` Roedel, Joerg
2011-02-22 10:11 ` James Neave
2011-02-23 0:11 ` Chris Wright
2011-02-23 19:44 ` James Neave
2011-02-23 20:09 ` James Neave
2011-02-24 9:26 ` James Neave
2011-02-25 0:13 ` Chris Wright
2011-02-25 0:06 ` Chris Wright
2011-02-25 22:47 ` James Neave
2011-02-25 23:02 ` James Neave
2011-02-25 23:09 ` James Neave
2011-02-25 23:31 ` Chris Wright
2011-02-28 13:42 ` James Neave
2011-02-28 15:31 ` Chris Wright
2011-02-28 20:25 ` James Neave
2011-03-01 20:54 ` James Neave
[not found] ` <BANLkTi=ZHpHU=Gd+tTcLysTD3duGY8PPjQ@mail.gmail.com>
2011-05-10 16:00 ` James Neave
2011-02-25 23:14 ` Chris Wright
2011-02-24 23:59 ` Chris Wright
2011-02-21 23:28 ` Chris Wright
2011-02-21 23:50 ` James Neave
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=20110222015119.GY9869@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=Joerg.Roedel@amd.com \
--cc=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=roboj1m@gmail.com \
/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.