NVIDIA Virtual GPU Software v15.0 through 15.4
Version 15.0 Download PDF

Microsoft Windows Server

Virtual GPU Software R525 for Microsoft Windows Server Release Notes

Release information for all users of NVIDIA virtual GPU software and hardware on Microsoft Windows Server.

These Release Notes summarize current status, information on validated platforms, and known issues with NVIDIA vGPU software and associated hardware on Microsoft Windows Server.

1.1. NVIDIA vGPU Software Driver Versions

Each release in this release family of NVIDIA vGPU software includes a specific version of the NVIDIA Windows driver and NVIDIA Linux driver.

NVIDIA vGPU Software Version NVIDIA Windows Driver Version NVIDIA Linux Driver Version
15.4 529.19 525.147.05
15.3 529.11 525.125.06
15.2 528.89 525.105.17
15.1 528.24 525.85.05
15.0 527.41 525.60.13

Note:

You must use NVIDIA License System with every release in this release family of NVIDIA vGPU software. All releases in this release family of NVIDIA vGPU software are incompatible with all releases of the NVIDIA vGPU software license server.

1.2. Updates in Release 15.4

New Features in Release 15.4

  • Security updates - see Security Bulletin: NVIDIA GPU Display Driver - October 2023, which is posted shortly after the release date of this software and is listed on the NVIDIA Product Security page
  • Miscellaneous bug fixes

1.3. Updates in Release 15.3

New Features in Release 15.3

  • Security updates - see Security Bulletin: NVIDIA GPU Display Driver - June 2023, which is posted shortly after the release date of this software and is listed on the NVIDIA Product Security page
  • Miscellaneous bug fixes

Hardware and Software Support Introduced in Release 15.3

  • Support for Red Hat Enterprise Linux 8.8 as a guest OS

Feature Support Withdrawn in Release 15.3

  • Red Hat Enterprise Linux 8.7 and 8.4 are no longer supported as a guest OS.

1.4. Updates in Release 15.2

New Features in Release 15.2

  • Support for authenticated local proxy servers by licensed clients of a Cloud License Service (CLS) instance
  • Security updates - see Security Bulletin: NVIDIA GPU Display Driver - March 2023, which is posted shortly after the release date of this software and is listed on the NVIDIA Product Security page
  • Miscellaneous bug fixes

Hardware and Software Support Introduced in Release 15.2

  • Support for the for the following GPUs:
    • NVIDIA H800 PCIe 80GB
    • NVIDIA L4
  • Support for Rocky Linux as a guest OS

Features Deprecated in Release 15.2

The following table lists features that are deprecated in this release of NVIDIA vGPU software. Although the features remain available in this release, they might be withdrawn in a future release. In preparation for the possible removal of these features, use the preferred alternatives listed in the table.
Deprecated Feature Preferred Alternatives
CentOS Linux as a guest OS The following CentOS Linux releases are the last releases to be supported by NVIDIA vGPU software:
  • CentOS Linux 7.9
  • CentOS Linux 8 (2011)
Rocky Linux

Rocky Linux releases that are compatible with supported Red Hat Enterprise Linux releases are supported.

1.5. Updates in Release 15.1

New Features in Release 15.1

  • Miscellaneous bug fixes

Hardware and Software Support Introduced in Release 15.1

  • Support for the for the following GPUs:
    • NVIDIA L40
    • NVIDIA RTX 6000 Ada
  • Support for Windows 11 22H2 as a guest OS
  • Support for Windows 10 2022 Update (22H2) as a guest OS

1.6. Updates in Release 15.0

New Features in Release 15.0

  • Unified memory support on the following GPUs:
    • NVIDIA A100 (all variants)
    • NVIDIA A30
  • Support for non-transparent local proxy servers when NVIDIA vGPU software is served licenses by a Cloud License Service (CLS) instance
  • Miscellaneous bug fixes

Hardware and Software Support Introduced in Release 15.0

  • Support for the following GPUs:
    • NVIDIA A100 PCIe 80GB liquid cooled
    • NVIDIA A800 PCIe 80GB
    • NVIDIA A800 PCIe 80GB liquid cooled
    • NVIDIA A800 HGX 80GB
    • NVIDIA H100 PCIe 80GB

Feature Support Withdrawn in Release 15.0

  • The legacy NVIDIA vGPU software license server is no longer supported.
    Note:

    If you are using the legacy NVIDIA vGPU software license server to serve licenses for an earlier vGPU software release, you must migrate your licenses to NVIDIA License System as part of your upgrade to NVIDIA vGPU software 15.0. Otherwise, your guest VMs will not be able to acquire a license for NVIDIA vGPU software. For more information, refer to Migrating Licenses from a Legacy NVIDIA vGPU Software License Server in the NVIDIA License System documentation.

  • All versions of Microsoft Windows Server 2016 with Hyper-V role are no longer supported as a hypervisor.
  • All versions of Microsoft Windows Server 2016 are no longer supported as a guest OS.

This release family of NVIDIA vGPU software provides support for several NVIDIA GPUs on validated server hardware platforms, Microsoft Windows Server hypervisor software versions, and guest operating systems.

2.1. Supported NVIDIA GPUs and Validated Server Platforms

This release of NVIDIA vGPU software on Microsoft Windows Server provides support for several NVIDIA GPUs running on validated server hardware platforms. For a list of validated server platforms, refer to NVIDIA GRID Certified Servers.

