Transcription

GRID VGPU FOR CITRIX XENSERVERVERSION 367.106/370.12RN-06927-001 v4.3 (GRID) June 2017Release Notes

TABLE OF CONTENTSChapter 1. Release Notes. 1Chapter 2. Validated Platforms.22.1. Supported NVIDIA GPUs and Validated Server Platforms. 22.2. Hypervisor Software Versions. 22.3. Guest OS Support. 32.3.1. Windows Guest OS Support. 32.3.2. Linux Guest OS Support. 3Chapter 3. Known Product Limitations. 53.1. vGPU profiles with 512 Mbytes or less of frame buffer support only 1 virtual display headon Windows 10. 53.2. NVENC requires at least 1 Gbyte of frame buffer. 63.3. VM running older NVIDIA vGPU drivers fails to initialize vGPU when booted.63.4. Virtual GPU fails to start if ECC is enabled. 73.5. Single vGPU benchmark scores are lower than passthrough GPU. 83.6. Virtual GPU fails to start when GPUs are mapped above 4G.93.7. nvidia-smi fails to operate when all GPUs are assigned to GPU passthrough mode. 103.8. GRID K1 and GRID K2 cards do not support monitoring of vGPU engine usage. 113.9. Windows Aero is disabled on XenDesktop session using 3 or 4 monitors in 2560 1600resolution. 113.10. VMs configured with large memory fail to initialize vGPU when booted.113.11. vGPU host driver RPM upgrade fails. 12Chapter 4. Resolved Issues. 14Chapter 5. Known Issues. 155.1. Memory exhaustion can occur with vGPU profiles that have 512 Mbytes or less of framebuffer. 155.2. VM bug checks after the guest VM driver for Windows 10 RS2 is installed. 165.3. On XenServer 7.0, VMs unexpectedly reboot and XenServer crashes or freezes. 175.4. With no NVIDIA driver installed, XenServer misidentifies Tesla M10 cards. 185.5. GNOME Display Manager (GDM) fails to start on Red Hat Enterprise Linux 7.2 and CentOS7.0.185.6. Video goes blank when run in loop in Windows Media Player.195.7. Local VGA console is momentarily unblanked when XenDesktop changes resolution of theVM desktop. 205.8. VM bugchecks on shutdown/restart when XenDesktop is installed and NVIDIA driver isuninstalled or upgraded. 205.9. Application frame rate may drop when running XenDesktop at 2560 1600 resolution. 215.10. Windows VM BSOD. 215.11. Windows VM BSOD when upgrading NVIDIA drivers over a XenDesktop session.225.12. XenCenter does not allow vGPUs to be selected as a GPU type for Linux VMs.23www.nvidia.comGRID vGPU for Citrix XenServer Version367.106/370.12RN-06927-001 v4.3 (GRID) ii

5.13. If X server is killed on a RHEL7 VM running vGPU, XenCenter console may notautomatically switch to text console. 235.14. Multiple WebGL tabs in Microsoft Internet Explorer may trigger TDR on Windows VMs. 245.15. XenDesktop shows only a black screen when connected to a vGPU VM. 24www.nvidia.comGRID vGPU for Citrix XenServer Version367.106/370.12RN-06927-001 v4.3 (GRID) iii

www.nvidia.comGRID vGPU for Citrix XenServer Version367.106/370.12RN-06927-001 v4.3 (GRID) iv

Chapter 1.RELEASE NOTESThese Release Notes summarize current status, information on validated platforms, andknown issues with NVIDIA GRID vGPU software and hardware on Citrix XenServer.This release includes the following software:‣‣‣NVIDIA GRID Virtual GPU Manager version 367.106 for the Citrix XenServerreleases listed in Hypervisor Software VersionsNVIDIA Windows drivers for vGPU version 370.12NVIDIA Linux drivers for vGPU version 367.106CautionIf you install the wrong package for the version of Citrix XenServer you are using, GRIDvGPU Manager will fail to load.The GRID vGPU Manager and Windows guest VM drivers must be installed together.Older VM drivers will not function correctly with this release of GRID vGPU Manager.Similarly, older GRID vGPU Managers will not function correctly with this release ofWindows guest drivers. See VM running older NVIDIA vGPU drivers fails to initializevGPU when booted.Updates in this release:‣‣Miscellaneous bug fixesSupport for Citrix XenServer 7.2 on Tesla M6, M10, and M60 GPUswww.nvidia.comGRID vGPU for Citrix XenServer Version367.106/370.12RN-06927-001 v4.3 (GRID) 1

