1. Release Notes

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

The releases in this release family of NVIDIA vGPU software include the software listed in the following table:

Software 6.0 6.1 6.2 6.3
NVIDIA Virtual GPU Manager for the Nutanix AHV releases listed in Hypervisor Software Releases 390.42 390.57 390.72 390.94
NVIDIA Windows driver 391.03 391.58 391.81 392.05
NVIDIA Linux driver 390.42 390.57 390.75 390.96
CAUTION:

If you install the wrong NVIDIA vGPU software packages for the version of Nutanix AHV you are using, NVIDIA Virtual GPU Manager will fail to load.

The releases of the vGPU Manager and guest VM drivers that you install must be compatible. Different versions of the vGPU Manager and guest VM driver from within the same main release branch can be used together. For example, you can use the vGPU Manager from release 6.1 with guest VM drivers from release 6.0. However, versions of the vGPU Manager and guest VM driver from different main release branches cannot be used together. For example, you cannot use the vGPU Manager from release 6.1 with guest VM drivers from release 5.2.

See VM running older NVIDIA vGPU drivers fails to initialize vGPU when booted.

This requirement does not apply to the NVIDIA vGPU software license sever. All releases of NVIDIA vGPU software are compatible with all releases of the license server.

Updates in Release 6.0

New Features in Release 6.0

  • New -2B vGPU type for each supported GPU
  • vGPU support for NVML accounting functions
  • vGPU support for nvidia-smi accounting modes
  • Change of default scheduler to best effort scheduler for GPUs based on the NVIDIA® Pascal™ architecture
  • Change of maximum resolution for unlicensed GPUs based on the Pascal architecture to 1280×1024
  • Plain-text logging on Windows of significant licensing events
  • New setting EnableLogging for disabling or enabling logging of significant licensing events
  • Miscellaneous bug fixes

Hardware and Software Support Introduced in Release 6.0

  • Support for Windows 10 Fall Creators Update (1709) as a guest OS

Updates in Release 6.1

New Features in Release 6.1

  • Change in behavior to enable logging of licensing events on Windows by default
  • Miscellaneous bug fixes

Updates in Release 6.2

New Features in Release 6.2

  • New -2B4 vGPU type, which supports up to four displays at resolutions up to 2560×1600 for each supported GPU
  • Relaxation of restrictions on unlicensed vGPUs to allow screen resolutions higher than 1280×1024
  • Miscellaneous bug fixes

Hardware and Software Support Introduced in Release 6.2

  • Support for Nutanix AOS Hypervisor (AHV) 5.6 and 5.8

Updates in Release 6.3

New Features in Release 6.3

  • Inclusion of the name and version of the licensed product in logged license acquisition events
  • Miscellaneous bug fixes

2. Validated Platforms

This release family of NVIDIA vGPU software provides support for several NVIDIA GPUs on validated server hardware platforms, Nutanix AHV hypervisor software versions, and guest operating systems. It also supports the version of NVIDIA CUDA Toolkit that is compatible with R390 drivers.

Supported NVIDIA GPUs and Validated Server Platforms

This release of NVIDIA vGPU software provides support for the following NVIDIA GPUs on Nutanix AHV, running on validated Nutanix NX series server hardware platforms:

  • Tesla M10
  • Tesla M60
  • Tesla P40

For a list of validated server platforms, refer to NVIDIA GRID Certified Nutanix Servers.

Note:

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.

Hypervisor Software Releases

This release is supported on the Nutanix AHV releases listed in the table.

Note: Updates to a base release of Nutanix AHV are compatible with the base release and can also be used with this version of NVIDIA vGPU software unless expressly stated otherwise.
Software Releases Supported
Since 6.2: Nutanix AOS Hypervisor (AHV) 5.8 5.8 RTM and compatible 5.8.x updates
Since 6.2: Nutanix AOS Hypervisor (AHV) 5.6 5.6 RTM and compatible 5.6.x updates
Nutanix AOS Hypervisor (AHV) 5.5 5.5 RTM and compatible 5.5.x updates

Guest OS Support

NVIDIA vGPU software supports several Windows releases and Linux distributions as a guest OS. The supported guest operating systems depend on the hypervisor software version.

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.

In pass-through mode, GPUs based on the Pascal architecture or Volta architecture support only 64-bit guest operating systems. No 32-bit guest operating systems are supported in pass-through mode for these GPUs.

Windows Guest OS Support