The supported products for each type of NVIDIA vGPU software deployment depend on the GPU.

Note:

All GPUs that support graphics acceleration are supported as a secondary device in a bare-metal deployment. Tesla M6 is also supported as the primary display device in a bare-metal deployment.


Since 15.1: GPUs Based on the NVIDIA Ada Lovelace Architecture

GPU Supported NVIDIA vGPU Software Products1, 2, 3
Time-Sliced NVIDIA vGPU MIG-Backed NVIDIA vGPU DDA
NVIDIA L40 N/A N/A
  • vCS
  • vWS
  • vApps
Since 15.2: NVIDIA L4 N/A N/A
  • vCS
  • vWS
  • vApps
NVIDIA RTX 6000 Ada N/A N/A
  • vCS
  • vWS
  • vApps


GPUs Based on the NVIDIA Hopper Architecture

GPU Supported NVIDIA vGPU Software Products1, 2, 3
Time-Sliced NVIDIA vGPU MIG-Backed NVIDIA vGPU DDA
Since 15.2: H800 PCIe 80GB N/A N/A vCS
H100 PCIe 80GB N/A N/A vCS


GPUs Based on the NVIDIA Ampere Architecture

GPU Supported NVIDIA vGPU Software Products1, 2, 3
Time-Sliced NVIDIA vGPU MIG-Backed NVIDIA vGPU DDA
NVIDIA A800 PCIe 80GB N/A N/A vCS
NVIDIA A800 PCIe 80GB liquid cooled N/A N/A vCS
NVIDIA A800 HGX 80GB N/A N/A vCS
NVIDIA A100 PCIe 80GB N/A N/A vCS
NVIDIA A100 PCIe 80GB liquid cooled N/A N/A vCS
NVIDIA A100X N/A N/A vCS
NVIDIA A100 HGX 80GB N/A N/A vCS
NVIDIA A100 PCIe 40GB N/A N/A vCS
NVIDIA A100 HGX 40GB N/A N/A vCS
NVIDIA A404 N/A N/A
  • vCS
  • vWS
  • vApps
NVIDIA A30 N/A N/A vCS
NVIDIA A30X N/A N/A vCS
NVIDIA A16 N/A N/A
  • vCS
  • vWS
  • vApps
NVIDIA A10 N/A N/A
  • vCS
  • vWS
  • vApps
NVIDIA A2 N/A N/A
  • vCS
  • vWS
  • vApps
NVIDIA RTX A60004 N/A N/A
  • vCS
  • vWS
  • vApps
NVIDIA RTX A55004 N/A N/A
  • vCS
  • vWS
  • vApps
NVIDIA RTX A50004 N/A N/A
  • vCS
  • vWS
  • vApps


GPUs Based on the NVIDIA Turing Architecture

GPU Supported NVIDIA vGPU Software Products1, 2, 3
Time-Sliced NVIDIA vGPU MIG-Backed NVIDIA vGPU DDA
Tesla T4 N/A N/A
  • vCS
  • vWS
  • vApps
Quadro RTX 6000 4 N/A N/A
  • vCS
  • vWS
  • vApps
Quadro RTX 6000 passive4 N/A N/A
  • vCS
  • vWS
  • vApps
Quadro RTX 80004 N/A N/A
  • vCS
  • vWS
  • vApps
Quadro RTX 8000 passive4 N/A N/A
  • vCS
  • vWS
  • vApps


GPUs Based on the NVIDIA Volta Architecture

GPU Supported NVIDIA vGPU Software Products1, 2, 3
Time-Sliced NVIDIA vGPU MIG-Backed NVIDIA vGPU DDA
Tesla V100 SXM2 N/A N/A
  • vCS
  • vWS
  • vApps
Tesla V100 SXM2 32GB N/A N/A
  • vCS
  • vWS
  • vApps
Tesla V100 PCIe N/A N/A
  • vCS
  • vWS
  • vApps
Tesla V100 PCIe 32GB N/A N/A
  • vCS
  • vWS
  • vApps
Tesla V100S PCIe 32GB N/A N/A
  • vCS
  • vWS
  • vApps
Tesla V100 FHHL N/A N/A
  • vCS
  • vWS
  • vApps


GPUs Based on the NVIDIA Pascal™ Architecture

GPU Supported NVIDIA vGPU Software Products1, 2, 3
Time-Sliced NVIDIA vGPU MIG-Backed NVIDIA vGPU DDA
Tesla P4 N/A N/A
  • vCS
  • vWS
  • vApps
Tesla P6 N/A N/A
  • vCS
  • vWS
  • vApps
Tesla P40 N/A N/A
  • vCS
  • vWS
  • vApps
Tesla P100 PCIe 16 GB N/A N/A
  • vCS
  • vWS
  • vApps
Tesla P100 SXM2 16 GB N/A N/A
  • vCS
  • vWS
  • vApps
Tesla P100 PCIe 12GB N/A N/A
  • vCS
  • vWS
  • vApps


GPUs Based on the NVIDIA Maxwell Graphic Architecture

Note:

NVIDIA Virtual Compute Server (vCS) is not supported on GPUs based on the NVIDIA Maxwell™ graphic architecture.

GPU Supported NVIDIA vGPU Software Products1, 2, 3
Time-Sliced NVIDIA vGPU MIG-Backed NVIDIA vGPU DDA
Tesla M6 N/A N/A
  • vWS
  • vApps
Tesla M10 N/A N/A
  • vWS
  • vApps
