Known Issues and Resolved issues: Release Notes GRID VGPU FOR VMWARE VSPHERE - Version 361.40 / 362.13 - April 4th, 2016

Answer ID 4129
Published 05/17/2016 08:23 AM
Updated 08/09/2016 09:15 AM

Known Issues and Resolved issues: Release Notes GRID VGPU FOR VMWARE VSPHERE - Version 361.40 / 362.13 - April 4th, 2016

Customers are strongly advised to read the full release notes included in the download for each version of GRID vGPU they install. Additionally customers are advised to familiarize themselves with the release notes of later versions so they are aware of known and resolved issues in the event they encounter them.

This article draws highlights the known and resolved issues associated with the release notes for GRID VGPU FOR VMWARE VSPHERE - Version 361.40 / 362.13; released on April 4th, 2016.

RESOLVED ISSUES

GRID vGPU for VMware vSphere Version 361.40 / 362.13 RN-07347-001| 9

 

Issues resolved by this release, which could be seen in earlier releases. Customers who suspect they are encountering any of these issues and using earlier releases, are advised to upgrade to this release where possible.

 

Bug ID: 200172195

Summary and Description: PowerPoint intermittently crashes in slideshow mode on  XenDesktop in a dual-monitor setup. Running the PowerPoint application in slideshow mode over a XenDesktop session in a dual-monitor setup sometimes causes the application to crash.

 

Bug ID: 200155765

CATIA intermittently crashes during quick object rotation. Using the mouse to quickly rotate large models in the CATIA application sometimes causes the application to crash

 

Bug ID: 1717876

Loading large models in CATIA causes an OpenGL failure. Loading very large models in CATIA exhausts the frame buffer, causing Open GL to fail with the error OPENGL 8.

 

Bug ID: 1720471

Black screen on initial connection to a VM using XenDesktop from a client with multiple displays. The initial connection to a VM that uses XenDesktop from a client with multiple displays results in a black screen. Disconnecting and reconnecting to the VM resolves the issue.

 

Bug ID: 1710641

Intermittent BSODs on vGPU VMs that are running on a heavily-loaded server vGPU VMs that are running on a heavily loaded server and are accessed through Horizon intermittently bugcheck with error code 0x50.This error occurs because the kernel driver is trying to access an invalid memory location

 

Bug ID: 1718648

OpenGL applications hang on Linux VMs. OpenGL applications hang after sometime when running on Linux VMs with vGPU.

 

Known Issues

GRID vGPU for VMware vSphere Version 361.40 / 362.13 RN-07347-001| 9

 

Driver upgrade from 352.83 to 361.40 fails on baremetal

Description:  Driver upgrade fails on a bare metal setup with this error message:

An NVIDIA kernel module 'nvidia' appears to already

be loaded in your kernel. This may be because it is

in use .....

The upgrade fails because it does not stop the nvidia-gridd service.

 

Workaround: Stop the nvidia-griddservice before upgrading the driver.

Status: Open

Ref. #200184005

 

 

4096x2160 resolution is not available in Windows Control Panel

Description: 4096x2160 resolution cannot be applied through NVIDIA Control Panel and is not listed in Windows Control Panel.

Workaround: Clear the “Hide all unsupported modes” checkbox in Windows Control Panel.

Status: Open

Ref. #200182826

 

 

NVIDIA Control Panel is killed during reconnection with a View Session

Description:  If NVIDIA Control Panel is running while a View session is disconnected and then reconnected, NVIDIA Control Panel is killed before the View session is reconnected.

Status: Open

Ref. #200176969

 

 

GNOME Display Manager (GDM) fails to start on Red Hat Enterprise Linux (RHEL) 7.2

Description:  GDM fails to start on Red Hat Enterprise Linux 7.2.

Workaround: Enable permissive mode for Security Enhanced Linux (SELinux)

Status:  Not an NVIDIA bug

Ref. #200167868

 

NVIDIA Control Panel complains that “you are not currently using a display that is attached to an Nvidia GPU”

Description: When you launch NVIDIA Control Panel on a VM configured with vGPU, it fails to start and complains about not using a display attached to an NVIDIA GPU. This usually happens because Windows is using VMware’s SVGA device instead of NVIDIA vGPU.

 

Fix: Make NVIDIA vGPU the primary display adapter. Use Windows screen resolution control panel to make the second display, identified as “2” and corresponding to NVIDIA vGPU, to be the active display and:

1.     Select the  Show desktop only on 2 option

2.     Click Apply to accept the configuration.

3.     You may need to click on the Detect button for Windows to recognize the display connected to NVIDIA vGPU.

 

Note: If the VMware Horizon/View agent is installed in the VM, the NVIDIA GPU is automatically selected in preference to the SVGA device.

Status:  Open

 