NVIDIA vGPU software supports only the Windows releases listed in the table as a guest OS on Nutanix AHV. The releases of Nutanix AHV for which a Windows release is supported depend on whether NVIDIA vGPU or pass-through GPU is used. When configured for NVIDIA vGPU, GPUs based on the Volta architecture support only 64-bit Windows guest operating systems. No 32-bit Windows guest operating systems are supported for these GPUs when configured for NVIDIA vGPU.

Note:

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

Guest OS NVIDIA vGPU - Nutanix AHV Releases Pass-Through GPU - Nutanix AHV Releases
Windows Server 2016 1607, 1709

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Windows Server 2012 R2

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Windows Server 2008 R2

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Windows 10 RTM (1507), November Update (1511), Anniversary Update (1607), Creators Update (1703), Fall Creators Update (1709) (64-bit)

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Windows 10 RTM (1507), November Update (1511), Anniversary Update (1607), Creators Update (1703), Fall Creators Update (1709) (32-bit)

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Supported only on GPUs based on the Maxwell architecture

Windows 8.1 Update (64-bit)

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Windows 8.1 Update (32-bit)

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Supported only on GPUs based on the Maxwell architecture

Windows 8.1 (64-bit)

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Windows 8.1 (32-bit)

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Supported only on GPUs based on the Maxwell and Pascal architectures

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Supported only on GPUs based on the Maxwell architecture

Windows 8 (64-bit)

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Windows 8 (32-bit)

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Supported only on GPUs based on the Maxwell and Pascal architectures

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Supported only on GPUs based on the Maxwell architecture

Windows 7 (64-bit)

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Windows 7 (32-bit)

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Supported only on GPUs based on the Maxwell and Pascal architectures

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Supported only on GPUs based on the Maxwell architecture

Linux Guest OS Support

NVIDIA vGPU software supports only the Linux distributions listed in the table as a guest OS on Nutanix AHV. The releases of Nutanix AHV for which a Linux release is supported depend on whether NVIDIA vGPU or pass-through GPU is used.

Note:

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

Guest OS NVIDIA vGPU - Nutanix AHV Releases Pass-Through GPU - Nutanix AHV Releases
Red Hat Enterprise Linux 7.0-7.4

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Since 6.1: Red Hat Enterprise Linux 7.5

Since 6.2: 5.8, 5.6, 5.5

6.1 only: 5.5

Since 6.2: 5.8, 5.6, 5.5

6.1 only: 5.5

CentOS 7.0-7.4

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Since 6.1: CentOS 7.5

Since 6.2: 5.8, 5.6, 5.5

6.1 only: 5.5

Since 6.2: 5.8, 5.6, 5.5

6.1 only: 5.5

Ubuntu 16.04 LTS

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Ubuntu 14.04 LTS

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

Since 6.2: 5.8, 5.6, 5.5

6.0, 6.1 only: 5.5

NVIDIA CUDA Toolkit Version Support

The releases in this release family of NVIDIA vGPU software support NVIDIA CUDA Toolkit 9.1.

For more information about NVIDIA CUDA Toolkit, see CUDA Toolkit 9.1 Documentation.

3. Known Product Limitations

Known product limitations for this release of NVIDIA vGPU software are described in the following sections.

vGPU profiles with 512 Mbytes or less of frame buffer support only 1 virtual display head on Windows 10

Description

To reduce the possibility of memory exhaustion, vGPU profiles with 512 Mbytes or less of frame buffer support only 1 virtual display head on a Windows 10 guest OS.

The following vGPU profiles have 512 Mbytes or less of frame buffer:

  • Tesla M6-0B, M6-0Q
  • Tesla M10-0B, M10-0Q
  • Tesla M60-0B, M60-0Q

Workaround

Use a profile that supports more than 1 virtual display head and has at least 1 Gbyte of frame buffer.

NVENC requires at least 1 Gbyte of frame buffer

Description

Using the frame buffer for the NVIDIA hardware-based H.264/HEVC video encoder (NVENC) may cause memory exhaustion with vGPU profiles that have 512 Mbytes or less of frame buffer. To reduce the possibility of memory exhaustion, NVENC is disabled on profiles that have 512 Mbytes or less of frame buffer. Application GPU acceleration remains fully supported and available for all profiles, including profiles with 512 MBytes or less of frame buffer. NVENC support from both Citrix and VMware is a recent feature and, if you are using an older version, you should experience no change in functionality.

The following vGPU profiles have 512 Mbytes or less of frame buffer:

  • Tesla M6-0B, M6-0Q
  • Tesla M10-0B, M10-0Q
  • Tesla M60-0B, M60-0Q

Workaround

