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. Omnissa IDD, not the NVIDIA vGPU software graphics driver is driving the display in Windows 11 24H2 VMs

11. vGPU VM fails to boot with error vmiop-display unable to reserve vgpu

12. NVIDIA Control Panel is not available in multiuser environments

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

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

15. CUDA profilers cannot gather hardware metrics on NVIDIA vGPU

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

49. DWM crashes randomly occur in Windows VMs

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

65. VMware vMotion fails gracefully under heavy load

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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