VM configured with more than one vGPU fails to initialize vGPU when booted

Description: Using the current VMware vCenter user interface, it is possible to configure a VM with more than one vGPU device. When booted, the VM boots in VMware SVGA mode and doesn’t load the NVIDIA driver. The additional vGPU devices are present in Windows Device Manager but display a warning sign, and a device status of “Windows has stopped this device because it has reported problems. (Code 43)”.

Workaround:  GRID vGPU currently supports a single virtual GPU device per VM.  Remove any additional vGPUs from the VM configuration before booting the VM.

Status:  Open

 

 

A VM configured with both a vGPU and a passthrough GPU fails to start the passthrough GPU

Description:  Using the current VMware vCenter user interface, it is possible to configure a VM with a vGPU device and a passthrough (direct path, vDGA) GPU device. This is not a currently supported configuration for vGPU. The passthrough GPU appears in Windows Device Manager with a warning sign, and a device status of “Windows has stopped this device because it has reported problems. (Code 43)”.

Workaround: Do not assign vGPU and passthrough GPUs to a VM simultaneously.

Status: Open

Ref. #1735002

 

 

vGPU allocation policy fails when multiple VMs are started simultaneously

Description: If multiple VMs are started simultaneously, vSphere may not adhere to the placement policy currently in effect. For example, if the default placement policy (breadth-first) is in effect, and 4 physical GPUs are available with no resident vGPUs, then starting 4 VMs simultaneously should result in one vGPU on each GPU. In practice, more than one vGPU may end up resident on a GPU.

Workaround:  Start VMs individually.

Status: Not an NVIDIA bug

Ref. #200042690

 

 

Prior to installing Horizon agent inside a VM, the Start menu’s sleep option is available.

Description:  When a VM is configured with a vGPU, the Sleep option remains available in the Windows Start menu. Sleep is not supported on vGPU and attempts to use it will lead to undefined behavior.

Workaround:  Do not use Sleep with vGPU. Installing the VMware Horizon agent will disable the Sleep option.

Status: Closed

Ref. #200043405

 

vGPU-enabled VMs fail to start, nvidia-smi fails when VMs are configured with too high a proportion of the server’s memory.

Description: If vGPU-enabled VMs are assigned too high a proportion of the server’s total memory, one of more of the VMs may fail to start with the error “The available Memory resources in the parent resource pool are insufficient for the operation”, and nvidia-smi run in the host shell returns this error:

-sh: can't fork

For example, on a server configured with 256G of memory, these errors may occur if vGPU-enabled VMs are assigned more than 243G of memory.

Workaround: Reduce the total amount of system memory assigned to the VMs.

Status: Closed

Ref. #200060499

 

 

On reset/restart VMs fail to start with the error “VMIOP: no graphics device is available for vGPU...”

Description: On a system running a maximal configuration, i.e. maximum number of vGPU VMs the server can support, some VMs might fail to start post a reset or restart operation.

 

Fix: Upgrade to ESXi 6.0 Update 1 or higher

Status: Closed

Ref. #200097546

 

 

nvidia-smi shows high GPU utilization for vGPU VMs with active Horizon sessions

Description: vGPU VMs with an active Horizon connection utilize a high percentage of the GPU on the ESXi host. The GPU utilization remains high for the duration of the Horizon session even if there are no active applications running on the VM.

Workaround:  None

Status:  Open

Ref. #1735009

 

 

MPlayer, or other video players, fail to start when using hardware acceleration on Linux VMs running vGPU

Description: VDPAU is currently not supported on Linux VMs running vGPU.

Workaround: Configure the video player to not use VDPAU or hardware acceleration.

Status: Open

Ref. #200144667

 

Horizon does not scale over multiple monitors when connecting to Ubuntu VMs

Description: Horizon when connecting to an Ubuntu VM in full screen mode fails to scale over multiple monitors.

Workaround:  Restart lightdmservice. Use the following command on Linux console to restart Lightdm service:

$ service lightdm restart

Status: Open

Ref. #200138540

 

Multiple WebGL tabs in Microsoft Internet Explorer may trigger TDR (Timeout Detection and Recovery) 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 Microsoft’s knowledge base article at: https://support.microsoft.com/en-us/kb/2528233

Status:  Open

Ref. #20014837

 

 

Users without support who suspect they are experiencing any of these issues can discuss their issues on the NVIDIA community forums at: https://gridforums.nvidia.com.  

 

Relevant Products

NVIDIA vGPU for VMware vSphere/ESXi

GRID vGPU cards including K1, K2, M6, M60, etc

Was this answer helpful?
Your rating has been submitted, please tell us how we can make this answer more useful.

LIVE CHAT

Chat online with one of our support agents

CHAT NOW

ASK US A QUESTION

Contact Support for assistance

CONTACT US