If you require NVENC to be enabled, use a profile that has at least 1 Gbyte of frame buffer.

VM running older NVIDIA vGPU drivers fails to initialize vGPU when booted

Description

A VM running a version of the NVIDIA guest VM drivers from a previous main release branch, for example release 4.4, will fail to initialize vGPU when booted on a Nutanix AHV platform running the current release of Virtual GPU Manager.

In this scenario, the VM boots in standard VGA mode with reduced resolution and color depth. The NVIDIA virtual GPU is present in Windows Device Manager but displays a warning sign, and the following device status:

Windows has stopped this device because it has reported problems. (Code 43)

Depending on the versions of drivers in use, the Nutanix AHV VM’s /var/log/messages log file reports one of the following errors:

  • An error message:
    vmiop_log: error: Unable to fetch Guest NVIDIA driver information
  • A version mismatch between guest and host drivers:
    vmiop_log: error: Guest VGX version(1.1) and Host VGX version(1.2) do not match
  • A signature mismatch:
    vmiop_log: error: VGPU message signature mismatch.

Resolution

Install the current NVIDIA guest VM driver in the VM.

Virtual GPU fails to start if ECC is enabled

Description

Tesla M60, Tesla M6, and GPUs based on the Pascal GPU architecture, for example Tesla P100 or Tesla P4, support error correcting code (ECC) memory for improved data integrity. Tesla M60 and M6 GPUs in graphics mode are supplied with ECC memory disabled by default, but it may subsequently be enabled using nvidia-smi. GPUs based on the Pascal GPU architecture are supplied with ECC memory enabled.

However, NVIDIA vGPU does not support ECC memory. If ECC memory is enabled, NVIDIA vGPU fails to start.

The following error is logged in the Nutanix AHV host’s /var/log/messages log file:

vmiop_log: error: Initialization: VGX not supported with ECC Enabled.

Resolution

Ensure that ECC is disabled on all GPUs.

Before you begin, ensure that NVIDIA Virtual GPU Manager is installed on your hypervisor.

  1. Use nvidia-smi to list the status of all GPUs, and check for ECC noted as enabled on GPUs.
    # nvidia-smi -q
    
    ==============NVSMI LOG==============
    
    Timestamp                           : Tue Dec 19 18:36:45 2017
    Driver Version                      : 384.99
    
    Attached GPUs                       : 1
    GPU 0000:02:00.0
    
    [...]
    
        Ecc Mode
            Current                     : Enabled
            Pending                     : Enabled
    
    [...]
  2. Change the ECC status to off on each GPU for which ECC is enabled.
    • If you want to change the ECC status to off for all GPUs on your host machine, run this command:
      # nvidia-smi -e 0
    • If you want to change the ECC status to off for a specific GPU, run this command:
      # nvidia-smi -i id -e 0

      id is the index of the GPU as reported by nvidia-smi.

      This example disables ECC for the GPU with index 0000:02:00.0.

      # nvidia-smi -i 0000:02:00.0 -e 0
  3. Reboot the host.
  4. Confirm that ECC is now disabled for the GPU.
    # nvidia-smi -q
    
    ==============NVSMI LOG==============
    
    Timestamp                           : Tue Dec 19 18:37:53 2017
    Driver Version                      : 384.99
    
    Attached GPUs                       : 1
    GPU 0000:02:00.0
    [...]
    
        Ecc Mode
            Current                     : Disabled
            Pending                     : Disabled
    
    [...]

If you later need to enable ECC on your GPUs, run one of the following commands:

  • If you want to change the ECC status to on for all GPUs on your host machine, run this command:
    # nvidia-smi -e 1
  • If you want to change the ECC status to on for a specific GPU, run this command:
    # nvidia-smi -i id -e 1

    id is the index of the GPU as reported by nvidia-smi.

    This example enables ECC for the GPU with index 0000:02:00.0.

    # nvidia-smi -i 0000:02:00.0 -e 1

After changing the ECC status to on, reboot the host.

Single vGPU benchmark scores are lower than pass-through GPU

Description

A single vGPU configured on a physical GPU produces lower benchmark scores than the physical GPU run in pass-through mode.

Aside from performance differences that may be attributed to a vGPU’s smaller frame buffer size, vGPU incorporates a performance balancing feature known as Frame Rate Limiter (FRL). On vGPUs that use the best-effort scheduler, FRL is enabled. On vGPUs that use the fixed share or equal share scheduler, FRL is disabled.

