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. On Windows hypervisors, vGPU utilization is reported as 0%

  4. vGPU migration fails for GPUs based on the NVIDIA Ampere and later GPU architectures

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

  6. Maxwell-architecture vGPU VMs fail to start

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

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

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

  10. NVIDIA Control Panel is not available in multiuser environments

  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. Multiple RDP session reconnections on Windows Server 2022 can consume all frame buffer

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

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

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

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

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

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

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

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

  22. Disconnected sessions cannot be reconnected or might be reconnected very slowly with NVWMI installed

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

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

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

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

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

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

  29. Microsoft DDA fails with some GPUs

  30. DWM crashes randomly occur in Windows VMs

  31. Citrix Virtual Apps and Desktops session freezes when the desktop is unlocked

  32. NVIDIA vGPU software graphics driver fails after Linux kernel upgrade with DKMS enabled

  33. Blue screen crash occurs or no devices are found after VM reset

  34. Migrating a VM configured with NVIDIA vGPU software release 19.1 to a host running release 19.0 fails

  35. Migration of VMs configured with vGPU stops before the migration is complete

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

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

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

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

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

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

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

  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