On 18/08/18 09:50, Gary wrote: > On 18/08/18 02:25, Alex Williamson wrote: >> This one is because the GPU is still bound to a VM IOMMU domain, >> probably because the audio function is still bound to the VM and >> userspace bindings are done at the group level. This is a user/libvirt >> error, your scenario has allowed libvirt to attempt to rebind the GPU >> to a host driver while the audio device in the same IOMMU group is >> still bound to vfio-pci and in use by the user. Had intel-iommu not >> hit a BUG_ON, vfio would for the isolation violation. >
Just a quick follow-up. With the switch to manual binding mentioned in the prior email, I no longer need to eject the gfx to successfully shutdown. It looks like it was not the AMD Reset Bug after all, but just another way to cause the libvirt unbinding order issue. Happy Days :) Gary _______________________________________________ vfio-users mailing list vfio-users@redhat.com https://www.redhat.com/mailman/listinfo/vfio-users