FRL is used to ensure balanced performance across multiple vGPUs that are resident on the same physical GPU. The FRL setting is designed to give good interactive remote graphics experience but may reduce scores in benchmarks that depend on measuring frame rendering rates, as compared to the same benchmarks running on a pass-through GPU.

Resolution

FRL is controlled by an internal vGPU setting. On vGPUs that use the best-effort scheduler, NVIDIA does not validate vGPU with FRL disabled, but for validation of benchmark performance, FRL can be temporarily disabled by setting the extra vGPU parameter frame_rate_limiter=0 through the ACLI when a vGPU type is assigned to a VM.

For example:

vm.gpu_assign a7f24fc0-dd05-4595-a76f-8b1901942aae gpu=Nvidia_GRID_M60-4Q extra_param=frame_rate_limiter=0

The setting takes effect the next time any VM using the given vGPU type is started.

With this setting in place, the VM’s vGPU will run without any frame rate limit.

The FRL can be reverted back to its default setting by setting the extra vGPU parameter frame_rate_limiter=1

nvidia-smi fails to operate when all GPUs are assigned to GPU pass-through mode

Description

If all GPUs in the platform are assigned to VMs in pass-through mode, nvidia-smi will return an error:

[root@vgx-test ~]# nvidia-smi
Failed to initialize NVML: Unknown Error

This is because GPUs operating in pass-through mode are not visible to nvidia-smi and the NVIDIA kernel driver operating in the Nutanix AHVhost.

Resolution

N/A

4. Resolved Issues

Issues Resolved in Release 6.0

Bug ID Summary and Description
200376678

The license expires prematurely in Linux guest VMs

In Linux guest VMs, the license expires before the default borrow period has elapsed. In normal operation, the license is renewed periodically at an interval that depends on the license borrow period. As a result, a failure to renew the license may cause the license to expire before the default borrow period has elapsed.

Issues Resolved in Release 6.1

Bug ID Summary and Description
2075467

The displays flicker each time a license is requested or renewed in Linux guest VMs

Whenever a license is requested or renewed in Linux guest VMs, the displays are reconfigured and rescanned. Rescanning the displays causes the remoting solution to momentarily drop the connection and, as a result, the displays flicker.

200391532

Issues in remote desktop sessions if a license is acquired after a session is started

A VM might acquire a license for NVIDIA vGPU software after a remote desktop session has connected to the VM. In this situation, some licensed features and capabilities are not available to a properly licensed vGPU or pass-through GPU in the session. For example, the updated maximum resolution supported is not available.

Issues Resolved in Release 6.2

Bug ID Summary and Description
2104867

Screen resolution reverts to a lower value after a VM is rebooted

When a VM is booted, the NVIDIA vGPU software graphics driver is initially unlicensed. Screen resolution is limited to a maximum of 1280×1024 until the VM requires a license for NVIDIA vGPU software.

200407382

Benign Calling load_byte_array(tra) messages are logged

In Linux guest VMs, the Calling load_byte_array(tra) messages from the nvidia-gridd daemon are logged in /var/log/syslog.

Issues Resolved in Release 6.3

Bug ID Summary and Description
2194234

The mouse cursor moves slowly when traversing the Windows 10 Start menu

When a user traverses the Windows 10 Start menu with the mouse, highlighting of items on the menu is slow and lags behind the motion of the mouse.

200346607

Licensing pop-up windows contain the text microsoft.explorer.notification

On Windows 10 Creators Update (1703), licensing pop-up windows contain the text microsoft.explorer.notification.

2187717

VMs configured with vGPU fail to power on on servers with 1 TB or more of system memory

Support for vGPU is limited to servers with less than 1 TB of system memory. On servers with 1 TB or more of system memory, VMs configured with vGPU fail to power on. However, support for GPU pass through is not affected by this limitation.

5. NVIDIA Software Security Updates

For more information about NVIDIA’s vulnerability management, visit the NVIDIA Product Security page.

NVIDIA Software Security Updates in Release 6.0

No NVIDIA software security updates are reported in this release for Nutanix AHV.

NVIDIA Software Security Updates in Release 6.1

No NVIDIA software security updates are reported in this release for Nutanix AHV.

NVIDIA Software Security Updates in Release 6.2

No NVIDIA software security updates are reported in this release for Nutanix AHV.

NVIDIA Software Security Updates in Release 6.3

No NVIDIA software security updates are reported in this release for Nutanix AHV.

6. Known Issues

Cloned VMs configured with a vGPU type different than the type in the master image fail to start

Description

Cloned VMs configured with a vGPU type different than the type in the master image fail to start.

