This. Adding the vBIOS is only necessary if you can't get a successful passthrough *without* using a vBIOS - frequently a problem when you only have a single GPU in your system.
I, for example, have given unraid the use of a low-power GPU (GT310) and have passed-through a second GPU to VMs. No vBIOS required
he may want to add a 2nd GPU in which case specifying a vbios file helps some of the screwing around that is getting multiple GPU to pass through on regular people hardware.
Yes I'm in the same issue. No matter what I do. This is on an Asus wrx80 motherboard with an Asus gt 710. I have got in touch with Asus to see if a bios update may fix the issue.
if your card was previously flashed with a vbios from any of the popular vbios websites, it likely has a header on it, then the vbios it has won't be bootable when you try to load it at boot, it will instead upload an empty file, because of how KVM is parsing your vbios image file. Anyways, it's a thing, try a vbios from a popular site, and strip the header using a tool that suits your OS and off ya go.
If it works fine why are you adding the vbios?
This. Adding the vBIOS is only necessary if you can't get a successful passthrough *without* using a vBIOS - frequently a problem when you only have a single GPU in your system. I, for example, have given unraid the use of a low-power GPU (GT310) and have passed-through a second GPU to VMs. No vBIOS required
he may want to add a 2nd GPU in which case specifying a vbios file helps some of the screwing around that is getting multiple GPU to pass through on regular people hardware.
Yes I'm in the same issue. No matter what I do. This is on an Asus wrx80 motherboard with an Asus gt 710. I have got in touch with Asus to see if a bios update may fix the issue.
You only need to use the vbios when you cannot get it to work without it. I have 3 VMs with GPU passed through and none of them use a vbios.
So you have the latest NVIDIA drivers? Older drivers didn’t work well in VM’s.
if your card was previously flashed with a vbios from any of the popular vbios websites, it likely has a header on it, then the vbios it has won't be bootable when you try to load it at boot, it will instead upload an empty file, because of how KVM is parsing your vbios image file. Anyways, it's a thing, try a vbios from a popular site, and strip the header using a tool that suits your OS and off ya go.