Known Issues

1. CUDA or deep learning applications might fail with memory errors after vGPU migration

2. GSP firmware cannot be disabled when NVIDIA Linux open GPU kernel modules are installed

3. After vGPU migration, a vGPU VM might crash or applications might fail with XID error 43

4. VMware vSphere ESXi host might crash when rebooted while vGPU VMs are running

5. Migration or suspension of a vGPU VM might fail after XID error 13

6. Wayland with Ubuntu 24.04 does not work with multi-vGPU VMs

7. Display resolutions can’t be changed in GNOME Settings with Wayland

8. Remote desktop connections fail for vGPUs with 1 GB of frame buffer when used with Wayland

9. With Red Hat Enterprise Linux 10 on VMware vSphere, the VM crashes when graphical.target is set

10. The dmesg command reports non-fatal asserts and warnings

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

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

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

14. NVIDIA Control Panel is not available in multiuser environments

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

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

17. CUDA profilers cannot gather hardware metrics on NVIDIA vGPU

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

51. DWM crashes randomly occur in Windows VMs

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

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

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

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

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

57. Migrating a VM configured with NVIDIA vGPU software release 20.1 to a host running release 20.0 fails

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

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

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

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

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

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

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

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

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

67. VMware vMotion fails gracefully under heavy load

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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