On 10/08/2015 at 07:30 PM Joerg Roedel wrote: > On Wed, Oct 07, 2015 at 07:02:32PM +0200, Andreas Hartmann wrote: >> Binding the device to vfio isn't a problem (it's done before the vm is >> started). The problem occurs during start of qemu-system-x86_64 (2.3.0). >> >> The attached dmesg.out doesn't show the trace, but the desired iommu dump. >> >>> Also, which device are you trying to attach to the guest (pci >>> bus/device/function)? >> >> See attached ath9k.device. > > Hmm, can you also test this again with the v4.3-rc4 please? The device > you are attaching has its own group and no aliases, so I really can't > see how the trace could happen, and I can't reproduce it here either. Unchanged - this time hard locked machine and no trace at all because of data loss after reboot :-(. Btw: Linux 4.2 doesn't show this problem. Nevertheless I'll try to get a trace - maybe I'm lucky and the machine doesn't lock up completely another time :-). Regards, Andreas -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