Chapter 2.VALIDATED PLATFORMSThis release of virtual GPU provides support for several NVIDIA GPUs on validatedserver hardware platforms, Citrix XenServer hypervisor software versions, and guestoperating systems.2.1. Supported NVIDIA GPUs and Validated ServerPlatformsThis release of virtual GPU provides support for the following NVIDIA GPUs on CitrixXenServer, running on validated server hardware platforms:‣‣‣‣‣GRID K1GRID K2Tesla M6Tesla M10Tesla M60For a list of validated server platforms, refer to NVIDIA GRID Certified Servers.Tesla M60 and M6 GPUs support compute mode and graphics mode. GRID vGPUrequires GPUs that support both modes to operate in graphics mode.Recent Tesla M60 GPUs and M6 GPUs are supplied in graphics mode. However, yourGPU might be in compute mode if it is an older Tesla M60 GPU or M6 GPU, or if itsmode has previously been changed.To configure the mode of Tesla M60 and M6 GPUs, use the gpumodeswitch toolprovided with GRID software releases.2.2. Hypervisor Software VersionsThis release has been tested with the following hypervisor software versions:www.nvidia.comGRID vGPU for Citrix XenServer Version367.106/370.12RN-06927-001 v4.3 (GRID) 2

Validated PlatformsSoftwareVersion testedCitrix XenServer 7.2RTM build is supported only on Tesla M6, M10 and M60 GPUs.Citrix XenServer 7.2 is not supported on GRID K1 andGRID K2 GPUs with any release of NVIDIA GRID Software.Citrix XenServer 7.1RTM build is supported.Citrix XenServer 7.0RTM build 125380 is supported.Citrix XenServer 6.5Version 6.5 with XS65ESP1. The GRID vGPU Manager included in thisrelease will not install without XenServer 6.5 SP1.Citrix XenDesktopVersion 7.6, 7.8, and 7.11 in HDX 3D Pro mode.2.3. Guest OS SupportGRID vGPU supports several Windows releases and Linux distributions as a guest OS.Use only a guest OS release that is listed as supported by GRID vGPU with yourvirtualization software. To be listed as supported, a guest OS release must besupported not only by GRID vGPU, but also by your virtualization software. NVIDIAcannot support guest OS releases that your virtualization software does not support.2.3.1. Windows Guest OS SupportGRID vGPU supports the following Windows releases as a guest OS on CitrixXenServer:‣‣‣‣‣‣‣Windows 7 (32/64-bit)Windows 8 (32/64-bit)Windows 8.1 (32/64-bit)Windows 10 (32/64-bit)Windows Server 2008 R2Windows Server 2012 R2Windows Server 20162.3.2. Linux Guest OS SupportGRID vGPU supports the following Linux distributions as a guest OS only on supportedTesla GPUs on Citrix XenServer:‣‣‣Red Hat Enterprise Linux 7.0-7.3CentOS 7.0-7.3Ubuntu 16.04 LTSwww.nvidia.comGRID vGPU for Citrix XenServer Version367.106/370.12RN-06927-001 v4.3 (GRID) 3

Validated Platforms‣Ubuntu 14.04 LTSGRID K1 and GRID K2 do not support vGPU on a Linux guest OS.www.nvidia.comGRID vGPU for Citrix XenServer Version367.106/370.12RN-06927-001 v4.3 (GRID) 4

Chapter 3.KNOWN PRODUCT LIMITATIONSKnown product limitations for this release of NVIDIA GRID are described in thefollowing sections.3.1. vGPU profiles with 512 Mbytes or less offrame buffer support only 1 virtual display headon Windows 10DescriptionTo reduce the possibility of memory exhaustion, vGPU profiles with 512 Mbytes or lessof 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-0QTesla M10-0B, M10-0QTesla M60-0B, M60-0QGRID K100, K120QGRID K200, K220QWorkaroundUse a profile that supports more than 1 virtual display head and has at least 1 Gbyte offrame buffer.www.nvidia.comGRID vGPU for Citrix XenServer Version367.106/370.12RN-06927-001 v4.3 (GRID) 5

