Any chance we can get the OP updated to include info on how to work with kernel 5.4 since vfio is built in?
Information on how to add options to systemd-boot would be helpful as well.
I did find some of that information here. That helped me get amd_iommu=on
added correctly, and I think my gpu is isolated properly.
But passing through my pci-e USB card is not working. I get a “Failed to set iommu for container: Operation not permitted.” error. It mentions the iommu group for my usb card, so I know that is the issue.
I updated AppArmor per this post. But it didn’t seem to help.
syslog does show this error:
Jul 29 17:00:55 monolith kernel: [ 169.269934] vfio_iommu_type1_attach_group: No interrupt remapping support. Use the module param "allow_unsafe_interrupts" to enable VFIO IOMMU support on this platform
So I tried to enable allow_unsafe_interrupts=1
the same way I added amd_iommu=on
, but syslog is still logging the same error message after a reboot.
Edit:
Per this Proxmox forum post I was able to add the vfio_iommu_type1.allow_unsafe_interrupts=1
option. I just needed the module name in front, then add it the same way you do amd_iommu=on
.
Now I think my usb card is being passed through, but when I switch monitor inputs to the Windows gpu, I don’t get any output from it. Syslog does show the external hdd I have connected to the usb card being added and removed when I turn on the vm, and/or turn it off.
Hmm…
Edit 2:
So, it seems that part of the no display issue may have just been Windows not showing anything without some kind of input from a keyboard or mouse. I added a QXL display, and after waiting a good while to be sure it booted, I hit a key on my keyboard, and the login screen shows up in the QXL window. If I switch to the GPU input on my monitor, and can see Windows as well.
Now if only my USB card was working again…