Tesla M60 N/A N/A
  • vWS
  • vApps


2.1.1. Switching the Mode of a GPU that Supports Multiple Display Modes

Some GPUs support display-off and display-enabled modes but must be used in NVIDIA vGPU software deployments in display-off mode.

The GPUs listed in the following table support multiple display modes. As shown in the table, some GPUs are supplied from the factory in display-off mode, but other GPUs are supplied in a display-enabled mode.

GPU Mode as Supplied from the Factory
NVIDIA A40 Display-off
NVIDIA L40 Display-off
NVIDIA RTX 6000 Ada Display enabled
NVIDIA RTX A5000 Display enabled
NVIDIA RTX A5500 Display enabled
NVIDIA RTX A6000 Display enabled

A GPU that is supplied from the factory in display-off mode, such as the NVIDIA A40 GPU, might be in a display-enabled mode if its mode has previously been changed.

To change the mode of a GPU that supports multiple display modes, use the displaymodeselector tool, which you can request from the NVIDIA Display Mode Selector Tool page on the NVIDIA Developer website.

Note:

Only the following GPUs support the displaymodeselector tool:

  • NVIDIA A40
  • NVIDIA L40
  • NVIDIA RTX A5000
  • NVIDIA RTX 6000 Ada
  • NVIDIA RTX A5500
  • NVIDIA RTX A6000

Other GPUs that support NVIDIA vGPU software do not support the displaymodeselector tool and, unless otherwise stated, do not require display mode switching.

2.1.2. Switching the Mode of a Tesla M60 or M6 GPU

Tesla M60 and M6 GPUs support compute mode and graphics mode. NVIDIA vGPU requires GPUs that support both modes to operate in graphics mode.

Recent Tesla M60 GPUs and M6 GPUs are supplied in graphics mode. However, your GPU might be in compute mode if it is an older Tesla M60 GPU or M6 GPU or if its mode has previously been changed.

To configure the mode of Tesla M60 and M6 GPUs, use the gpumodeswitch tool provided with NVIDIA vGPU software releases. If you are unsure which mode your GPU is in, use the gpumodeswitch tool to find out the mode.

Note:

Only Tesla M60 and M6 GPUs support the gpumodeswitch tool. Other GPUs that support NVIDIA vGPU do not support the gpumodeswitch tool and, except as stated in Switching the Mode of a GPU that Supports Multiple Display Modes, do not require mode switching.

Even in compute mode, Tesla M60 and M6 GPUs do not support NVIDIA Virtual Compute Server vGPU types.

For more information, refer to gpumodeswitch User Guide.

2.2. Hypervisor Software Releases

This release supports only the hypervisor software versions listed in the table.
Note:

If a specific release, even an update release, is not listed, it’s not supported.

Software Version Supported Notes

Microsoft Windows Server 2022

Windows Server 2022 with Hyper-V role

 

Microsoft Windows Server 2019

Windows Server 2019 with Hyper-V role

 

2.3. Guest OS Support

NVIDIA vGPU software supports several Windows releases and Linux distributions as a guest OS using GPU pass-through.

Microsoft Windows Server with Hyper-V role supports GPU pass-through over Microsoft Virtual PCI bus. This bus is supported through paravirtualized drivers.

Note:

Use only a guest OS release that is listed as supported by NVIDIA vGPU software with your virtualization software. To be listed as supported, a guest OS release must be supported not only by NVIDIA vGPU software, but also by your virtualization software. NVIDIA cannot support guest OS releases that your virtualization software does not support.

NVIDIA vGPU software supports only 64-bit guest operating systems. No 32-bit guest operating systems are supported.


2.3.1. Windows Guest OS Support

NVIDIA vGPU software supports only the 64-bit Windows releases listed as a guest OS on Microsoft Windows Server.

Note:

If a specific release, even an update release, is not listed, it’s not supported.

  • Windows Server 2019
  • Since 15.1: Windows 11 22H2 and all Windows 11 releases supported by Microsoft up to and including this release
  • Windows 11 21H2
  • Windows 10 2022 Update (22H2) and all Windows 10 releases supported by Microsoft up to and including this release

2.3.2. Linux Guest OS Support

NVIDIA vGPU software supports only the 64-bit Linux distributions listed as a guest OS on Microsoft Windows Server.

Note:

If a specific release, even an update release, is not listed, it’s not supported.

  • Since 15.3: Red Hat Enterprise Linux 8.8
  • 15.0-15.2 only: Red Hat Enterprise Linux 8.7
  • Red Hat Enterprise Linux 8.6
  • 15.0-15.2 only: Red Hat Enterprise Linux 8.4
  • Red Hat Enterprise Linux 7.9
  • Rocky Linux 8.4
  • Deprecated: CentOS Linux 8 (2105)
  • Deprecated: CentOS 7.6-7.8
  • Ubuntu 20.04 LTS
  • Ubuntu 18.04 LTS
  • Ubuntu 16.04 LTS
  • SUSE Linux Enterprise Server 15 SP2
  • SUSE Linux Enterprise Server 12 SP2

3.1. 15.0-15.3 Only: vCS license acquisition from CLS fails for general-purpose GPUs in pass-through mode on Windows

Description

A request to a Cloud License Service (CLS) instance for a vCS license from a Windows VM fails. This issue affects only Windows guest VMs that are configured with a general-purpose GPU in pass-through mode. A general-purpose GPU supports graphics acceleration in addition to compute workloads. When this issue occurs, NVIDIA License System (NLS) hangs after it is initialized.

