From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Hartmann Subject: Re: AMD KVM Pci Passthrough reports device busy Date: Tue, 05 Jun 2012 18:55:42 +0200 Message-ID: <4FCE3A0E.5020806@01019freenet.de> References: <1338867845.23475.168.camel@bling.home> <201206051039.q55AdXda002609@mail.maya.org> <1338906425.23475.186.camel@bling.home> <201206051517.q55FHU5B002790@mail.maya.org> <4FCE2C89.90209@01019freenet.de> <1338913159.23475.212.camel@bling.home> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Andreas Hartmann , Joerg.Roedel@amd.com, Chris Sanders , kvm@vger.kernel.org To: Alex Williamson Return-path: Received: from mout4.freenet.de ([195.4.92.94]:45300 "EHLO mout4.freenet.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754529Ab2FEQ7F (ORCPT ); Tue, 5 Jun 2012 12:59:05 -0400 In-Reply-To: <1338913159.23475.212.camel@bling.home> Sender: kvm-owner@vger.kernel.org List-ID: Alex Williamson wrote: [...] > Yep, I think the previous suggestion about reloading vfio_iommu_type1 > with allow_unsafe_interrupts=1 will solve it. Yes! Works now. Success!!!!! Works means: Device is seen in VM. I couldn't test it up to now, because I don't have any driver in the VM for this device. > It has nothing to do with > file permissions, you're getting EPERM at the point where we set the > iommu type, which enables access to devices. By default we want an > iommu which protects against malicious MSI attacks, which requires > interrupt remapping on x86. Joerg has been working to add this for AMD > since the hardware supports it, but for now, the above options lets us > bypass the check. Thanks, Now, I have to check my problem with the filesystem first, which isn't cleanly unmounted. I suspect a few missing options for kernel compile. Next will be fglrx :-) for 3.4 Hmmm, is there a chance to get your extension isolated to get it compiled for 3.1, too? Thanks, kind regards, Andreas