Known Product Limitations3.2. NVENC requires at least 1 Gbyte of framebufferDescriptionUsing the frame buffer for the NVIDIA hardware-based H.264/HEVC video encoder(NVENC) may cause memory exhaustion with vGPU profiles that have 512 Mbytesor less of frame buffer. To reduce the possibility of memory exhaustion, NVENC isdisabled on profiles that have 512 Mbytes or less of frame buffer. Application GPUacceleration remains fully supported and available for all profiles, including profileswith 512 MBytes or less of frame buffer. NVENC support from both Citrix and VMwareis a recent feature and, if you are using an older version, you should experience nochange in functionality.The following vGPU profiles have 512 Mbytes or less of frame buffer:‣‣‣‣‣Tesla M6-0B, M6-0QTesla M10-0B, M10-0QTesla M60-0B, M60-0QGRID K100, K120QGRID K200, K220QWorkaroundIf you require NVENC to be enabled, use a profile that has at least 1 Gbyte of framebuffer.3.3. VM running older NVIDIA vGPU drivers fails toinitialize vGPU when bootedDescriptionA VM running older NVIDIA drivers, such as those from a previous vGPU release, willfail to initialize vGPU when booted on a Citrix XenServer platform running the currentrelease of GRID Virtual GPU Manager.In this scenario, the VM boots in standard VGA mode with reduced resolution and colordepth. The NVIDIA GRID GPU is present in Windows Device Manager but displays awarning sign, and the following device status:Windows has stopped this device because it has reported problems. (Code 43)www.nvidia.comGRID vGPU for Citrix XenServer Version367.106/370.12RN-06927-001 v4.3 (GRID) 6

Known Product LimitationsDepending on the versions of drivers in use, the Citrix XenServer 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 informationA version mismatch between guest and host drivers:vmiop log: error: Guest VGX version(1.1) and Host VGX version(1.2) do notmatchA signature mismatch:vmiop log: error: VGPU message signature mismatch.ResolutionInstall the latest NVIDIA vGPU release drivers in the VM.3.4. Virtual GPU fails to start if ECC is enabledDescriptionGRID K2, Tesla M60, and Tesla M6 support error correcting code (ECC) for improveddata integrity. If ECC is enabled, virtual GPU fails to start. The following error is loggedin the Citrix XenServer VM’s /var/log/messages log file:vmiop log: error: Initialization: VGX not supported with ECC Enabled.Virtual GPU is not currently supported with ECC active. GRID K2 cards and TeslaM60, M6 cards in graphics mode ship with ECC disabled by default, but ECC maysubsequently be enabled using nvidia-smi.ResolutionEnsure that ECC is disabled on all GPUs.Use nvidia-smi to list the status of all GPUs, and check for ECC noted as enabledon GPUs.2. Change the ECC status to off on each GPU for which ECC is enabled by executingthe following command:1.nvidia-smi -i id -e 0id is the index of the GPU as reported by nvidia-smi.www.nvidia.comGRID vGPU for Citrix XenServer Version367.106/370.12RN-06927-001 v4.3 (GRID) 7

Known Product Limitations3.5. Single vGPU benchmark scores are lower thanpassthrough GPUDescriptionA single vGPU configured on a physical GPU produces lower benchmark scores thanthe physical GPU run in passthrough mode.Aside from performance differences that may be attributed to a vGPU’s smallerframebuffer size, vGPU incorporates a performance balancing feature known as FrameRate Limiter (FRL), which is enabled on all vGPUs. FRL is used to ensure balancedperformance across multiple vGPUs that are resident on the same physical GPU. TheFRL setting is designed to give good interactive remote graphics experience but mayreduce scores in benchmarks that depend on measuring frame rendering rates, ascompared to the same benchmarks running on a passthrough GPU.ResolutionFRL is controlled by an internal vGPU setting. NVIDIA does not validate vGPUwith FRL disabled, but for validation of benchmark performance, FRL can betemporarily disabled by specifying frame rate limiter 0 in the VM’splatform:vgpu extra args parameter:[[email protected] ]# xe vm-param-set uuid e71afda4-53f4-3a1b-6c92-a364a7f619c2platform:vgpu extra args "frame rate limiter 0"[[email protected] ]#The setting takes effect the next time the VM is started or rebooted.With this setting in place, the VM’s vGPU will run without any frame rate limit. The FRLcan be reverted back to its default setting in one of the following ways:‣‣‣Removing the vgpu extra args key from the platform parameterRemoving frame rate limiter 0 from the vgpu extra args keySetting frame rate limiter 1. For example:[[email protected] ]# xe vm-param-set uuid e71afda4-53f4-3a1b-6c92a364a7f619c2 platform:vgpu extra args "frame rate limiter 1"[[email protected] ]#www.nvidia.comGRID vGPU for Citrix XenServer Version367.106/370.12RN-06927-001 v4.3 (GRID) 8