Status

Resolved in NVIDIA vGPU software15.4

Ref. #

4253360

3.2. 15.0-15.2 Only: Applications crash after migrations of VMs configured with vGPUs based on the NVIDIA Hopper architecture

Description

After a VM configured with one or more vGPUs based on the NVIDIA Hopper architecture is migrated, applications on the destination host might crash immediately after the migration. This issue affects only MIG-backed vGPUs on GPUs based on the NVIDIA Hopper architecture and does not affect all migrations. When this issue occurs, the following messages might be written to the log files on the hypervisor host:

  • VGPU message 108 failed
  • VGPU message 111 failed

Status

Resolved in NVIDIA vGPU software 15.3

Note:

To avoid this issue, the Virtual GPU Manager from NVIDIA vGPU software 15.3 to be running on the source host and the destination host.


Ref. #

4059416

3.3. 15.0-15.2 Only: NVWMI floods Windows application logs with <a href="#bug-3896627-nvwmi-floods-windows-applicaton-logs" target="_self">Pipe operation failed</a> messages

Description

The NVIDIA Enterprise Management Toolkit (NVWMI) floods Windows application logs with Pipe operation failed messages. This issue affects only Windows guest VMs and has no functional impact other than the flooding of the Windows application logs.

Status

Resolved in NVIDIA vGPU software 15.3

Ref. #

3896627

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

Description

On all supported Windows Server guest OS releases, NVIDIA Control Panel crashes if a user session is disconnected and then reconnected while NVIDIA Control Panel is open.

Version

This issue affects all supported Windows Server guest OS releases.

Status

Open

Ref. #

4086605

3.5. 15.0-15.2 Only: Remote desktop connection is lost and the NVIDIA vGPU software graphics driver is unloaded

Description

The remote desktop connection is lost and the NVIDIA vGPU software graphics driver is unloaded after an attempt to access a VM over RDP and VMware Horizon agent direct connect. After an attempt to log in again, a black screen is displayed. When this issue occurs, the following errors are written to the log files on the guest VM:

  • A timeout detection and recovery (TDR) error:
    Copy
    Copied!
                

    vmiop_log: (0x0): Timeout occurred, reset initiated. vmiop_log: (0x0): TDR_DUMP:0x52445456 0x006907d0 0x000001cc 0x00000001

  • XID error 43:
    Copy
    Copied!
                

    vmiop_log: (0x0): XID 43 detected on physical_chid

  • vGPU error 22:
    Copy
    Copied!
                

    vmiop_log: (0x0): VGPU message 22 failed

  • Guest driver unloaded error:
    Copy
    Copied!
                

    vmiop_log: (0x0): Guest driver unloaded!

Workaround

To recover from this issue, reboot the VM.

Since 15. 2: To prevent this issue from occurring, disable translation lookaside buffer (TLB) invalidation by setting the vGPU plugin parameter tlb_invalidate_enabled to 0.

Status

Resolved in NVIDIA vGPU software 15.3

Ref. #

3596327

3.6.  NVIDIA vGPU software graphics driver for Windows sends a remote call to <a href="#bug-4031840-windows-driver-calls-ngx-download-nvidia-com" target="_self">ngx.download.nvidia.com</a>

Description

After the NVIDIA vGPU software graphics for windows has been installed in the guest VM, the driver sends a remote call to ngx.download.nvidia.com to download and install additional components. Such a remote call might be a security issue.

Workaround

Before running the NVIDIA vGPU software graphics driver installer, disable the remote call to ngx.download.nvidia.com by setting the following Windows registry key:

Copy
Copied!
            

[HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\NGXCore] "EnableOTA"=dword:00000000

Note:

If this Windows registry key is set to 1 or deleted, the remote call to ngx.download.nvidia.com is enabled again.


Status

Open

Ref. #

4031840

3.7. 15.0, 15.1 Only: Windows VMs fail to acquire a license in environments with multiple active desktop sessions

Description

A race condition in the NVIDIA vGPU softwaregraphics driver for Windows can cause Windows VMs to fail to acquire a license. This issue occurs in environments where multiple active desktop sessions are trying to acquire a license simultaneously. When this issue occurs, the following error message is written to licensing event log on the client:

Copy
Copied!
            

Mismatch between client and server with respect to licenses held. Returning the licenses

Version

This issue affects only Windows guest VMs.

Status

Resolved in NVIDIA vGPU software 15.2

Ref. #

3835855

3.8. 15.0, 15.1 Only: The NVIDIA vGPU software graphics driver for Windows cannot drive the display

Description

After a remoting session has been reconnected to several times or the screen has been resized several times, the NVIDIA vGPU software graphics driver can be randomly left in a state where it cannot drive the display. This issue affects only Windows guest VMs. Linux guest VMs are not affected.

Because the NVIDIA vGPU software graphics driver is not driving the display, this issue can cause visible performance degradation.

Status

Resolved in NVIDIA vGPU software 15.2

Ref. #

3956112

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

Description

Multiple RDP session reconnections in a Windows Server 2022 guest VM can consume all the frame buffer of a vGPU or physical GPU. When this issue occurs, users' screens becomes black, their sessions are disconnected but left intact, and they cannot log on again. The following error message is written to the event log on the hypervisor host:

Copy
Copied!
            

The Desktop Window Manager process has exited. (Process exit code: 0xe0464645, Restart count: 1, Primary display device ID: )

