Known Issues

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

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

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

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

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

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

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

8. Omnissa IDD, not the NVIDIA vGPU software graphics driver is driving the display in Windows 11 24H2 VMs

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

10. NVIDIA Control Panel is not available in multiuser environments

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

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

13. CUDA profilers cannot gather hardware metrics on NVIDIA vGPU

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

47. DWM crashes randomly occur in Windows VMs

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

63. VMware vMotion fails gracefully under heavy load

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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