Known Product Limitations3.6. Virtual GPU fails to start when GPUs aremapped above 4GVersionXenServer 6.2StatusFixed in XenServer 6.5DescriptionGRID vGPU on Citrix XenServer 6.2 does not support operation with GPUs mappedabove the 4 gigabyte (4G) boundary in the system’s physical address space.If GPUs are mapped above 4G, the GRID vGPU Manager rpm will warn at the time ofinstallation:Warning: vGPU does not support GPUs mapped in 64-bit address space. Pleasedisable 64-bit MMIO from the system's BIOS. Refer to vGPU release notes fordetails.Also, the NVIDIA kernel driver will fail to load in XenServer’s dom0, so the nvidiamodule won’t appear in the module listing produced by lsmod. Additionally, thefollowing warning messages will be present in the output of dmesg:NVRM:NVRM:NVRM:NVRM:NVRM:NVRM:This PCI I/O region assigned to your NVIDIA device is invalid:BAR1 is 128M @ 0xf800000000000000 (PCI:03ff:00:07.0)This is a 64-bit BAR mapped above 4GB by the systemBIOS or the Linux kernel. The NVIDIA Linux/x86graphics driver and other system software componentsdo not support this configuration.ResolutionEnsure that GPUs are mapped below the 4G boundary by disabling your server’s SBIOSoption that controls 64-bit memory-mapped I/O support. This option may be labeledEnable4G Decode or Enable 64-bit MMIO.www.nvidia.comGRID vGPU for Citrix XenServer Version367.106/370.12RN-06927-001 v4.3 (GRID) 9

Known Product Limitations3.7. nvidia-smi fails to operate when all GPUsare assigned to GPU passthrough modeDescriptionIf all GPUs in the platform are assigned to VMs in passthrough mode, nvidia-smi willreturn an error:[[email protected] ]# nvidia-smiFailed to initialize NVML: Unknown ErrorThis is because GPUs operating in passthrough mode are not visible to nvidia-smiand the NVIDIA kernel driver operating in the Citrix XenServer dom0.To confirm that all GPUs are operating in passthrough, use XenCenter’s GPU tab toreview current GPU assignment:www.nvidia.comGRID vGPU for Citrix XenServer Version367.106/370.12RN-06927-001 v4.3 (GRID) 10

Known Product LimitationsResolutionN/A3.8. GRID K1 and GRID K2 cards do not supportmonitoring of vGPU engine usageDescriptionGRID K1 and GRID K2 cards do not support monitoring of vGPU engine usage. Alltools and APIs for any vGPU running on GRID K1 or GRID K2 cards report 0 for thefollowing usage statistics:‣‣‣‣3D/ComputeMemory controller bandwidthVideo encoderVideo decoder3.9. Windows Aero is disabled on XenDesktopsession using 3 or 4 monitors in 2560 1600resolutionDescriptionWindows Aero may be disabled when XenDesktop is connected to a VM with a vGPU orpassthrough GPU, with 3 or 4 monitors at 2560 1600 resolution.This limitation is a limitation of Windows 7. For details, see the Microsoft knowledgebase article Desktop background disappears with very large extended desktop onWindows 7.3.10. VMs configured with large memory fail toinitialize vGPU when bootedDescriptionWhen starting multiple VMs configured with large amounts of RAM (typically morethan 32GB per VM), a VM may fail to initialize vGPU. In this scenario, the VM boots instandard VGA mode with reduced resolution and color depth. The NVIDIA GRID GPUis present in Windows Device Manager but displays a warning sign, and the followingdevice status:www.nvidia.comGRID vGPU for Citrix XenServer Version367.106/370.12RN-06927-001 v4.3 (GRID) 11