Version

This issue affects only the Windows Server 2022 guest OS.

Workaround

Periodically restart the Windows Server 2022 guest VM to prevent all frame buffer from being consumed.

Status

Open

Ref. #

3583766

3.10. NLS client fails to acquire a license with the error <a href="#bug-3859889-nls-client-cannot-get-license-response-time-expired" target="_self">The allowed time to process response has expired</a>

Description

A licensed client of NVIDIA License System (NLS) fails to acquire a license with the error The allowed time to process response has expired. This error can affect clients of a Cloud License Service (CLS) instance or a Delegated License Service (DLS) instance.

This error occurs when the time difference between the system clocks on the client and the server that hosts the CLS or DLS instance is greater than 10 minutes. A common cause of this error is the failure of either the client or the server to adjust its system clock when daylight savings time begins or ends. The failure to acquire a license is expected to prevent clock windback from causing licensing errors.

Workaround

Ensure that system clock time of the client and any server that hosts a DLS instance match the current time in the time zone where they are located. To prevent this error from occurring when daylight savings time begins or ends, enable the option to automatically adjust the system clock for daylight savings time:

  • Windows: Set the Adjust for daylight saving time automatically option.
  • Linux: Use the hwclock command.

Status

Not a bug

Ref. #

3859889

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

Description

In an environment with multiple active desktop sessions, the Manage License page of NVIDIA Control Panel shows that a licensed system is unlicensed. However, the nvidia-smi command and the management interface of the NVIDIA vGPU software license server correctly show that the system is licensed. When an active session is disconnected and reconnected, the NVIDIA Display Container service crashes.

The Manage License page incorrectly shows that the system is unlicensed because of stale data in NVIDIA Control Panel in an environment with multiple sessions. The data is stale because NVIDIA Control Panel fails to get and update the settings for remote sessions when multiple sessions or no sessions are active in the VM. The NVIDIA Display Container service crashes when a session is reconnected because the session is not active at the moment of reconnection.

Status

Open

Ref. #

3761243

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

Description

VP9 and AV1 decoding with web browsers are not supported on Microsoft Windows Server 2019 and later supported releases. This issue occurs because starting with Windows Server 2019, the required codecs are not included with the OS and are not available through the Microsoft Store app. As a result, hardware decoding is not available for viewing YouTube videos or using collaboration tools such as Google Meet in a web browser.

Version

This issue affects Microsoft Windows Server releases starting with Windows Server 2019.

Status

Not an NVIDIA bug

Ref. #

200756564

3.13. 15.0, 15.1 Only: NVIDIA Control Panel is started only for the RDP user that logs on first

Description

On all supported Windows Server guest OS releases, NVIDIA Control Panel is started only for the RDP user that logs on first. Other users cannot start NVIDIA Control Panel. If more than one RDP user is logged on when NVIDIA Control Panel is started, it always opens in the session of the RDP user that logged on first, irrespective of which user started NVIDIA Control Panel. Furthermore, on Windows Server 2016, NVIDIA Control Panel crashes if a user session is disconnected and then reconnected while NVIDIA Control Panel is open.

Version

This issue affects all supported Windows Server guest OS releases.

Status

Resolved in NVIDIA vGPU software 15.2

Ref. #

3334310

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

Description

After the NVIDIA vGPU software graphics driver for Linux is upgraded from an RPM package in a licensed VM, licensing fails. The nvidia-smi vgpu -q command shows the driver version and license status as N/A. Restarting the nvidia-gridd service fails with a Unit not found error.

Workaround

Perform a clean installation of the NVIDIA vGPU software graphics driver for Linux from an RPM package.

  1. Remove the currently installed driver.

  2. Install the new version of the driver.

    Copy
    Copied!
                

    $ rpm -iv nvidia-linux-grid-525_525.147.05_amd64.rpm

Status

Open

Ref. #

3512766

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

Description

After the NVIDIA vGPU software graphics driver for Linux is upgraded from a Debian package, the driver is not loaded into the VM.

Workaround

Use one of the following workarounds to load the driver into the VM:

  • Reboot the VM.

Status

Not a bug

Ref. #

200748806

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

Description

If a proxy is set with a system environment variable such as HTTP_PROXY or HTTPS_PROXY, a licensed client might fail to acquire a license.

Workaround

Perform this workaround on each affected licensed client.

  1. Add the address of the NVIDIA vGPU software license server to the system environment variable NO_PROXY.

    The address must be specified exactly as it is specified in the client's license server settings either as a fully-qualified domain name or an IP address. If the NO_PROXY environment variable contains multiple entries, separate the entries with a comma (,).

    If high availability is configured for the license server, add the addresses of the primary license server and the secondary license server to the system environment variable NO_PROXY.

  2. Restart the NVIDIA driver service that runs the core NVIDIA vGPU software logic.

    • On Windows, restart the NVIDIA Display Container service.
    • On Linux, restart the nvidia-gridd service.

Status

Closed

Ref. #

200704733

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

Description

Disconnected sessions cannot be reconnected or might be reconnected very slowly when the NVIDIA Enterprise Management Toolkit (NVWMI) is installed. This issue affects Citrix Virtual Apps and Desktops and VMware Horizon sessions on Windows guest VMs.

Workaround

Uninstall NVWMI.

Status

Open

Ref. #

3262923

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

Description

If NVIDIA licensing information is not configured on the system, any attempt to start NVIDIA Control Panel by right-clicking on the desktop within 30 seconds of the VM being started fails.

