I have 2 x NDIVA Quadro RTX 8000 and a Windows 2022 server with Hyper-V on a DELL 740
I had to go back with the BIOS and deinstalled the NDIVA driver
When I try to install again the driver it says: “NDIVA Installer cannot continue”
I would like to use gPU for the virtual Hayper-V machines
Any idea how I can remove the NDIVA and install again?
After experimenting and reading the docs I am now on the point that I have 1 NVIDIA RTX 8000 assigned to 1 virtual Win2022 server.
PS C:\Windows\system32> Set-VM -LowMemoryMappedIoSpace 2GB -VMName Vtest
PS C:\Windows\system32> Set-VM -HighMemoryMappedIoSpace 48GB -VMName Vtest
PS C:\Windows\system32> Add-VMAssignableDevice -LocationPath “PCIROOT(D7)#PCI(0000)#PCI(0000)” -VMName Vtest
the NVIDIA card is also deactivated on the physical server
In the virtual machine (remote desktop) in device settings I see 2 display cards
Microsoft Hyper-V Video
NVIDIA Quadro RTX 8000
I can open the NVIDIA control panel and see:
NVIDIA System Information report created on: 03/07/2022 03:04:50
System name: Vtest
Operating System: Windows Server 2022 Standard, 64-bit
DirectX version: 12.0
GPU processor: Quadro RTX 8000
Driver version: 511.79
Driver Type: DCH
CUDA Cores: 4608
Core clock: 1620 MHz
Memory data rate: 13.00 Gbps
Memory interface: 384-bit
Memory bandwidth: 624.10 GB/s
Memory type: GDDR6
Total available graphics memory: 46080 MB
Dedicated video memory: 46080 MB GDDR6
Video BIOS version: 90.02.4E.00.03
IRQ: Not used
Bus: PCI Express x16 Gen3
Error Correction Code (ECC): On
Device Id: 10DE 1E78 13D810DE
Part Number: G150 0231
nvui.dll 184.108.40.2069 NVIDIA User Experience Driver Component
nvxdplcy.dll 220.127.116.119 NVIDIA User Experience Driver Component
nvxdbat.dll 18.104.22.1689 NVIDIA User Experience Driver Component
nvxdapix.dll 22.214.171.1249 NVIDIA User Experience Driver Component
NVCPL.DLL 126.96.36.1999 NVIDIA User Experience Driver Component
nvCplUIR.dll 8.1.940.0 NVIDIA Control Panel
nvCplUI.exe 8.1.940.0 NVIDIA Control Panel
nvWSSR.dll 188.8.131.529 NVIDIA Workstation Server
nvWSS.dll 184.108.40.2069 NVIDIA Workstation Server
nvViTvSR.dll 220.127.116.119 NVIDIA Video Server
nvViTvS.dll 18.104.22.1689 NVIDIA Video Server
nvLicensingS.dll 22.214.171.1249 NVIDIA Licensing Server
nvDevToolSR.dll 126.96.36.1999 NVIDIA Licensing Server
nvDevToolS.dll 188.8.131.529 NVIDIA 3D Settings Server
nvDispSR.dll 184.108.40.2069 NVIDIA Display Server
nvDispS.dll 220.127.116.119 NVIDIA Display Server
NVCUDA64.DLL 18.104.22.1689 NVIDIA CUDA 11.6.110 driver
nvGameSR.dll 22.214.171.1249 NVIDIA 3D Settings Server
nvGameS.dll 126.96.36.1999 NVIDIA 3D Settings Server
What to do next to use this grafic card?
I tried also a WIN10 as virtual machine.
The NVIDA drivers install correct.
The NVIDA Control Panel shows not all features (I started the program as admin)
I used the microsoft documentation and Virtual GPU Software User Guide :: NVIDIA Virtual GPU Software Documentation … no errors, everything looks ok.
… but still I can not use the NVIDIA graphic card
and could you please describe what is not working? How do you know that the GPU is not working? Did you test with Youtube or other applications to see in Taskmanager or with nvidia-smi if there is GPU load? From the screenshots given it looks like it needs to work already as the GPU is properly recognized within the VM.
I did just a fresh installation.
No error messages and also the installation of the the NVIDIA driver 511.79 worked fine on a virtual machine with Windows 2022.
NVIDIA card is shown correctly under the display adapters.
Points that do not work:
- NVIDIA CONTROL PANEL: I thought there is shown more information?
- Task Manager: I thought the GPU must be shown
- You Tube: slow with 8 frames ( Iguess not using the RTX 8000 Grafic card)
I assigned now 48GB of the RTX 8000 to this virtual machine. The RTX Desktop Manager works, but the grafic card is not used …
unfortunately it doesn’t help if you make assumptions. Please use a tool to check if GPU is working or not. You can use GPUProfiler Releases · JeremyMain/GPUProfiler · GitHub or nvidia-smi which is already installed (command line tool).
You also need to be aware that you need to set a local policy on Server OS to use the GPU for RDP sessions which might be the case here.
And one more thing: Is this a passive cooled RTX8000 or an active one? This really makes a difference as you would need a different driver (vGPU driver) + licenses if running the passive one. This would also explain why it cannot work properly.
Thanks for the hint “passive cooled RTX8000”. I bought the server from DELL. I guess I can then buy the soware also from DELL. Is there a test license? Or should the driver from the enterprise area work?
NVIDIA Licensing Portal (here there is a lower driver version)
Correct, you need the driver from NV licensing portal. As you can see in GPUProfiler, the GPU is running in TCC mode so it is definitely a passive RTX (datacenter GPU) and therefore the public driver is only capable to do compute on Windows. For WDDM support you need the vGPU driver from the NV portal and then it will switch to WDDM mode and should work as expected. You can buy the vApps licenses from Dell (1vApps per CCU running on the RDSH). As you seem to have already access to the portal you should also got a 90 trial automatically…
With the vGPU driver from the NV portal it is working. GPU is shown in the taskmanager and in the GPU Profiler tool.
One more (basic) question:
I have as a physical server WIN2022 and 2 RTX 8000 with 48 GB.
Let assume I would like to have 8 Virtual machines (WIN2022) using this hardware.
As I understood from the manuals there are 2 ways to use the RTX8000.
a) GPU Pass-Through (this is working now)
b) vGPU (NVIDIA Virtual GPU Manager)
With a) I could have 2 VMs (or add more NVIDIA cards) and I could add Terminal licenses to the VM and this way I have 1 VM with 4 different users (and a second VM with the same). Correct?
With b) (NVIDIA Virtual GPU (vGPU)) I would have to install Citrix Hypervisor or VMware vSPhere on the physical server, correct?
Correct. vGPU only works with VMWare/Citrix or KVM as hypervisor.