Known Product LimitationsWindows has stopped this device because it has reported problems. (Code 43)The Citrix XenServer VM’s /var/log/messages log file contains these error messages:vmiop log:vmiop log:vmiop log:.vmiop log:.vmiop log:vmiop log:vmiop log:.vmiop log:error: NVOS status 0x29error: Assertion Failed at 0x7620fd4b:179error: 8 frames returned by backtraceerror: VGPU message 12 failed, result code: 0x29error: NVOS status 0x8error: Assertion Failed at 0x7620c8df:280error: 8 frames returned by backtraceerror: VGPU message 26 failed, result code: 0x8ResolutionvGPU reserves a portion of the VM’s framebuffer for use in GPU mapping of VM systemmemory. The reservation is sufficient to support up to 32GB of system memory, and maybe increased to accommodate up to 64GB by specifying enable large sys mem 1 inthe VM’s platform:vgpu extra args parameter:[[email protected] ]# xe vm-param-set uuid e71afda4-53f4-3a1b-6c92-a364a7f619c2platform:vgpu extra args "enable large sys mem 1"The setting takes effect the next time the VM is started or rebooted. With this settingin place, less GPU FB is available to applications running in the VM. To accommodatesystem memory larger than 64GB, the reservation can be further increased by specifyingextra fb reservation in the VM’s platform:vgpu extra args parameter,and setting its value to the desired reservation size in megabytes. The default value of64M is sufficient to support 64GB of RAM. We recommend adding 2M of reservationfor each additional 1GB of system memory. For example, to support 96GB of RAM, setextra fb reservation to 128:platform:vgpu extra args "enable large sys mem 1, extra fb reservation 128"The reservation can be reverted back to its default setting in one of the following ways:‣‣‣Removing the vgpu extra args key from the platform parameterRemoving enable large sys mem from the vgpu extra args keySetting enable large sys mem 03.11. vGPU host driver RPM upgrade failsDescriptionUpgrading vGPU host driver RPM fails with the following message on the console:[[email protected] ]# rpm –U NVIDIA-vGPU-xenserver-6.5-352.46.x86 64.rpmerror: Failed dependencies:NVIDIA-vgx-xenserver conflicts with NVIDIA-vGPUxenserver-6.5-352.46.x86 64[[email protected] ]#www.nvidia.comGRID vGPU for Citrix XenServer Version367.106/370.12RN-06927-001 v4.3 (GRID) 12

Known Product LimitationsResolutionUninstall the older vGPU RPM before installing the latest driver.Use the following command to uninstall the older vGPU RPM:[[email protected] ]# rpm –e NVIDIA-vgx-xenserverwww.nvidia.comGRID vGPU for Citrix XenServer Version367.106/370.12RN-06927-001 v4.3 (GRID) 13

Chapter 4.RESOLVED ISSUESNo resolved issues are reported in this release for Citrix XenServer.www.nvidia.comGRID vGPU for Citrix XenServer Version367.106/370.12RN-06927-001 v4.3 (GRID) 14

Chapter 5.KNOWN ISSUES5.1. Memory exhaustion can occur with vGPUprofiles that have 512 Mbytes or less of framebufferDescriptionMemory exhaustion can occur with vGPU profiles that have 512 Mbytes or less of framebuffer.This issue typically occurs in the following situations:‣‣‣‣‣Full screen 1080p video content is playing in a browser. In this situation, the sessionhangs and session reconnection fails.Multiple display heads are used with Citrix XenDesktop or VMware Horizon on aWindows 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 thathave 512 Mbytes or less of frame buffer.When memory exhaustion occurs, the NVIDIA host driver reports Xid error 31 and Xiderror 43 in XenServer’s /var/log/messages file.The following vGPU profiles have 512 Mbytes or less of frame buffer:‣‣‣Tesla M6-0B, M6-0QTesla M10-0B, M10-0QTesla M60-0B, M60-0Qwww.nvidia.comGRID vGPU for Citrix XenServer Version367.106/370.12RN-06927-001 v4.3 (GRID) 15

