Easy-GPU-PV VS FastGPUP

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

First create your VM like normal, give it a drive, RAM, Cores etc. then to add your gpu to the VM go to either of these links, https://github.com/b1on1cdog/FastGPUP, I recommend using this, its a bit buggy as its WIP but it gets the job done, it needs .net 0.6. https://forum.level1techs.com/t/2-gamers-1-gpu-with-hyper-v-gpu-p-gpu-partitioning-finally-made-possible-with-hyperv/172234 this is a much more difficult method but more consistently works, of course ensure you have a .iso of your OS of choice (I recommend windows 10) and install parsec on the VM. For the case of getting your games on the VM, in hyper V, Firstly, on your host pc, share the drive where your games are by clicking properties and then click on the tab "sharing" then go to "advanced sharing" and click "share this folder" then go to the bottom left and click "permissions" and click "full control" now in your VM launch it in enhanced session mode and in the pop up that appears to set your resolution click the arrow at the bottom saying "Show options" and in the top right click the "local resources" tab, on the local devices and resources section click "more" select the tab "drives" and select your drive where your games are, now if you boot into the VM and go to the documents app, in the bottom corner go to the network drive, find your games folder and copy them. from what I know theres no way to have them on your VM without copying them. From there just install the emulators you want and run the ROMS or whatever.

There are some good projects on github.

i uploaded here: https://github.com/b1on1cdog/FastGPUP

If anyone is interested, i decided to make a GUI app to ease a bit more the process, this wasn't tested too much, since i only made it to help me save some time and was only used on Windows 11. https://github.com/b1on1cdog/FastGPUP. the usage is simple, choose VM, choose GPU, slide the percentage you want to allocate of it and then press Add. For drivers you press Mount VHD, when done it will open disk management where you'll assign a letter for the mounted drive (if it doesn't has one) and then you chose that drive letter on the tool and press "install/update driver" button. Since i didn't test this outside my own PC i'm not sure if you might need to change PowerShell execution policy.