Known Issues

1. Purple screen crashes might occur on ESXi hosts with multiple GPUs

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

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

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. vGPU VM fails to boot with error vmiop-display unable to reserve vgpu

11. NVIDIA Control Panel is not available in multiuser environments

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

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

14. CUDA profilers cannot gather hardware metrics on NVIDIA vGPU

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

16. Multiple RDP session reconnections on Windows Server 2022 can consume all frame buffer

17. VM with multiple legacy fractional vGPUs on the same GPU fails to boot

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

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

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

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

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

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

24. Desktop session freezes when a VM is migrated to or from a host running an NVIDIA vGPU software 14 release

25. Application or vGPU VM crashes when multiple application instances are launched

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

27. VM fails after a second vGPU is assigned to it

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

29. When a licensed client deployed by using VMware instant clone technology is destroyed, it does not return the license

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

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

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

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

34. Windows VM crashes during Custom (Advanced) driver upgrade

35. VMs with vGPUs on GPUs based on the NVIDIA Ampere architecture fail to power on

36. Linux VM hangs after vGPU migration to a host running a newer vGPU manager version

37. GPU Operator doesn’t support vGPU on GPUs based on architectures before NVIDIA Turing

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

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

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

41. Citrix Virtual Apps and Desktops session corruption occurs in the form of residual window borders

42. Omnissa Horizon clients cannot connect to a Windows 10 2004 VM with multiple displays

43. Suspend and resume between hosts running different versions of the vGPU manager fails

44. On Linux, a VMware Horizon 7.12 session freezes after a switch to full screen

45. On Linux, a VMware Horizon 7.12 session with two 4K displays freezes

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

47. Frame buffer consumption grows with Omnissa Horizon over Blast Extreme

48. DWM crashes randomly occur in Windows VMs

49. Remote desktop session freezes with assertion failure and XID error 43 after migration

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

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

52. Red Hat Enterprise Linux and CentOS 6 VMs hang during driver installation

53. Tesla T4 is enumerated as 32 separate GPUs by VMware vSphere ESXi

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

55. Users’ sessions may freeze during vMotion migration of VMs configured with vGPU

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

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

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

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

60. H.264 encoder falls back to software encoding on 1Q vGPUs with a 4K display

61. H.264 encoder falls back to software encoding on 2Q vGPUs with 3 or more 4K displays

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

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

64. VMware vMotion fails gracefully under heavy load

65. View session freezes intermittently after a Linux VM acquires a license

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

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

68. GPU resources not available error during VMware instant clone provisioning

69. Module load failed during VIB downgrade from R390 to R384

70. On Linux, 3D applications run slowly when windows are dragged

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

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

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

74. Memory exhaustion can occur with vGPU profiles that have 512 Mbytes or less of frame buffer

75. vGPU VM fails to boot in ESXi if the graphics type is Shared

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

77. NVIDIA Control Panel fails to start and reports that “you are not currently using a display that is attached to an Nvidia GPU”

78. VM configured with more than one vGPU fails to initialize vGPU when booted

79. A VM configured with both a vGPU and a passthrough GPU fails to start the passthrough GPU

80. vGPU allocation policy fails when multiple VMs are started simultaneously

81. Before Horizon agent is installed inside a VM, the Start menu’s sleep option is available

82. vGPU-enabled VMs fail to start, nvidia-smi fails when VMs are configured with too high a proportion of the server’s memory.

83. On reset or restart VMs fail to start with the error VMIOP: no graphics device is available for vGPU…

84. nvidia-smi shows high GPU utilization for vGPU VMs with active Horizon sessions