Known Issues‣‣GRID K100, K120QGRID K200, K220QThe root cause is a known issue associated with changes to the way that recent Microsoftoperating systems handle and allow access to overprovisioning messages and errors. Ifyour systems are provisioned with enough frame buffer to support your use cases, youshould not encounter these issues.Workaround‣‣‣Use an appropriately sized vGPU to ensure that the frame buffer supplied to a VMthrough the vGPU is adequate for your workloads.Monitor your frame buffer usage.If you are using Windows 10, consider these workarounds and solutions:‣‣Use a profile that has 1 Gbyte of frame buffer.Optimize your Windows 10 resource usage.To obtain information about best practices for improved user experience usingWindows 10 in virtual environments, complete the NVIDIA GRID vGPU ProfileSizing Guide for Windows 10 download request form.For more information, see also Windows 10 Optimization for XenDesktop on theCitrix blog.StatusOpenRef. #‣‣20013086418038615.2. VM bug checks after the guest VM driver forWindows 10 RS2 is installedDescriptionWhen the VM is rebooted after the guest VM driver for Windows 10 RS2 is installed, theVM bug checks. When Windows boots, it selects one of the standard supported videomodes. If Windows is booted directly with a display that is driven by an NVIDIA driver,for example a vGPU on Citrix XenServer, a blue screen crash occurs.This issue occurs when the screen resolution is switched from VGA mode to a resolutionthat is higher than 1920 1200.www.nvidia.comGRID vGPU for Citrix XenServer Version367.106/370.12RN-06927-001 v4.3 (GRID) 16

Known IssuesFixDownload and install Microsoft Windows Update KB4020102 from the MicrosoftUpdate Catalog.WorkaroundIf you have applied the fix, ignore this workaround.Otherwise, you can work around this issue until you are able to apply the fix by notusing resolutions higher than 1920 1200.Choose a GPU profile in Citrix XenCenter that does not allow resolutions higherthan 1920 1200.2. Before rebooting the VM, set the display resolution to 1920 1200 or lower.1.StatusNot an NVIDIA bugRef. #2003108615.3. On XenServer 7.0, VMs unexpectedly rebootand XenServer crashes or freezesDescriptionOn XenServer 7.0, VMs to which a vGPU is attached unexpectedly reboot and XenServercrashes or freezes.The event log in XenServer’s /var/log/crash/xen.log file lists the following errors:‣‣A fatal bus error on a component at the slot where the GPU card is installedA fatal error on a component at bus 0, device 2, function 0This issue occurs when page-modification logging (PML) is enabled on Intel BroadwellCPUs running XenServer 7.0. Citrix is aware of this issue and is working on a permanentfix.WorkaroundDisable page-modification logging (PML) as explained in XenServer 7 host crash whilestarting multiple virtual machines in the Citrix Support Knowledge Center.www.nvidia.comGRID vGPU for Citrix XenServer Version367.106/370.12RN-06927-001 v4.3 (GRID) 17

Known IssuesStatusNot an NVIDIA bugRef. #18532485.4. With no NVIDIA driver installed, XenServermisidentifies Tesla M10 cardsDescriptionAn erroneous entry in the pci.ids database causes Citrix XenServer to identify TeslaM10 cards as GRID M40 when no NVIDIA driver is installed.VersionCitrix XenServer 6.5 and 7.0WorkaroundNoneStatusNot an NVIDIA bugRef. #NVIDIA-420/17923415.5. GNOME Display Manager (GDM) fails to starton Red Hat Enterprise Linux 7.2 and CentOS 7.0DescriptionGDM fails to start on Red Hat Enterprise Linux 7.2 and CentOS 7.0 with the followingerror:Oh no! Something has gone wrong!WorkaroundPermanently enable permissive mode for Security Enhanced Linux (SELinux).www.nvidia.comGRID vGPU for Citrix XenServer Version367.106/370.12RN-06927-001 v4.3 (GRID) 18

Known Issues1.2.As root, edit the /etc/selinux/config file to set SELINUX to permissive.SELINUX permissiveReboot the system. ]# rebootFor more information, see Permissive Mode in Red Hat Enterprise Linux 7 SELinux User'sand Administrator's Guide.StatusNot an NVIDIA bugRef. #2001678685.6. Video goes blank when run in loop inWindows Media PlayerDescriptionWhen connected to a vGPU-enabled VM using Citrix XenDesktop, a video played backin looping mode on Windows Media Player goes blank or freezes after a few iterations.WorkaroundNoneStatusNot an NVIDIA bugRef. #1306623www.nvidia.comGRID vGPU for Citrix XenServer Version367.106/370.12RN-06927-001 v4.3 (GRID) 19

