1. Release Notes

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

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

Software 5.0 5.1
NVIDIA Virtual GPU Manager for the Nutanix AHV releases listed in Hypervisor Software Versions Not supported 384.99
NVIDIA Windows driver Not supported 385.90
NVIDIA Linux driver version Not supported 384.99

Updates in Release 5.1

  • Support for Nutanix AHV release 5.5
  • Miscellaneous bug fixes

2. Validated Platforms

This release of NVIDIA virtual GPU software provides support for several NVIDIA GPUs on validated server hardware platforms, Nutanix AHV hypervisor software versions, and guest operating systems.

Supported NVIDIA GPUs and Validated Server Platforms

This release of NVIDIA virtual GPU 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 virtual GPU software releases.

Hypervisor Software Versions

This release has been tested with the following hypervisor software versions:

Software Version Tested
Nutanix AHV 5.5 RTM

Guest OS Support

NVIDIA virtual GPU 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 virtual GPU software with your virtualization software. To be listed as supported, a guest OS release must be supported not only by NVIDIA virtual GPU 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 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 virtual GPU software supports the following Windows releases as a guest OS on Nutanix AHV:

Guest OS NVIDIA vGPU Pass-Through GPU
Windows Server 2016 5.5 RTM 5.5 RTM
Windows Server 2012 R2 5.5 RTM 5.5 RTM
Windows Server 2008 R2 5.5 RTM 5.5 RTM
Windows 10 RS2 (64-bit) 5.5 RTM 5.5 RTM
Windows 10 RS2 (32-bit) 5.5 RTM 5.5 RTM
Windows 8.1 Update (64-bit) 5.5 RTM 5.5 RTM
Windows 8.1 Update (32-bit) 5.5 RTM 5.5 RTM
Windows 8.1 (64-bit) 5.5 RTM 5.5 RTM
Windows 8.1 (32-bit) 5.5 RTM 5.5 RTM
Windows 8 (32/64-bit) 5.5 RTM 5.5 RTM
Windows 7 (32/64-bit) 5.5 RTM 5.5 RTM

Linux Guest OS Support

NVIDIA virtual GPU software supports the following Linux distributions as a guest OS on Nutanix AHV:

Guest OS NVIDIA vGPU Pass-Through GPU
Red Hat Enterprise Linux 7.0-7.3 5.5 RTM 5.5 RTM
CentOS 7.0-7.3 5.5 RTM 5.5 RTM
Ubuntu 16.04 LTS 5.5 RTM 5.5 RTM
Ubuntu 14.04 LTS 5.5 RTM 5.5 RTM

3. Known Product Limitations

Known product limitations for this release of NVIDIA virtual GPU 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 VM’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.

  1. Use nvidia-smi to list the status of all GPUs, and check for ECC noted as enabled on GPUs.
  2. Change the ECC status to off on each GPU for which ECC is enabled by executing the following command:
    nvidia-smi -i id -e 0

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

  3. Reboot the host.

Single vGPU benchmark scores are lower than passthrough GPU

Description

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

Aside from performance differences that may be attributed to a vGPU’s smaller framebuffer size, vGPU incorporates a performance balancing feature known as Frame Rate Limiter (FRL), which is enabled on all vGPUs. 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 passthrough GPU.

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

Description

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

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

This is because GPUs operating in passthrough mode are not visible to nvidia-smi and the NVIDIA kernel driver operating in the Nutanix AHV dom0.

Resolution

N/A

VMs configured with large memory fail to initialize vGPU when booted

Description

When starting multiple VMs configured with large amounts of RAM (typically more than 32GB per VM), a VM may fail to initialize vGPU. In this scenario, the VM boots in standard VGA mode with reduced resolution and color depth. The NVIDIA virtual GPU software 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)

The Nutanix AHV VM’s /var/log/messages log file contains these error messages:

vmiop_log: error: NVOS status 0x29
vmiop_log: error: Assertion Failed at 0x7620fd4b:179
vmiop_log: error: 8 frames returned by backtrace
...
vmiop_log: error: VGPU message 12 failed, result code: 0x29
...
vmiop_log: error: NVOS status 0x8
vmiop_log: error: Assertion Failed at 0x7620c8df:280
vmiop_log: error: 8 frames returned by backtrace
...
vmiop_log: error: VGPU message 26 failed, result code: 0x8

Resolved Issues

Issues Resolved in Release 5.1

No resolved issues are reported in this release for Nutanix AHV.

5. Known Issues

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

Since 5.1: 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.

Since 5.1: The GUI for licensing is disabled by default.

Version

Red Hat Enterprise Linux 6.8 and 6.9

CentOS 6.8 and 6.9

NVIDIA virtual GPU software 5.0

5.0 Only: Workaround

This workaround requires sudo privileges.

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

  2. Start the nvidia-gridd service.

    # sudo service nvidia-gridd start
  3. Confirm that the nvidia-gridd service has obtained a license by examining the log messages written to /var/log/messages.

    # sudo grep gridd /var/log/messages
    …
    Aug 5 15:40:06 localhost nvidia-gridd: Started (4293)
    Aug 5 15:40:24 localhost nvidia-gridd: License acquired successfully.

Status

Open

Ref. #

  • 200358191
  • 200319854
  • 1895945

Since 5.1: 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 virtual GPU software on Linux as explained in Virtual GPU Client Licensing User Guide.

Status

Open

Ref. #

200359469

Since 5.1: 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 virtual GPU 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.