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. The dmesg command reports non-fatal asserts and warnings

5. vGPUs created with a vendor-specific VFIO framework do not support Console VNC

6. NVIDIA vGPU software does not support Ubuntu 22.04 with an upgraded HWE kernel

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

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

9. NVIDIA Control Panel is not available in multiuser environments

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

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

12. CUDA profilers cannot gather hardware metrics on NVIDIA vGPU

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

14. On NVIDIA H100, creation of multiple compute instances after deletion of existing compute instances fails

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

16. NVIDIA vGPU software graphics driver fails to load on KVM-based hypervisors

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

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

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

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

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

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

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

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

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

26. NVIDIA A100 HGX 80GB vGPU names shown as Graphics Device by nvidia-smi

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

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

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

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

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

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

33. DWM crashes randomly occur in Windows VMs

34. Migrating a VM configured with NVIDIA vGPU software release 20.1 to a host running release 20.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. License is not acquired in Windows VMs

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

44. Hot plugging and unplugging vCPUs causes a blue-screen crash in Windows VMs

45. Luxmark causes a segmentation fault on an unlicensed Linux client

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

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

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

49. VM bug checks after the guest VM driver for Windows 10 RS2 is installed