PCI connection issues Common problems with PCI passthrough Troubleshooting tips
PCI connection issues Common problems with PCI passthrough Troubleshooting tips
the issue involves moving through all items in the same IOMMU group. you can't skip just one part. your PCI bridge belongs to the same group as your GPUs, audio, and graphics, so passing only the GPU won’t work. instead, use an ACS patched kernel. this is typically a DIY task, but on Arch Linux it’s available in the AUR. install the linux-vfio and linux-vfio-headers packages with an AUR helper, then restart grub and boot with the updated kernel. after applying this, all PCI devices will be placed in their own IOMMU group. once your VM is running and passthrough works, you may face another challenge. NVIDIA prohibits using drivers when a hypervisor is hosting the OS. if you check Device Manager in your Windows VM and see the graphics card showing Error 43, it indicates this problem. you should modify your KVM configuration and set hidden state to on.
I've already tested that kernel version. My VM is set up correctly—NVIDIA drivers installed and configured to change the hardware ID—but I’m still having trouble seeing my host screen while the VM runs. The Windows display works fine, but the Linux display flickers and behaves erratically whenever the VM starts.
I'm still getting this right, but fixing it by changing the HDMI cable helped. It's unclear how a faulty HDMI cable would impact the DVI display—maybe a poor ground connection or something similar. Thanks to everyone who took the time to assist; it really means a lot!
It seems there might have been confusion earlier. Did it get stuck in a boot loop? I've faced that before and struggled a lot to figure it out. It turned out to be a cable issue. Interestingly, it functioned properly on the host but caused problems with the guest.
It wasn't stuck in a boot loop; the problem occurred when the guest device connected (such as an HDMI cable) and caused the host display to flicker, glitch, lose signal, or become unusable. It turned out the issue was a faulty HDMI cable.