Workaround

Restart the VM and wait at least 30 seconds before trying to launch NVIDIA Control Panel.

Status

Open

Ref. #

200623179

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

Description

When a window is dragged across the desktop in a Citrix Virtual Apps and Desktops session, corruption of the session in the form of residual window borders occurs.

Version

This issue affects only Citrix Virtual Apps and Desktops version 7 2003

Workaround

Use Citrix Virtual Apps and Desktops version 7 1912 or 2006.

Status

Not an NVIDIA bug

Ref. #

200608675

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

Description

On Linux, the frame rate might drop to 1 frame per second (FPS) after NVIDIA vGPU software has been running for several minutes. Only some applications are affected, for example, glxgears. Other applications, such as Unigine Heaven, are not affected. This behavior occurs because Display Power Management Signaling (DPMS) for the Xorg server is enabled by default and the display is detected to be inactive even when the application is running. When DPMS is enabled, it enables power saving behavior of the display after several minutes of inactivity by setting the frame rate to 1 FPS.

Workaround

  1. If necessary, stop the Xorg server.

    Copy
    Copied!
                

    # /etc/init.d/xorg stop

  2. In a plain text editor, edit the /etc/X11/xorg.conf file to set the options to disable DPMS and disable the screen saver.

    1. In the Monitor section, set the DPMS option to false.
      Copy
      Copied!
                  

      Option "DPMS" "false"

    2. At the end of the file, add a ServerFlags section that contains option to disable the screen saver.
      Copy
      Copied!
                  

      Section "ServerFlags" Option "BlankTime" "0" EndSection

    3. Save your changes to /etc/X11/xorg.conf file and quit the editor.
  3. Start the Xorg server.

    Copy
    Copied!
                

    # etc/init.d/xorg start

Status

Open

Ref. #

200605900

3.21. Microsoft DDA fails with some GPUs

Description

Microsoft Discrete Device Assignment (DDA) fails with GPUs that have more than 16 GB of GPU memory. After the NVIDIA vGPU software graphics driver is installed in the guest VM, a second display device appears on the GPU and the driver prompts for a reboot. After the reboot, the device disappears and the Microsoft Hyper-V Video device appears.

This issue occurs because less memory-mapped input/output (MMIO) space is configured for the operating system than the device requires.

Workaround

Perform this workaround in a Windows Power Shell window on the hypervisor host.

Set the upper MMIO space to the amount that the device requires to allow all of the MMIO to be mapped. Upper MMIO space starts at approximately 64 GB in address space.

Copy
Copied!
            

Set-VM –HighMemoryMappedIoSpace mmio-space –VMName vm-name

mmio-space
The amount of MMIO space that the device requires, appended with the appropriate unit of measurement, for example, 64GB for 64 GB of MMIO space.

The required amount of MMIO space depends on the amount of BAR1 memory on the installed GPUs and the number of GPUs assigned to the VM as follows:

mmio-space = 2 ˟ gpu-bar1-memory ˟ assigned-gpus

gpu-bar1-memory
The amount of BAR1 memory on one of the installed GPUs. For example, in a server in which eight GPUs are installed and each GPU has 32 GB of BAR1 memory, gpu-bar1-memory is 32 GB.
assigned-gpus
The number of GPUs assigned to the VM.
vm-name
The name of the VM to which the GPU is assigned.

The following example sets the upper MMIO space to 64 GB for the VM named mygpuvm, to which one GPU with 32 GB of BAR1 memory is assigned.

Copy
Copied!
            

Set-VM –HighMemoryMappedIoSpace 64GB –VMName mygpuvm

For more information, see Deploy graphics devices using Discrete Device Assignment on the Microsoft technical documentation site.

Status

Not an NVIDIA bug

Ref. #

2812853

3.22. DWM crashes randomly occur in Windows VMs

Description

Desktop Windows Manager (DWM) crashes randomly occur in Windows VMs, causing a blue-screen crash and the bug check CRITICAL_PROCESS_DIED. Computer Management shows problems with the primary display device.

Version

This issue affects Windows 10 1809, 1903 and 1909 VMs.

Status

Not an NVIDIA bug

Ref. #

2730037

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

Description

After the Linux kernel is upgraded (for example by running sudo apt full-upgrade) with Dynamic Kernel Module Support (DKMS) enabled, the nvidia-smi command fails to run. If DKMS is enabled, an upgrade to the Linux kernel triggers a rebuild of the NVIDIA vGPU software graphics driver. The rebuild of the driver fails because the compiler version is incorrect. Any attempt to reinstall the driver fails because the kernel fails to build.

When the failure occurs, the following messages are displayed:

Copy
Copied!
            

-> Installing DKMS kernel module: ERROR: Failed to run `/usr/sbin/dkms build -m nvidia -v 525.60.13 -k 5.3.0-28-generic`: Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area... 'make' -j8 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=5.3.0-28-generic IGNORE_CC_MISMATCH='' modules...(bad exit status: 2) ERROR (dkms apport): binary package for nvidia: 525.60.13 not found Error! Bad return status for module build on kernel: 5.3.0-28-generic (x86_64) Consult /var/lib/dkms/nvidia/ 525.60.13/build/make.log for more information. -> error. ERROR: Failed to install the kernel module through DKMS. No kernel module was installed; please try installing again without DKMS, or check the DKMS logs for more information. ERROR: Installation has failed. Please see the file '/var/log/nvidia-installer.log' for details. You may find suggestions on fixing installation problems in the README available on the Linux driver download page at www.nvidia.com.


