Easy-GPU-PV
A work-in-progress project dedicated to making GPU Paravirtualization on Windows Hyper-V easier!
GPU-PV allows you to partition your systems dedicated or integrated GPU and assign it to several Hyper-V VMs. It's the same technology that is used in WSL2, and Windows Sandbox.
Easy-GPU-PV aims to make this easier by automating the steps required to get a GPU-PV VM up and running.
Easy-GPU-PV does the following...
- Creates a VM of your choosing
- Automatically Installs Windows to the VM
- Partitions your GPU of choice and copies the required driver files to the VM
- Installs Parsec to the VM, Parsec is an ultra low latency remote desktop app, use this to connect to the VM. You can use Parsec for free non commercially. To use Parsec commercially, sign up to a Parsec For Teams account
Prerequisites:
- Windows 10 20H1+ Pro, Enterprise or Education OR Windows 11 Pro, Enterprise or Education. Windows 11 on host and VM is preferred due to better compatibility.
- Matched Windows versions between the host and VM. Mismatches may cause compatibility issues, blue-screens, or other issues. (Win10 21H1 + Win10 21H1, or Win11 21H2 + Win11 21H2, for example)
- Desktop Computer with dedicated NVIDIA/AMD GPU or Integrated Intel GPU - Laptops with NVIDIA GPUs are not supported at this time, but Intel integrated GPUs work on laptops. GPU must support hardware video encoding (NVIDIA NVENC, Intel Quicksync or AMD AMF).
- Latest GPU driver from Intel.com or NVIDIA.com, don't rely on Device manager or Windows update.
- Latest Windows 10 ISO downloaded from here / Windows 11 ISO downloaded from here. - Do not use Media Creation Tool, if no direct ISO link is available, follow this guide.
- Virtualisation enabled in the motherboard and Hyper-V fully enabled on the Windows 10/ 11 OS (requires reboot).
- Allow Powershell scripts to run on your system - typically by running "Set-ExecutionPolicy unrestricted" in Powershell running as Administrator.
Instructions
- Make sure your system meets the prerequisites.
- Download the Repo and extract.
- Search your system for Powershell ISE and run as Administrator.
- In the extracted folder you downloaded, open PreChecks.ps1 in Powershell ISE. Run the files from within the extracted folder. Do not move them.
- Open and Run PreChecks.ps1 in Powershell ISE using the green play button and copy the GPU Listed (or the warnings that you need to fix).
- Open CopyFilesToVM.ps1 Powershell ISE and edit the params section at the top of the file, you need to be careful about how much ram, storage and hard drive you give it as your system needs to have that available. On Windows 10 the GPUName must be left as "AUTO", In Windows 11 it can be either "AUTO" or the specific name of the GPU you want to partition exactly how it appears in PreChecks.ps1. Additionally, you need to provide the path to the Windows 10/11 ISO file you downloaded.
- Run CopyFilesToVM.ps1 with your changes to the params section - this may take 5-10 minutes.
- Open and sign into Parsec on the VM. You can use Parsec to connect to the VM up to 4K60FPS.
- You should be good to go!
Upgrading GPU Drivers when you update the host GPU Drivers
It's important to update the VM GPU Drivers after you have updated the Host GPUs drivers. You can do this by...
- Reboot the host after updating GPU Drivers.
- Open Powershell as administrator and change directory (CD) to the path that CopyFilestoVM.ps1 and Update-VMGPUPartitonDriver.ps1 are located.
- Run
Update-VMGPUPartitonDriver.ps1 -VMName "Name of your VM" -GPUName "Name of your GPU"
(Windows 10 GPU name must be "AUTO")
Values
VMName = "GPUP"
- Name of VM in Hyper-V and the computername / hostname
SourcePath = "C:\Users\james\Downloads\Win11_English_x64.iso"
- path to Windows 10/ 11 ISO on your host
Edition = 6
- Leave as 6, this means Windows 10/11 Pro
VhdFormat = "VHDX"
- Leave this value alone
DiskLayout = "UEFI"
- Leave this value alone
SizeBytes = 40gb
- Disk size, in this case 40GB, the minimum is 20GB
MemoryAmount = 8GB
- Memory size, in this case 8GB
CPUCores = 4
- CPU Cores you want to give VM, in this case 4
NetworkSwitch = "Default Switch"
- Leave this alone unless you're not using the default Hyper-V Switch
VHDPath = "C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks\"
- Path to the folder you want the VM Disk to be stored in, it must already exist
UnattendPath = "$PSScriptRoot"+"\autounattend.xml"
-Leave this value alone
GPUName = "AUTO"
- AUTO selects the first available GPU. On Windows 11 you may also use the exact name of the GPU you want to share with the VM in multi GPU situations (GPU selection is not available in Windows 10 and must be set to AUTO)
GPUResourceAllocationPercentage = 50
- Percentage of the GPU you want to share with the VM
Team_ID = ""
- The Parsec for Teams ID if you are a Parsec for Teams Subscriber
Key = ""
- The Parsec for Teams Secret Key if you are a Parsec for Teams Subscriber
Username = "GPUVM"
- The VM Windows Username, do not include special characters, and must be different from the "VMName" value you set
Password = "CoolestPassword!"
- The VM Windows Password, cannot be blank
Autologon = "true"
- If you want the VM to automatically login to the Windows Desktop
Thanks to:
- Hyper-ConvertImage for creating an updated version of Convert-WindowsImage that is compatible with Windows 10 and 11.
- gawainXX for help testing and pointing out bugs and feature improvements.
Notes:
- After you have signed into Parsec on the VM, always use Parsec to connect to the VM. Keep the Microsft Hyper-V Video adapter disabled. Using RDP and Hyper-V Enhanced Session mode will result in broken behaviour and black screens in Parsec. RDP and the Hyper-V video adapter only offer a maximum of 30FPS. Using Parsec will allow you to use up to 4k60 FPS.
- If you get "ERROR : Cannot bind argument to parameter 'Path' because it is null." this probably means you used Media Creation Tool to download the ISO. You unfortunately cannot use that, if you don't see a direct ISO download link at the Microsoft page, follow this guide.
- Your GPU on the host will have a Microsoft driver in device manager, rather than an nvidia/intel/amd driver. As long as it doesn't have a yellow triangle over top of the device in device manager, it's working correctly.
- A powered on display / HDMI dummy dongle must be plugged into the GPU to allow Parsec to capture the screen. You only need one of these per host machine regardless of number of VM's.
- If your computer is super fast it may get to the login screen before the audio driver (VB Cable) and Parsec display driver are installed, but fear not! They should soon install.
- The screen may go black for times up to 10 seconds in situations when UAC prompts appear, applications go in and out of fullscreen and when you switch between video codecs in Parsec - not really sure why this happens, it's unique to GPU-P machines and seems to recover faster at 1280x720.
- Vulkan renderer is unavailable and GL games may or may not work. This may help with some OpenGL apps.
- If you do not have administrator permissions on the machine it means you set the username and vmname to the same thing, these needs to be different.
- AMD Polaris GPUS like the RX 580 do not support hardware video encoding via GPU Paravirtualization at this time.
- To download Windows ISOs with Rufus, it must have "Check for updates" enabled.