"The workaround" is to add few lines in VM's XML, which are available in pretty much every VFIO / GPU passthrough guide (in "code 43" sections). Like these ones:
And you don't have to do it for the most of AMD cards and the newest NVIDIA cards.
Unfortunately that's not beginner-friendly, I know, but that's the problem of VFIO in general - you can't really do it without being comfortable with terminal, editing configuration files etc. It would be cool to make it automatic somehow, but that would require making some tool(s) for all the preparatiary work (assigning vfio-pci driver, building united) and adding features to virt-manager (to be able to all the stuff graphically, without modifying XML).
But anyway, in your original comment you said that passthrough is not possible with consumer GPUs, which is simply not true. It's possible with pretty much every consumer card.
https://mathiashueber.com/windows-virtual-machine-gpu-passth... https://linustechtips.com/topic/978579-guide-linux-pci-gpu-v... https://wiki.archlinux.org/title/PCI_passthrough_via_OVMF
And you don't have to do it for the most of AMD cards and the newest NVIDIA cards.
Unfortunately that's not beginner-friendly, I know, but that's the problem of VFIO in general - you can't really do it without being comfortable with terminal, editing configuration files etc. It would be cool to make it automatic somehow, but that would require making some tool(s) for all the preparatiary work (assigning vfio-pci driver, building united) and adding features to virt-manager (to be able to all the stuff graphically, without modifying XML).
But anyway, in your original comment you said that passthrough is not possible with consumer GPUs, which is simply not true. It's possible with pretty much every consumer card.