Is this page helpful?

Known Issues#

  1. The console or RDP session is black on Windows vGPU VMs

  2. Intermittent deadlock occurs in the NVIDIA Direct3D11 user-mode driver

  3. GLX does not work after the NVIDIA vGPU software graphics driver is installed from an RPM package file

  4. Maxwell-architecture vGPU VMs fail to start

  5. Linux graphics driver installation from a .run file fails

  6. GPU device is unavailable on Windows 11 VMs with more than 1 TB of memory

  7. Default client configuration token folder missing on Windows client VMs

  8. NVIDIA Control Panel is not available in multiuser environments

  9. NVIDIA Control Panel crashes if a user session is disconnected and reconnected

  10. VM assigned multiple fractional vGPUs from the same GPU hangs

  11. CUDA profilers cannot gather hardware metrics on NVIDIA vGPU

  12. NVIDIA vGPU software graphics driver for Windows sends a remote call to ngx.download.nvidia.com

  13. On NVIDIA H100, creation of multiple compute instances after deletion of existing compute instances fails

  14. NLS client fails to acquire a license with the error The allowed time to process response has expired

  15. NVIDIA vGPU software graphics driver fails to load on KVM-based hypervisors

  16. With multiple active sessions, NVIDIA Control Panel incorrectly shows that the system is unlicensed

  17. VP9 and AV1 decoding with web browsers are not supported on Microsoft Windows Server 2019

  18. nvidia-smi ignores the second NVIDIA vGPU device added to a Microsoft Windows Server 2016 VM

  19. After an upgrade of the Linux graphics driver from an RPM package in a licensed VM, licensing fails

  20. After an upgrade of the Linux graphics driver from a Debian package, the driver is not loaded into the VM

  21. The reported NVENC frame rate is double the actual frame rate

  22. NVENC does not work with Teradici Cloud Access Software on Windows

  23. A licensed client might fail to acquire a license if a proxy is set

  24. Session connection fails with four 4K displays and NVENC enabled on a 2Q, 3Q, or 4Q vGPU

  25. For some accounted processes, nvidia-smi incorrectly reports maximum memory use of 0 MiB

  26. NVIDIA A100 HGX 80GB vGPU names shown as Graphics Device by nvidia-smi

  27. Idle NVIDIA A100, NVIDIA A40, and NVIDIA A10 GPUs show 100% GPU utilization

  28. Guest VM frame buffer listed by nvidia-smi for vGPUs on GPUs that support SRIOV is incorrect

  29. Driver upgrade in a Linux guest VM with multiple vGPUs might fail

  30. NVIDIA Control Panel fails to start if launched too soon from a VM without licensing information

  31. On Linux, the frame rate might drop to 1 after several minutes

  32. DWM crashes randomly occur in Windows VMs

  33. ECC memory settings for a vGPU cannot be changed by using NVIDIA X Server Settings

  34. Changes to ECC memory settings for a Linux vGPU VM by nvidia-smi might be ignored

  35. Host core CPU utilization is higher than expected for moderate workloads

  36. Frame capture while the interactive logon message is displayed returns blank screen

  37. RDS sessions do not use the GPU with Microsoft Windows Server as guest OS

  38. When the scheduling policy is fixed share, GPU utilization is reported as higher than expected

  39. License is not acquired in Windows VMs

  40. nvidia-smi reports that vGPU migration is supported on all hypervisors

  41. Hot plugging and unplugging vCPUs causes a blue-screen crash in Windows VMs

  42. Luxmark causes a segmentation fault on an unlicensed Linux client

  43. A segmentation fault in DBus code causes nvidia-gridd to exit on Red Hat Enterprise Linux and CentOS

  44. No Manage License option available in NVIDIA X Server Settings by default

  45. Licenses remain checked out when VMs are forcibly powered off

  46. VM bug checks after the guest VM driver for Windows 10 RS2 is installed

  47. GNOME Display Manager (GDM) fails to start on Red Hat Enterprise Linux 7.2 and CentOS 7.0