When a Windows 10 VM is booted, the VM becomes stuck in a loop and alternately displays Getting devices ready: 50% and Preparation in progress.

Workaround

Create one master image for each vGPU type that you want to use. Do not attempt to configure a cloned VM with a vGPU type different than the type in the master image.

Status

Open

Ref. #

2285306

6.1, 6.2 Only: VMs configured with vGPU fail to power on on servers with 1 TB or more of system memory

Description

Support for vGPU is limited to servers with less than 1 TB of system memory. On servers with 1 TB or more of system memory, VMs configured with vGPU fail to power on. However, support for GPU pass through is not affected by this limitation.

This limitation applies only to systems with supported GPUs based on the Maxwell architecture: Tesla M6, Tesla M10, and Tesla M60.

Resolution

  1. Limit the amount of system memory on the server to 1 TB minus 16 GB.

  2. Reboot the server.

If the problem persists, contact your server vendor for the recommended system memory configuration with NVIDIA GPUs.

Status

Resolved in NVIDIA vGPU software release 6.3

Ref. #

2187717

Even when the scheduling policy is equal share, unequal GPU utilization is reported

Description

When the scheduling policy is equal share, unequal GPU engine utilization can be reported for the vGPUs on the same physical GPU.

For example, GPU engine usage for three P40-8Q vGPUs on a Tesla P40 GPU might be reported as follows:

[root@localhost:~] nvidia-smi vgpu
Wed Jun 27 10:33:18 2018
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 390.59                 Driver Version: 390.59                    |
|-------------------------------+--------------------------------+------------+
| GPU  Name                     | Bus-Id                         | GPU-Util   |
|      vGPU ID    Name          | VM ID    VM Name               | vGPU-Util  |
|===============================+================================+============|
|   0  Tesla P40                | 00000000:81:00.0               |  52%       |
|      2122661    GRID P40-8Q   | 2122682  centos7.4-xmpl-211... |     19%    |
|      2122663    GRID P40-8Q   | 2122692  centos7.4-xmpl-211... |      0%    |
|      2122659    GRID P40-8Q   | 2122664  centos7.4-xmpl-211... |     25%    |
+-------------------------------+--------------------------------+------------+
|   1  Tesla P40                | 00000000:85:00.0               |  58%       |
|      2122662    GRID P40-8Q   | 2122689  centos7.4-xmpl-211... |      0%    |
|      2122658    GRID P40-8Q   | 2122667  centos7.4-xmpl-211... |     59%    |
|      2122660    GRID P40-8Q   | 2122670  centos7.4-xmpl-211... |      0%    |
+-------------------------------+--------------------------------+------------+

The vGPU utilization of the vGPU 2122658 is reported as 59%. However, the expected vGPU utilization should not exceed 33%.

This behavior is a result of the mechanism that is used to measure GPU engine utilization.

Status

Open

Ref. #

2175888

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

Description

When the scheduling policy is fixed share, GPU engine utilization can be reported as higher than expected for a vGPU.

For example, GPU engine usage for six P40-4Q vGPUs on a Tesla P40 GPU might be reported as follows:

[root@localhost:~] nvidia-smi vgpu
Mon Aug 20 10:33:18 2018
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 390.42                 Driver Version: 390.42                    |
|-------------------------------+--------------------------------+------------+
| GPU  Name                     | Bus-Id                         | GPU-Util   |
|      vGPU ID    Name          | VM ID    VM Name               | vGPU-Util  |
|===============================+================================+============|
|   0  Tesla P40                | 00000000:81:00.0               |  99%       |
|      85109      GRID P40-4Q   | 85110    win7-xmpl-146048-1    |     32%    |
|      87195      GRID P40-4Q   | 87196    win7-xmpl-146048-2    |     39%    |
|      88095      GRID P40-4Q   | 88096    win7-xmpl-146048-3    |     26%    |
|      89170      GRID P40-4Q   | 89171    win7-xmpl-146048-4    |      0%    |
|      90475      GRID P40-4Q   | 90476    win7-xmpl-146048-5    |      0%    |
|      93363      GRID P40-4Q   | 93364    win7-xmpl-146048-6    |      0%    |
+-------------------------------+--------------------------------+------------+
|   1  Tesla P40                | 00000000:85:00.0               |   0%       |
+-------------------------------+--------------------------------+------------+

The vGPU utilization of vGPU 85109 is reported as 32%. For vGPU 87195, vGPU utilization is reported as 39%. And for 88095, it is reported as 26%. However, the expected vGPU utilization of any vGPU should not exceed approximately 16.7%.

