Just as a comment, I have a similar system, though no ACS, also recently 
updated Arch and noticed a change in libvirt behavior. Specifically, my VM 
which didn't autostart for some reason (there were multiple cryptic errors in 
the journal) started autostarting again. (It worked when I first set it up, 
then stopped several Arch updates ago).  The joys of running Arch and subtle 
interactions....  I assume it will stop again at some future Arch update.

> On Aug 2, 2016, at 3:09 PM, Alex Williamson <alex.l.william...@gmail.com> 
> wrote:
> 
> 
> 
>> On Tue, Aug 2, 2016 at 4:02 PM, Mark <kram...@gmail.com> wrote:
>> Thank you for your input Alex, here is a pastie with some of the info you 
>> were interested in:
>> VM powered off: http://pastie.org/10927534
>> 00:1b.0 is the onboard, 01:00.0 and 01:00.1 are the nvidia gpu/nvidia audio.
> 
> Group 1
> /sys/kernel/iommu_groups/1/devices/0000:00:01.0
> /sys/kernel/iommu_groups/1/devices/0000:01:00.0
> /sys/kernel/iommu_groups/1/devices/0000:01:00.1
> 
> Group 7
> /sys/kernel/iommu_groups/7/devices/0000:00:1b.0
> 
>  
>> Notice in that pastie the driver in use is snd_hda_intel, yet in this lspci 
>> -vvv (with the VM booted up) it is changed to vfio-pci, and they are still 
>> in the same iommu group.
>> VM powered on: http://pastie.org/10927535
> 
> There must be some confusion over what an iommu group is because those are 
> clearly in separate groups with and without the VM running.  The driver is 
> simply the driver in use for the device, it doesn't change the composition of 
> the group.  IOMMU groups are assigned at boot and barring removing and 
> re-adding the device, don't change.  Thanks,
> 
> Alex
> _______________________________________________
> vfio-users mailing list
> vfio-users@redhat.com
> https://www.redhat.com/mailman/listinfo/vfio-users
_______________________________________________
vfio-users mailing list
vfio-users@redhat.com
https://www.redhat.com/mailman/listinfo/vfio-users

Reply via email to