From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Wright 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 Message-ID: <20110222015119.GY9869@sequoia.sous-sol.org> References: <20110207132641.GD2665@redhat.com> <1297705728.14733.50.camel@x201> <1298322078.5764.45.camel@x201> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Alex Williamson , kvm@vger.kernel.org, "Roedel, Joerg" To: James Neave Return-path: Received: from sous-sol.org ([216.99.217.87]:59297 "EHLO sequoia.sous-sol.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751343Ab1BVBwG (ORCPT ); Mon, 21 Feb 2011 20:52:06 -0500 Content-Disposition: inline In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: * 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