Known Issues5.7. Local VGA console is momentarily unblankedwhen XenDesktop changes resolution of the VMdesktopDescriptionWhen XenDesktop establishes a remote connection to a VM using vGPU, the VM’s localVGA console display in XenCenter is blanked (assuming the VM local console has notbeen disabled by setting platform:vgpu extra args "disable vnc 1"). If theXenDesktop session changes resolution of the VM’s desktop, the local VGA consolemomentarily unblanks, allowing a XenCenter user to briefly view the desktop.WorkaroundDisable the VM’s local VGA consolexe vm-param-set uuid vm-uuid platform:vgpu extra args "disable vnc 1"StatusOpenRef. #NVIDIA-145/13751645.8. VM bugchecks on shutdown/restart whenXenDesktop is installed and NVIDIA driver isuninstalled or upgraded.DescriptionIf the XenDesktop agent is installed in a VM before any NVIDIA GPUdriver is installed, the VM will bugcheck (bluescreen) when the NVIDIAdriver is subsequently upgraded or uninstalled. The bugcheck code is 0x7E,SYSTEM THREAD EXCEPTION NOT HANDLED.WorkaroundUse one of the following workarounds:‣Do a force shutdown of the VM and restart it.www.nvidia.comGRID vGPU for Citrix XenServer Version367.106/370.12RN-06927-001 v4.3 (GRID) 20

Known Issues‣Install the NVIDIA driver in guest VMs before installing XenDesktop.StatusOpenRef. #NVIDIA-295/2000181255.9. Application frame rate may drop whenrunning XenDesktop at 2560 1600 resolution.DescriptionAn application’s rendering frame rate may drop when running XenDesktop at 2560 1600resolution, relative to the frame rate obtained at lower resolutions.FixUsing the Windows regedit utility within the VM, open the HKLM\SOFTWARE\Citrix\Graphics registry key and create a new DWORD value, EncodeSpeed, witha value of 2. Reboot the VM. This setting may improve the delivered frame rate at theexpense of a reduction in image quality.StatusOpenRef. #NVIDIA-190/14163365.10. Windows VM BSODDescriptionWindows VM bugchecks on XenServer when running a large number of vGPU basedVMs.XenServer’s /var/log/messages file contains these error messages:NVRM: Xid (PCI:0000:08:00): 31, Ch 0000001e, engmask 00000111, intr 10000000NVRM: Xid (PCI:0000:08:00): 31, Ch 00000016, engmask 00000111, intr 10000000.vmiop log: error: Assertion Failed at 0xb5b898d8:4184vmiop log: error: 8 frames returned by backtracewww.nvidia.comGRID vGPU for Citrix XenServer Version367.106/370.12RN-06927-001 v4.3 (GRID) 21

Known Issuesvmiop log:vmiop log:vmiop log:vmiop log:vmiop log:vmiop log:vmiop log:vmiop log:vmiop log:vmiop log:vmiop log:vmiop log:vmiop log:vmiop log:vmiop ib/libnvidia-vgx.so( nv000793vgx 0x69d) [0xb5b8064d]/usr/lib/libnvidia-vgx.so( nv000479vgx 0x118) [0xb5b898d8]/usr/lib/libnvidia-vgx.so( nv000782vgx 0x59) [0xb5b85f49]/usr/lib/libnvidia-vgx.so( nv000347vgx 0x3db) [0xb5b932db]/usr/lib/libnvidia-vgx.so [0xb5b78e4a]/usr/lib/xen/bin/vgpu [0x80554be]/lib/libpthread.so.0 [0xb7612912]/lib/libc.so.6(clone 0x5e) [0xb76fc5ee]failed to initialize guest PTE entriesfailed to fill up guest PTE entries 3VGPU message 27 failed, result code: 0xff0000030xc1d00001, 0xff010000, 0x1a77ba000, 0x0, 0x1,0x1, 0x1000, 0x10202, 0xc1d00001, 0xff010000,0xcaf00004, 0x0Timeout occurred, reset initiated.VersionXenServer 6.2FixEnsure that you are running the latest OEM firmware for your GRID boards.StatusClosedRef. #NVIDIA-327/16321205.11. Windows VM BSOD when upgrading NVIDIAdrivers over a XenDesktop sessionDescriptionWindows VM bugchecks when NVIDIA guest drivers are upgraded over a XenDesktopsession.If the VM is restarted after the bugcheck, the upgraded driver loads correctly and fullfunctionality i

Citrix XenServer 7.1 RTM build is supported. Citrix XenServer 7.0 RTM build 125380 is supported. Citrix XenServer 6.5 Version 6.5 with XS65ESP1. The GRID vGPU Manager included in this release will not install without XenServer 6.5 SP1. Citrix XenDesktop Version 7.6