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 share 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 Otherwise, dmesg and device info please. > BTW: I think libvirt / virsh isn't aware yet of the new vfio way, isn't > it? Correct, need to get it into the kernel and qemu first. Thanks, Alex -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
