Known Issues

Virtual GPU Software R595 Known Issues

Known issues for NVIDIA virtual GPU software and hardware on all supported hypervisors.

Table of Contents

• 1. Wayland with Ubuntu 24.04 does not work with multi-vGPU VMs
• 2. Wayland sessions on Red Hat Enterprise Linux 10 with vGPUs on Blackwell-architecture GPUs are corrupted and unusable
• 3. Display resolutions can't be changed in GNOME Settings with Wayland
• 4. Application windows disappear after display resolution change in Wayland
• 5. Remote desktop connections fail for vGPUs with 1 GB of frame buffer when used with Wayland
• 6. With Red Hat Enterprise Linux 10 on VMware vSphere, the VM crashes when graphical.target is set
• 7. The dmesg command reports non-fatal asserts and warnings
• 8. vGPUs created with a vendor-specific VFIO framework on Ubuntu do not support Console VNC
• 9. NVIDIA vGPU software does not support Ubuntu 22.04 with an upgraded HWE kernel
• 10. Linux graphics driver installation from a .run file fails
• 11. GPU device is unavailable on Windows 11 VMs with more than 1 TB of memory
• 12. Default client configuration token folder missing on Windows client VMs
• 13. Omnissa IDD, not the NVIDIA vGPU software graphics driver is driving the display in Windows 11 24H2 VMs
• 14. vGPU VM fails to boot with error vmiop-display unable to reserve vgpu
• 15. NVIDIA Control Panel is not available in multiuser environments
• 16. NVIDIA Control Panel crashes if a user session is disconnected and reconnected
• 17. VM assigned multiple fractional vGPUs from the same GPU hangs
• 18. CUDA profilers cannot gather hardware metrics on NVIDIA vGPU
• 19. NVIDIA vGPU software graphics driver for Windows sends a remote call to ngx.download.nvidia.com
• 20. Multiple RDP session reconnections on Windows Server 2022 can consume all frame buffer
• 21. VM with multiple legacy fractional vGPUs on the same GPU fails to boot
• 22. On NVIDIA H100, creation of multiple compute instances after deletion of existing compute instances fails
• 23. NLS client fails to acquire a license with the error The allowed time to process response has expired
• 24. NVIDIA vGPU software graphics driver fails to load on KVM-based hypervsiors
• 25. With multiple active sessions, NVIDIA Control Panel incorrectly shows that the system is unlicensed
• 26. VP9 and AV1 decoding with web browsers are not supported on Microsoft Windows Server 2019
• 27. Ubuntu guest driver initialization fails with vGPUs and GPUs that support SR-IOV
• 28. nvidia-smi ignores the second NVIDIA vGPU device added to a Microsoft Windows Server 2016 VM
• 29. After an upgrade of the Linux graphics driver from an RPM package in a licensed VM, licensing fails
• 30. After an upgrade of the Linux graphics driver from a Debian package, the driver is not loaded into the VM
• 31. Desktop session freezes when a VM is migrated to or from a host running an NVIDIA vGPU software 14 release
• 32. Application or vGPU VM crashes when multiple application instances are launched
• 33. The reported NVENC frame rate is double the actual frame rate
• 34. VM fails after a second vGPU is assigned to it
• 35. Hypervisor host reboots when multiple cloned VMs are simultaneously powered on or migrated
• 36. NVENC does not work with Teradici Cloud Access Software on Windows
• 37. When a licensed client deployed by using VMware instant clone technology is destroyed, it does not return the license
• 38. A licensed client might fail to acquire a license if a proxy is set
• 39. Session connection fails with four 4K displays and NVENC enabled on a 2Q, 3Q, or 4Q vGPU
• 40. Disconnected sessions cannot be reconnected or might be reconnected very slowly with NVWMI installed
• 41. For some accounted processes, nvidia-smi incorrectly reports maximum memory use of 0 MiB
• 42. Windows VM crashes during Custom (Advanced) driver upgrade
• 43. VMs with vGPUs on GPUs based on the NVIDIA Ampere architecture fail to power on
• 44. Linux VM hangs after vGPU migration to a host running a newer vGPU manager version
• 45. NVIDIA A100 HGX 80GB vGPU names shown as Graphics Device by nvidia-smi
• 46. Idle Teradici Cloud Access Software session disconnects from Linux VM
• 47. GPU Operator doesn't support vGPU on GPUs based on architectures before NVIDIA Turing
• 48. No virtual GPU types are listed in Citrix XenCenter
• 49. Idle NVIDIA A100, NVIDIA A40, and NVIDIA A10 GPUs show 100% GPU utilization
• 50. NVIDIA vGPU software graphics driver fails to load after upgrade on XenServer
• 51. Windows guest VMs with vGPUs or GPUs with large BAR memory settings fail to boot to the desktop in UEFI mode
• 52. Guest VM frame buffer listed by nvidia-smi for vGPUs on GPUs that support SRIOV is incorrect
• 53. Migrated VM with more than two vGPUs crashes on destination host
• 54. VMs fail to boot on RHV 4.4
• 55. Driver upgrade in a Linux guest VM with multiple vGPUs might fail
• 56. NVIDIA Control Panel fails to start if launched too soon from a VM without licensing information
• 57. VNC client session goes blank and console VNC is corrupted when the guest driver is uninstalled
• 58.  Citrix Virtual Apps and Desktops session corruption occurs in the form of residual window borders
• 59. Omnissa Horizon clients cannot connect to a Windows 10 2004 VM with multiple displays
• 60. Suspend and resume between hosts running different versions of the vGPU manager fails
• 61. On Linux, a VMware Horizon 7.12 session freezes after a switch to full screen
• 62. On Linux, a VMware Horizon 7.12 session with two 4K displays freezes
• 63. On Linux, the frame rate might drop to 1 after several minutes
• 64. Frame buffer consumption grows with Omnissa Horizon over Blast Extreme
• 65. Citrix XenCenter displays misleading information about vGPU types
• 66. Citrix Virtual Apps and Desktops connection freezes initially
• 67. Microsoft DDA fails with some GPUs
• 68. DWM crashes randomly occur in Windows VMs
• 69. NVIDIA Control Panel fails to launch in a platform layer or published image
• 70. Remote desktop session freezes with assertion failure and XID error 43 after migration
• 71. Citrix Virtual Apps and Desktops session freezes when the desktop is unlocked
• 72. NVIDIA vGPU software graphics driver fails after Linux kernel upgrade with DKMS enabled
• 73. Red Hat Enterprise Linux and CentOS 6 VMs hang during driver installation
• 74. On XenServer, all vGPUs in a VM must be of the same type
• 75. Console VGA cannot be disabled
• 76. Console VNC is unusable with Xorg on multiple vGPUs in a VM
• 77. Blue screen crash occurs or no devices are found after VM reset
• 78. Tesla T4 is enumerated as 32 separate GPUs by VMware vSphere ESXi
• 79. Users' sessions may freeze during vMotion migration of VMs configured with vGPU
• 80. Migration of VMs configured with vGPU stops before the migration is complete
• 81. ECC memory settings for a vGPU cannot be changed by using NVIDIA X Server Settings
• 82. Changes to ECC memory settings for a Linux vGPU VM by nvidia-smi might be ignored
• 83. Incorrect GPU type shown for Quadro RTX 8000 GPUs in Citrix XenCenter
• 84. NVIDIA Notification Icon prevents log off of Citrix Published Application user sessions
• 85. Host core CPU utilization is higher than expected for moderate workloads
• 86. H.264 encoder falls back to software encoding on 1Q vGPUs with a 4K display
• 87. H.264 encoder falls back to software encoding on 2Q vGPUs with 3 or more 4K displays
• 88. Frame capture while the interactive logon message is displayed returns blank screen
• 89. RDS sessions do not use the GPU with Microsoft Windows Server as guest OS
• 90. VMware vMotion fails gracefully under heavy load
• 91. View session freezes intermittently after a Linux VM acquires a license
• 92. When the scheduling policy is fixed share, GPU utilization is reported as higher than expected
• 93. Benign warnings during Virtual GPU Manager installation or uninstallation after hypervisor upgrade
• 94. Benign not in gzip format messages during Virtual GPU Manager installation or uninstallation
• 95. License is not acquired in Windows VMs
• 96. nvidia-smi reports that vGPU migration is supported on all hypervisors
• 97. NVIDIA Control Panel Crashes in a VM connected to two 4K displays
• 98. Hot plugging and unplugging vCPUs causes a blue-screen crash in Windows VMs
• 99. GPU resources not available error during VMware instant clone provisioning
• 100. Module load failed during VIB downgrade from R390 to R384
• 101. vGPU guest VM driver not properly loaded on servers with more than 512 GB or 1 TB or more of system memory
• 102. Luxmark causes a segmentation fault on an unlicensed Linux client
• 103. On Linux, 3D applications run slowly when windows are dragged
• 104. A segmentation fault in DBus code causes nvidia-gridd to exit on Red Hat Enterprise Linux and CentOS
• 105. No Manage License option available in NVIDIA X Server Settings by default
• 106. Licenses remain checked out when VMs are forcibly powered off
• 107. Memory exhaustion can occur with vGPU profiles that have 512 Mbytes or less of frame buffer
• 108. VM bug checks after the guest VM driver for Windows 10 RS2 is installed
• 109. On XenServer 7.0, VMs unexpectedly reboot and XenServer crashes or freezes
• 110. With no NVIDIA driver installed, XenServer misidentifies Tesla M10 cards
• 111. vGPU VM fails to boot in ESXi if the graphics type is Shared
• 112. GNOME Display Manager (GDM) fails to start on Red Hat Enterprise Linux 7.2 and CentOS 7.0
• 113. NVIDIA Control Panel fails to start and reports that “you are not currently using a display that is attached to an Nvidia GPU”
• 114. VM configured with more than one vGPU fails to initialize vGPU when booted
• 115. A VM configured with both a vGPU and a passthrough GPU fails to start the passthrough GPU
• 116. vGPU allocation policy fails when multiple VMs are started simultaneously
• 117. Before Horizon agent is installed inside a VM, the Start menu’s sleep option is available
• 118. vGPU-enabled VMs fail to start, nvidia-smi fails when VMs are configured with too high a proportion of the server’s memory.
• 119. On reset or restart VMs fail to start with the error VMIOP: no graphics device is available for vGPU…
• 120. nvidia-smi shows high GPU utilization for vGPU VMs with active Horizon sessions
• 121. Video goes blank when run in loop in Windows Media Player
• 122. Local VGA console is momentarily unblanked when Citrix Virtual Apps and Desktops changes resolution of the VM desktop
• 123. VM bugchecks on shutdown/restart when Citrix Virtual Apps and Desktops is installed and NVIDIA driver is uninstalled or upgraded.
• 124. Application frame rate may drop when running Citrix Virtual Apps and Desktops at 2560×1600 resolution.
• 125. Windows VM BSOD
• 126. Windows VM BSOD when upgrading NVIDIA drivers over a Citrix Virtual Apps and Desktops session
• 127. XenCenter does not allow vGPUs to be selected as a GPU type for Linux VMs
• 128. If X server is killed on a RHEL7 VM running vGPU, XenCenter console may not automatically switch to text console
• 129. Citrix Virtual Apps and Desktops shows only a black screen when connected to a vGPU VM