This behavior is a result of the mechanism that is used to measure GPU engine utilization.

Status

Open

Ref. #

2227591

Benign warnings during Virtual GPU Manager installation or uninstallation after hypervisor upgrade

Description

If the Virtual GPU Manager is installed or uninstalled after the hypervisor is upgraded, several warning messages about missing files are displayed.

The messages are similar to the following examples:

WARNING: Can't read module /lib/modules/4.4.77-1.el6.nutanix.20170830.124.x86_64/weak-updates/ixgbevf.ko: No such file or directory
WARNING: Can't read module /lib/modules/4.4.77-1.el6.nutanix.20170830.124.x86_64/weak-updates/i40evf.ko: No such file or directory
...
egrep: /lib/modules/4.4.77-1.el6.nutanix.20170830.124.x86_64//weak-updates/ixgbevf.ko: No such file or directory
egrep: /lib/modules/4.4.77-1.el6.nutanix.20170830.124.x86_64//weak-updates/i40evf.ko: No such file or directory
...
gzip: /boot/initramfs-4.4.77-1.el6.nutanix.20170830.124.x86_64.tmp: not in gzip format
WARNING: Can't read module /lib/modules/4.4.77-1.el6.nutanix.20170830.124.x86_64/weak-updates/ixgbevf.ko: No such file or directory
WARNING: Can't read module /lib/modules/4.4.77-1.el6.nutanix.20170830.124.x86_64/weak-updates/i40evf.ko: No such file or directory
...

After a hypervisor upgrade, files that are the targets of some symbolic links no longer exist. Although these missing files cause warning messages to be displayed during the installation or uninstallation of the Virtual GPU Manager, the installation or uninstallation is completed without errors.

Workaround

Ignore these messages as they are benign.

Status

Open

Ref. #

200423757

Benign not in gzip format messages during Virtual GPU Manager installation or uninstallation

Description

During the installation or uninstallation of the Virtual GPU Manager, the warning messages are displayed:

gzip: /boot/initramfs-4.4.77-1.el6.nutanix.20170830.100726.x86_64.img: not in gzip format

gzip: /boot/initramfs-4.4.77-1.el6.nutanix.20170830.100726.x86_64.tmp: not in gzip format

Workaround

Ignore these messages as they are benign.

Status

Open

Ref. #

200405700

Since 6.1: License is not acquired in Windows VMs

Description

When a windows VM configured with a licensed vGPU is started, the VM fails to acquire a license.

Error messages in the following format are written to the NVIDIA service logs:

[000000020.860152600 sec] - [Logging.lib]   ERROR: [nvGridLicensing.FlexUtility] 353@FlexUtility::LogFneError : Error: Failed to add trusted storage. Server URL : license-server-url - 
[1,7E2,2,1[7000003F,0,9B00A7]]
 
System machine type does not match expected machine type..

Workaround

This workaround requires administrator privileges.

  1. Stop the NVIDIA Display Container LS service.
  2. Delete the contents of the folder %SystemDrive%:\Program Files\NVIDIA Corporation\Grid Licensing.
  3. Start the NVIDIA Display Container LS service.

Status

Closed

Ref. #

200407287

Since 6.1: nvidia-smi reports that vGPU migration is supported on all hypervisors

Description

The command nvidia-smi vgpu -m shows that vGPU migration is supported on all hypervisors, even hypervisors or hypervisor versions that do not support vGPU migration.

Status

Closed

Ref. #

200407230

Screen resolution reverts to a lower value after a VM is rebooted

Description

When a VM is booted, the NVIDIA vGPU software graphics driver is initially unlicensed. Screen resolution is limited to a maximum of 1280×1024 until the VM requires a license for NVIDIA vGPU software. Because the higher resolutions are not available, the OS falls back to next available resolution in its mode list (for example, 1366×768) even if the resolution for the VM had previously been set to a higher value (for example, 1920×1080). After the license has been acquired, the OS does not attempt to set the resolution to a higher value.

This behavior is the expected behavior for licensed NVIDIA vGPU software products.

Workaround

Manually set the screen resolution to the required higher value after the VM has acquired the NVIDIA vGPU software license.

Status

Resolved in NVIDIA vGPU software release 6.2.

Ref. #

2104867

6.1 Only: Benign Calling load_byte_array(tra) messages are logged

Description

In Linux guest VMs, the following messages from the nvidia-gridd daemon are logged in /var/log/syslog:

