@lizardface110
Oh my god, game changer! I haven't got an APU so can't experiment with VFIO yet, but I've been following these tutorials for a bit now and the ability to instantly swap the GPU from host to virtual machine solves the biggest issue preventing me from committing to it. Thank you!
@gothic..
i usually can't stand modern youtube creators but i came across your channel looking up vfio stuff and i've been pleasantly surprised. very concise without 50% of the video being dedicated to intros/time padding for ads/etc and they just so happen to match the exact use cases i was looking for. bless you also, unsure if this has been covered in one of your videos but how noticeable of a performance difference would there be using a qcow image on a nvme drive vs passing the physical drive through? qcow's extra features seem very nice.
@kirkkork
Have you taken a look SomeOrdinaryGamers' video "I Almost Lost My Virtual Machines"? At 28:34 he mentions writing hooks to load vfio modules and remove the Nvidia GPU from the host, and the reverse on shutdown of the VM. I haven't tried this yet, but this might be worth a look if it avoids rebooting the machine.
@T1NK33R
You are amazing keep up the good work. One thing i need to clarify grubby only on fedora based distros right, what about arch!
@Shirocco7
So. Awesome. Thanks for sharing!!
@Xx_Eric_was_Here_xX
ok, i find it easier to just have separate boot options in grub, one for vfio and one without it.. i thought you were gonna show us how to bind to vfio without rebooting. i already know how to unbind from vfio and use nvidia driver without rebooting, just trying to figure out the other way around...to be fair, the graphics card might hate trying to do this without rebooting, idk, rebooting is probably the 'healthiest' way so far
@JanLunge
Really nice to see, this would work really well for me I would just need to figure out how to do this with the gpus i have. In which slot in the mainboard do you have your passthrough gpu and the not passed gpu? I always get into issues with having the passthrough card in the 1st slot. but the other slots do not support 16x bandwidth am I missing something here? (passing through a 3090, and a rx 580 for the host as fallback gpu, on a ryzen cpu so no i-gpu)
@moonofdeceit5688
Nice, I'm curious how this may differ by using libvirt hooks. Right now based on the vm I boot a script runs, stops associated drivers, detaches gpu, and loads vfio services. I am hesitating to install a second gpu to see if I can modify my hook to stop amd drivers, detach my first amd gpu, then reinit my drivers to get my rx 370 back to outputting the host. My primary passthrough card is an RX 6800. Awesome video as always.
@rabid6449
not terrible. I have two capable video cards. but here's a suggestion on your command... also edit the qemu XML to autostart or not autostart your VM depending on if the nvidia card is going to be available to vfio
@ein1742
Wait couldn't you just have a second vm with linux instead of windows? I mean the performance would be worse but at least you wouldn't have to deal with this stuff (I think? Idk I'm just now discovering VFIO)
@mobgripchamanrogue
Feelsbadman iv'e made a minimal vm just to load up the driver in order to stop the fan of my hijacked GPU when i'm using my linux système. I should have spent more Time on the wiki thx for the tips
@owlmostdead9492
I do it without rebooting, since A) It's faster B) I don't have to retype my disk encryption password. I simply run "sudo nohup ./scriptDOTsh" which kills display-manager.service and the nvidia kernel module then VFIO automatically takes over the GPU. Although I am running into an issue recently where the Nvidia GPU is bound to VFIO, the Windows VM has full access to the GPU and the driver is installed but I don't have any video output. I haven't found a solution to it yet because a couple months ago it worked perfectly fine, I think it has something to do with the new Nvidia driver or Kernel tainting the GPU.. if someone has a solution for that I'd appreciate it.
@houndsolo1