Workaround

When installing the NVIDIA vGPU software graphics driver with DKMS enabled, use one of the following workarounds:

  • Before running the driver installer, install the dkms package, then run the driver installer with the -dkms option.
  • Run the driver installer with the --no-cc-version-check option.

Status

Not a bug.

Ref. #

2836271

3.24. Blue screen crash occurs or no devices are found after VM reset

Description

If a VM on Microsoft Windows Server with Hyper-V role is reset from the hypervisor host, a blue screen crash (BSOD) occurs on Windows VMs and the nvidia-smi command reports No devices were found on Linux VMs. This issue occurs only on Windows Server 2019 with Tesla T4 GPUs with SRIOV enabled, Quadro RTX 8000 passive GPUs, and Quadro RTX 6000 passive GPUs.

Workaround

Contact NVIDIA Enterprise Support for a workaround for this issue, referencing the knowledge base article Workaround for Blue Screen Crashes On Hyper-V DDA With SRIOV-Enabled GPUs. This article is available only to NVIDIA Enterprise Support personnel.

Status

Not an NVIDIA bug

Ref. #

200567935

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

Description

Because of a known limitation with NvFBC, a frame capture while the interactive logon message is displayed returns a blank screen.

An NvFBC session can capture screen updates that occur after the session is created. Before the logon message appears, there is no screen update after the message is shown and, therefore, a black screen is returned instead. If the NvFBC session is created after this update has occurred, NvFBC cannot get a frame to capture.

Workaround

Press Enter or wait for the screen to update for NvFBC to capture the frame.

Status

Not a bug

Ref. #

2115733

3.26. RDS sessions do not use the GPU with some Microsoft Windows Server releases

Description

When some releases of Windows Server are used as a guest OS, Remote Desktop Services (RDS) sessions do not use the GPU. With these releases, the RDS sessions by default use the Microsoft Basic Render Driver instead of the GPU. This default setting enables 2D DirectX applications such as Microsoft Office to use software rendering, which can be more efficient than using the GPU for rendering. However, as a result, 3D applications that use DirectX are prevented from using the GPU.

Version

  • Windows Server 2019
  • Windows Server 2016
  • Windows Server 2012

Solution

Change the local computer policy to use the hardware graphics adapter for all RDS sessions.

  1. Choose Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment.

  2. Set the Use the hardware default graphics adapter for all Remote Desktop Services sessions option.

3.27. A segmentation fault in DBus code causes <a href="#bug-1895945-nvidia-gridd-segfaults-in-dbus-code-on-centos-6-8-6-9" target="_self">nvidia-gridd</a> to exit on Red Hat Enterprise Linux and CentOS

Description

On Red Hat Enterprise Linux 6.8 and 6.9, and CentOS 6.8 and 6.9, a segmentation fault in DBus code causes the nvidia-gridd service to exit.

The nvidia-gridd service uses DBus for communication with NVIDIA X Server Settings to display licensing information through the Manage License page. Disabling the GUI for licensing resolves this issue.

To prevent this issue, the GUI for licensing is disabled by default. You might encounter this issue if you have enabled the GUI for licensing and are using Red Hat Enterprise Linux 6.8 or 6.9, or CentOS 6.8 and 6.9.

Version

Red Hat Enterprise Linux 6.8 and 6.9

CentOS 6.8 and 6.9

Status

Open

Ref. #

  • 200358191
  • 200319854
  • 1895945

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

Description

By default, the Manage License option is not available in NVIDIA X Server Settings. This option is missing because the GUI for licensing on Linux is disabled by default to work around the issue that is described in A segmentation fault in DBus code causes nvidia-gridd to exit on Red Hat Enterprise Linux and CentOS.

Workaround

This workaround requires sudo privileges.

Note:

Do not use this workaround with Red Hat Enterprise Linux 6.8 and 6.9 or CentOS 6.8 and 6.9. To prevent a segmentation fault in DBus code from causing the nvidia-gridd service from exiting, the GUI for licensing must be disabled with these OS versions.

If you are licensing a physical GPU for vCS, you must use the configuration file /etc/nvidia/gridd.conf.

  1. If NVIDIA X Server Settings is running, shut it down.
  2. If the /etc/nvidia/gridd.conf file does not already exist, create it by copying the supplied template file /etc/nvidia/gridd.conf.template.

  3. As root, edit the /etc/nvidia/gridd.conf file to set the EnableUI option to TRUE.

  4. Start the nvidia-gridd service.

    Copy
    Copied!
                

    # sudo service nvidia-gridd start

When NVIDIA X Server Settings is restarted, the Manage License option is now available.

Status

Open

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

Description

NVIDIA vGPU software licenses remain checked out on the license server when non-persistent VMs are forcibly powered off.

The NVIDIA service running in a VM returns checked out licenses when the VM is shut down. In environments where non-persistent licensed VMs are not cleanly shut down, licenses on the license server can become exhausted. For example, this issue can occur in automated test environments where VMs are frequently changing and are not guaranteed to be cleanly shut down. The licenses from such VMs remain checked out against their MAC address for seven days before they time out and become available to other VMs.

Resolution

If VMs are routinely being powered off without clean shutdown in your environment, you can avoid this issue by shortening the license borrow period. To shorten the license borrow period, set the LicenseInterval configuration setting in your VM image. For details, refer to Virtual GPU Client Licensing User Guide.