May 21 18:36:39 test-HVM-domU nvidia-gridd: Started (657)
May 21 18:36:39 test-HVM-domU nvidia-gridd: Ignore Service Provider Licensing.
May 21 18:36:39 test-HVM-domU nvidia-gridd: Calling load_byte_array(tra)
May 21 18:36:41 test-HVM-domU nvidia-gridd: Acquiring license for GRID vGPU Edition.
May 21 18:36:41 test-HVM-domU nvidia-gridd: Calling load_byte_array(tra)
May 21 18:36:43 test-HVM-domU nvidia-gridd: License acquired successfully. Server URL : http://192.0.2.117:7070/request

Workaround

Ignore these messages as they are benign.

Status

Resolved in NVIDIA vGPU software release 6.2.

Ref. #

200407382

6.0 Only: Issues in remote desktop sessions if a license is acquired after a session is started

Description

A VM might acquire a license for NVIDIA vGPU software after a remote desktop session has connected to the VM. In this situation, some licensed features and capabilities are not available to a properly licensed vGPU or pass-through GPU in the session. For example, the updated maximum resolution supported is not available.

Workaround

Before attempting this workaround, confirm that the VM has obtained the correct license for NVIDIA vGPU software.

  1. After installing the guest VM driver package and configuring required license settings on the VM (or on the master image used for VM deployment), set the IgnoreSP property to 1.

    • On Windows, add the following registry setting:

      [HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\GridLicensing] 
      "IgnoreSP"=dword:00000001
    • On Linux, add the following setting to the file /etc/nvidia/gridd.conf:

      IgnoreSP=1
  2. Restart the VM.

Status

Resolved in NVIDIA vGPU software release 6.1.

Ref. #

200391532

6.0-6.2 Only: Licensing pop-up windows contain the text microsoft.explorer.notification

Description

On Windows 10 Creators Update (1703), licensing pop-up windows contain the text microsoft.explorer.notification.

Version

Windows 10 Creators Update (1703)

Status

Resolved in NVIDIA vGPU software release 6.3

Ref. #

200346607

Multiple display heads are not detected by Ubuntu 14.04 guest VMs

Description

After an Ubuntu 14.04 guest VM has acquired a license, multiple display heads connected to the VM are not detected.

Version

Ubuntu 14.04

Workaround

To see all the connected display heads after the VM has acquired a license, open the Displays settings window and click Detect displays.

Status

Open

Ref. #

200334648

On GPUs based on the Pascal architecture, Ubuntu 16.04 VMs run slowly after acquiring a license

Description

On GPUs based on the Pascal architecture, Ubuntu VMs to which an NVIDIA vGPU or pass-through GPU is assigned run slowly after acquiring a license. Ubuntu VMs that have not been assigned an NVIDIA vGPUor pass-through GPU run noticeably faster.

Workaround

After the VM has acquired a license, restart the lightdm service.

Status

Open.

Ref. #

200359618

Resolution is not updated after a VM acquires a license and is restarted

Description

In a Red Enterprise Linux 7.3 guest VM, an increase in resolution from 1024×768 to 2560×1600 is not applied after a license is acquired and the gridd service is restarted. This issue occurs if the multimonitor parameter is added to the xorg.conf file.

Version

Red Enterprise Linux 7.3

Status

Open

Ref. #

200275925

A segmentation fault in DBus code causes nvidia-gridd 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

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.
  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.

    # sudo service nvidia-gridd start

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

Status

Open

The nvidia-gridd service fails because the required configuration is not provided

Description

The nvidia-gridd service exits with an error because the required configuration is not provided.

The known issue described in A segmentation fault in DBus code causes nvidia-gridd to exit on Red Hat Enterprise Linux and CentOS causes the NVIDIA X Server Settings page for managing licensing settings through a GUI to be disabled by default. As a result, if the required license configuration is not provided through the configuration file, the service exits with an error.

Details of the error can be obtained by checking the status of the nvidia-gridd service.

