Easy-GPU-PV VS SR-HyperVTools

I'm trying to run the update "Update-VMGpuPartitionDriver.ps1" command mentioned in the instructions alongside with my VM and gpu name (which is auto) but it keeps telling me it doesn't recognize that command in both powershell and powershell ISE.

One nice thing about WSL: GPU "passthrough" (via GPU-PV) is handled out-of-the-box.

There are some solutions (such as https://github.com/jamesstringerparsec/Easy-GPU-PV) that makes the process easy if you are using Hyper-V as the hypervisor, but it is not a straightforward task yet. Hopefully that will change in the future!

Using Google Collab would be easier, but if you want to try partitioning GPUs, this might work: https://github.com/jamesstringerparsec/Easy-GPU-PV (No, I haven't tried it, so don't ask me any questions. ;-)

https://github.com/jamesstringerparsec/Easy-GPU-PV Proxmox would be a good option for this.

As far as I know, GPU virtualization (passthrough) is not featured by VirtualBox (was removed in version 6), so it won't let you pass through the GPU to the VM. However, Virtualbox provides 3D acceleration through Guest Additions, which accelerates some VM graphics by running them on the host (old games might run inside the VM). For GPU passthrough on a Windows host, you need to use Hyper-V. See Easy-GPU-P Github page: https://github.com/jamesstringerparsec/Easy-GPU-PV

Windows hosts do not allow PCIe passthrough, but instead use GPU-PV to partition GPU calls to a Windows VM. This GitHub may be helpful in that regard.

There are 3 major options Hyper-V, ESXi or KVM. If you want to you use VM for OBS, you might need to passthrough entire GPU to achieve better results. It is supported on all hypervisors (except Hyper-V on desktop Windows OS). r/vfIO should help with GPU passthrough on KVM. Check the following script for Hyper-V and GPU-P. https://github.com/jamesstringerparsec/Easy-GPU-PV/blob/main/Add-VMGpuPartitionAdapterFiles.psm1

Here's a modified version of it converted to a module called SR-HyperVTools. If you save the files into your modules folder in PowerShell, you can run the cmdlet with specified parameters to create the VM. No editing of any files is required.