From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Hartmann Subject: Re: AMD KVM Pci Passthrough reports device busy Date: Wed, 06 Jun 2012 00:02:03 +0200 Message-ID: <4FCE81DB.90802@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> <4FCE3A0E.5020806@01019freenet.de> <1338921804.23475.230.camel@bling.home> <201206052038.q55Kbxmx002741@mail.maya.org> <1338930560.23475.232.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 mout2.freenet.de ([195.4.92.92]:59442 "EHLO mout2.freenet.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751968Ab2FEWEw (ORCPT ); Tue, 5 Jun 2012 18:04:52 -0400 In-Reply-To: <1338930560.23475.232.camel@bling.home> Sender: kvm-owner@vger.kernel.org List-ID: Alex Williamson wrote: > On Tue, 2012-06-05 at 22:37 +0200, Andreas Hartmann wrote: >> Alex Williamson wrote: >>> On Tue, 2012-06-05 at 18:55 +0200, Andreas Hartmann wrote: >>>> 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. >> >> Well, I've got another problem now with 3.4: I can't pass through my >> PCIe device any more, which works fine without any problem with 3.1.10. >> I'm getting the following error in 3.4: >> >> Failed to assign irq for "hostdev0": Input/output error >> Perhaps you are assigning a device that shares an IRQ with another device? >> qemu-kvm: -device pci-assign,host=04:00.0,id=hostdev0,configfd=19,bus=pci.0,addr=0x6: Device 'pci-assign' could not be initialized >> >> options kvm allow_unsafe_assigned_interrupts=1 is set. >> >> There are shared IRQ's - but that's the same in 3.1.10. >> >> This VM is started with libvirt (virsh) the old fashioned way with the >> old qemu-kvm tool. Doesn't this work any more? > > Does this help: https://lkml.org/lkml/2012/6/1/261 Yes - this fixed the problem! Thanks, Andreas