# service nvidia-gridd status
nvidia-gridd.service - NVIDIA Grid Daemon
Loaded: loaded (/usr/lib/systemd/system/nvidia-gridd.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Wed 2017-11-01 19:25:07 IST; 27s ago
  Process: 11990 ExecStopPost=/bin/rm -rf /var/run/nvidia-gridd (code=exited, status=0/SUCCESS)
  Process: 11905 ExecStart=/usr/bin/nvidia-gridd (code=exited, status=0/SUCCESS)
Main PID: 11906 (code=exited, status=1/FAILURE)
Nov 01 19:24:35 localhost.localdomain systemd[1]: Starting NVIDIA Grid Daemon...
Nov 01 19:24:35 localhost.localdomain nvidia-gridd[11906]: Started (11906)
Nov 01 19:24:35 localhost.localdomain systemd[1]: Started NVIDIA Grid Daemon.
Nov 01 19:24:36 localhost.localdomain nvidia-gridd[11906]:  Failed to open config file : /etc/nvidia/gridd.conf error :No such file or directory
Nov 01 19:25:07 localhost.localdomain nvidia-gridd[11906]: Service provider detection complete.
Nov 01 19:25:07 localhost.localdomain nvidia-gridd[11906]: Shutdown (11906)
Nov 01 19:25:07 localhost.localdomain systemd[1]: nvidia-gridd.service: main process exited, code=exited, status=1/FAILURE
Nov 01 19:25:07 localhost.localdomain systemd[1]: Unit nvidia-gridd.service entered failed state.
Nov 01 19:25:07 localhost.localdomain systemd[1]: nvidia-gridd.service failed.

Workaround

Use a configuration file to license NVIDIA vGPU software on Linux as explained in Virtual GPU Client Licensing User Guide.

Status

Open

Ref. #

200359469

The Apply button is disabled after change to unlicensed mode

Description

After the mode is changed from licensed Quadro Virtual Datacenter Workstation Edition mode to Unlicensed Tesla mode, the Apply button on the Manage GRID License page is disabled. As a result, NVIDIA X Server Settings cannot be used to switch to Tesla (Unlicensed) mode on a licensed system.

Workaround

  1. Start NVIDIA X Server Settings by using the method for launching applications provided by your Linux distribution.
  2. In the NVIDIA X Server Settings window that opens, click Manage GRID License.
  3. Clear the Primary Server field.
  4. Select the Tesla (unlicensed) option.
  5. Click Apply.

Status

Open

Ref. #

200359624

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

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

Description

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

This issue typically occurs in the following situations:

  • Full screen 1080p video content is playing in a browser. In this situation, the session hangs and session reconnection fails.
  • Multiple display heads are used with Citrix XenDesktop or VMware Horizon on a Windows 10 guest VM.
  • Higher resolution monitors are used.
  • Applications that are frame-buffer intensive are used.
  • NVENC is in use.

To reduce the possibility of memory exhaustion, NVENC is disabled on profiles that have 512 Mbytes or less of frame buffer.

The following vGPU profiles have 512 Mbytes or less of frame buffer:

  • Tesla M6-0B, M6-0Q
  • Tesla M10-0B, M10-0Q
  • Tesla M60-0B, M60-0Q

The root cause is a known issue associated with changes to the way that recent Microsoft operating systems handle and allow access to overprovisioning messages and errors. If your systems are provisioned with enough frame buffer to support your use cases, you should not encounter these issues.

Workaround

  • Use an appropriately sized vGPU to ensure that the frame buffer supplied to a VM through the vGPU is adequate for your workloads.
  • Monitor your frame buffer usage.
  • If you are using Windows 10, consider these workarounds and solutions:

Status

Open

Ref. #

  • 200130864
  • 1803861

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

Description

GDM fails to start on Red Hat Enterprise Linux 7.2 and CentOS 7.0 with the following error:

Oh no! Something has gone wrong!

Workaround

Permanently enable permissive mode for Security Enhanced Linux (SELinux).

  1. As root, edit the /etc/selinux/config file to set SELINUX to permissive.
    SELINUX=permissive
  2. Reboot the system.
    ~]# reboot

For more information, see Permissive Mode in Red Hat Enterprise Linux 7 SELinux User's and Administrator's Guide.

Status

Not an NVIDIA bug

Ref. #

200167868

Multiple WebGL tabs in Microsoft Internet Explorer may trigger TDR on Windows VMs

Description

Running intensive WebGL applications in multiple IE tabs may trigger a TDR on Windows VMs.

Workaround

Disable hardware acceleration in IE.

To enable software rendering in IE, refer to the Microsoft knowledge base article How to enable or disable software rendering in Internet Explorer.

Status

Open

Ref. #

200148377

Notices

Notice

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.

Information furnished is believed to be accurate and reliable. However, NVIDIA Corporation assumes no responsibility for the consequences of use of such information or for any infringement of patents or other rights of third parties that may result from its use. No license is granted by implication of otherwise under any patent rights of NVIDIA Corporation. Specifications mentioned in this publication are subject to change without notice. This publication supersedes and replaces all other information previously supplied. NVIDIA Corporation products are not authorized as critical components in life support devices or systems without express written approval of NVIDIA Corporation.

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, vGPU, Pascal, 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.