Updated Oct 1, 2021
1. Windows Server 2022 Build 20348 GPU-P Partitioning Instructions Available (See Support Contact, Additional Layered Driver Required)

Updated June 6, 2020
1. Add a special virtual hardware, virtual renderer device (vrd).
This virtual hardware is invisiable in the hyper-v console.
You can see it in the devmgmt.msc of guest operating system.

$vm = "win10"
$gpup = Get-VMPartitionableGpu
Remove-VMGpuPartitionAdapter -VMName $vm
Set-VMPartitionableGpu -Name $gpup.Name -PartitionCount 1
Set-VM -GuestControlledCacheTypes $true -VMName $vm
Set-VM -LowMemoryMappedIoSpace 3072MB -VMName $vm
Set-VM -HighMemoryMappedIoSpace 32768MB -VMName $vm
Add-VMGpuPartitionAdapter -VMName $vm

2. Locate your host's graphics driver path:
a. Start dxdiag
b. Click [Save all information]
c. Open DxDiag.txt
d. Search 'Driver Name'
e. You should see something like:
Driver Name: C:\Windows\System32\DriverStore\FileRepository\
nvcvi.inf_amd64_265a497b8b286fab\nvldumdx.dll

f. Different drivers have different names, in this case, the folder name is
nvcvi.inf_amd64_265a497b8b286fab
Change it to your own value.

3. Copy the entire folder from the host os:
C:\Windows\System32\DriverStore\FileRepository\
nvcvi.inf_amd64_265a497b8b286fab\
To the guest os:
C:\Windows\System32\HostDriverStore\FileRepository\
nvcvi.inf_amd64_265a497b8b286fab\

(If the folder name 'HostDriverStore' does not exist, manually create it.)

4. Now you should have full graphics virtulization in the guest os.
5. To verify, go to device management, under Display Adapters, you should see two graphics cards.
6. Try 3D Benchmark, you should see Guest OS is utilizing the graphics card of the Host OS.

Updated May 5, 2020
- Windows 10 19041.208 Hyper-V GPU-P Supported
- Guest VM Vulkan API Preliminary Support
- WDDM Driver 2.9 Under Testing, with GPU-PV Support

Updated Jan 20, 2020
Note this GPU-P Test Drive Instruction is different from Windows Sandbox.
- Windows Sandbox only provides partial GPU virtualization.
- It only exposes DirectX 12 API for general users.
- It requires configuration of the operating system every time you re-start the Sandbox.
- It requires remote desktop connection (mstsc), which causes some applications to not working correctly. (v.s. Hyper-V native client vmconnect)

Updated Jan 10, 2020
Note I have made new instructions (it took me few weeks to research), which no longer requires my special kernel modification driver.
Also, the GPU-P feature now seems to be very stable under stress tests (AIDA64).
Previously, to make GPU-P work under Windows 10 we need to inject some special code to trigger undocumented (experimental) features.

This test drive gives you instructions to test Hyper-V GPU Virtualization.
This is the first true graphics virtualization solution currently available for consumer market.
(v.s. expensive AMD MxGPU / Nvidia Grid)

If you have a laptop with Nvidia Geforce Graphics Card such as GTX 1060, it can be used for Hyper-V Graphics Virtualization.
Also this Test Drive does not require SR-IOV to be enabled. Most laptops does not provide such BIOS settings.

Currently there are only few solutions for desktop GPU Virtualization:
VMWare Workstation 15.5 - Only Supports DirectX 10.1 and OpenGL 3.3
VMWare Workstation 20H2 (Hardware Version v18) - Supports DirectX 11.0 and OpenGL 4.0 but slow
Hyper-V RemoteFX is deprecated and its API-forwarding architecture is not efficient
Hyper-V DDA - Supports Native Graphics Drivers but Requires at lease Nvidia Quadro Card

This new solution gives you full graphics virtualization technology support, enabling you to
utilize full OpenGL 4.6 and DirectX 12 capabilities on Hyper-V Virtual Machines on Modern Laptops.

Support Contact:
455718191#qq.com

свернуть