Status

Closed

Ref. #

1694975

Notice

This document is provided for information purposes only and shall not be regarded as a warranty of a certain functionality, condition, or quality of a product. NVIDIA Corporation (“NVIDIA”) makes no representations or warranties, expressed or implied, as to the accuracy or completeness of the information contained in this document and assumes no responsibility for any errors contained herein. NVIDIA shall have no liability for the consequences or use of such information or for any infringement of patents or other rights of third parties that may result from its use. This document is not a commitment to develop, release, or deliver any Material (defined below), code, or functionality.

NVIDIA reserves the right to make corrections, modifications, enhancements, improvements, and any other changes to this document, at any time without notice.

Customer should obtain the latest relevant information before placing orders and should verify that such information is current and complete.

NVIDIA products are sold subject to the NVIDIA standard terms and conditions of sale supplied at the time of order acknowledgement, unless otherwise agreed in an individual sales agreement signed by authorized representatives of NVIDIA and customer (“Terms of Sale”). NVIDIA hereby expressly objects to applying any customer general terms and conditions with regards to the purchase of the NVIDIA product referenced in this document. No contractual obligations are formed either directly or indirectly by this document.

NVIDIA products are not designed, authorized, or warranted to be suitable for use in medical, military, aircraft, space, or life support equipment, nor in applications where failure or malfunction of the NVIDIA product can reasonably be expected to result in personal injury, death, or property or environmental damage. NVIDIA accepts no liability for inclusion and/or use of NVIDIA products in such equipment or applications and therefore such inclusion and/or use is at customer’s own risk.

NVIDIA makes no representation or warranty that products based on this document will be suitable for any specified use. Testing of all parameters of each product is not necessarily performed by NVIDIA. It is customer’s sole responsibility to evaluate and determine the applicability of any information contained in this document, ensure the product is suitable and fit for the application planned by customer, and perform the necessary testing for the application in order to avoid a default of the application or the product. Weaknesses in customer’s product designs may affect the quality and reliability of the NVIDIA product and may result in additional or different conditions and/or requirements beyond those contained in this document. NVIDIA accepts no liability related to any default, damage, costs, or problem which may be based on or attributable to: (i) the use of the NVIDIA product in any manner that is contrary to this document or (ii) customer product designs.

No license, either expressed or implied, is granted under any NVIDIA patent right, copyright, or other NVIDIA intellectual property right under this document. Information published by NVIDIA regarding third-party products or services does not constitute a license from NVIDIA to use such products or services or a warranty or endorsement thereof. Use of such information may require a license from a third party under the patents or other intellectual property rights of the third party, or a license from NVIDIA under the patents or other intellectual property rights of NVIDIA.

Reproduction of information in this document is permissible only if approved in advance by NVIDIA in writing, reproduced without alteration and in full compliance with all applicable export laws and regulations, and accompanied by all associated conditions, limitations, and notices.

THIS DOCUMENT AND ALL NVIDIA DESIGN SPECIFICATIONS, REFERENCE BOARDS, FILES, DRAWINGS, DIAGNOSTICS, LISTS, AND OTHER DOCUMENTS (TOGETHER AND SEPARATELY, “MATERIALS”) ARE BEING PROVIDED “AS IS.” NVIDIA MAKES NO WARRANTIES, EXPRESSED, IMPLIED, STATUTORY, OR OTHERWISE WITH RESPECT TO THE MATERIALS, AND EXPRESSLY DISCLAIMS ALL IMPLIED WARRANTIES OF NONINFRINGEMENT, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE. TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILL NVIDIA BE LIABLE FOR ANY DAMAGES, INCLUDING WITHOUT LIMITATION ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF ANY USE OF THIS DOCUMENT, EVEN IF NVIDIA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Notwithstanding any damages that customer might incur for any reason whatsoever, NVIDIA’s aggregate and cumulative liability towards customer for the products described herein shall be limited in accordance with the Terms of Sale for the product.

VESA DisplayPort

DisplayPort and DisplayPort Compliance Logo, DisplayPort Compliance Logo for Dual-mode Sources, and DisplayPort Compliance Logo for Active Cables are trademarks owned by the Video Electronics Standards Association in the United States and other countries.

HDMI

HDMI, the HDMI logo, and High-Definition Multimedia Interface are trademarks or registered trademarks of HDMI Licensing LLC.

OpenCL

OpenCL is a trademark of Apple Inc. used under license to the Khronos Group Inc.

Trademarks

NVIDIA, the NVIDIA logo, NVIDIA GRID, NVIDIA GRID vGPU, NVIDIA Maxwell, NVIDIA Pascal, NVIDIA Turing, NVIDIA Volta, GPUDirect, Quadro, and Tesla are trademarks or registered trademarks of NVIDIA Corporation in the U.S. and other countries. Other company and product names may be trademarks of the respective companies with which they are associated.

1 The supported products are as follows:
  • vCS: NVIDIA Virtual Compute Server
  • vWS: NVIDIA RTX Virtual Workstation
  • vPC: NVIDIA Virtual PC
  • vApps: NVIDIA Virtual Applications

2 N/A indicates that the deployment is not supported.

3vApps is supported only on Windows operating systems.

4 This GPU is supported only in displayless mode. In displayless mode, local physical display connectors are disabled.

© 2013-2024 NVIDIA Corporation & affiliates. All rights reserved. Last updated on Mar 26, 2024.