0% found this document useful (0 votes)

18 views110 pages

grid-vgpu-release-notes-citrix-xenserver

The document provides release notes for the Virtual GPU Software R550 for XenServer, detailing driver versions, compatibility requirements, and updates from releases 17.0 to 17.5. It includes information on validated platforms, known product limitations, resolved issues, and known issues specific to various releases. The document serves as a comprehensive guide for users to understand the capabilities and limitations of the software across different environments.

Uploaded by

Ashutosh Dhoundiyal

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

18 views110 pages

grid-vgpu-release-notes-citrix-xenserver

Uploaded by

Ashutosh Dhoundiyal

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 110

Virtual GPU Software R550 for

XenServer

Release Notes

RN-06927-001 _v17.0 through 17.5 | January 2025

Table of Contents
Chapter 1. Release Notes......................................................................................................................1
1.1. NVIDIA vGPU Software Driver Versions.................................................................................................1
1.2. Compatibility Requirements for the NVIDIA vGPU Manager and Guest VM Driver
....... 2
1.3. Updates in Release 17.5................................................................................................................................3
1.4. Updates in Release 17.4................................................................................................................................4
1.5. Updates in Release 17.3................................................................................................................................4
1.6. Updates in Release 17.2................................................................................................................................4
1.7. Updates in Release 17.1................................................................................................................................5
1.8. Updates in Release 17.0................................................................................................................................5
Chapter 2. Validated Platforms.......................................................................................................... 7
2.1. Supported NVIDIA GPUs and Validated Server Platforms........................................................... 7
2.1.1. Support for a Mixture of Time-Sliced vGPU Types on the Same GPU........................ 12
2.1.2. Switching the Mode of a GPU that Supports Multiple Display Modes....................... 12
2.2. Hypervisor Software Releases.................................................................................................................13
2.3. Guest OS Support......................................................................................................................................... 14
2.3.1. Windows Guest OS Support............................................................................................................ 15
2.3.1.1. Windows Guest OS Support in Release 17.5.................................................................. 15
2.3.1.2. Windows Guest OS Support in Release 17.4.................................................................. 15
2.3.1.3. Windows Guest OS Support in Release 17.3.................................................................. 16
2.3.1.4. Windows Guest OS Support in Release 17.2.................................................................. 16
2.3.1.5. Windows Guest OS Support in Release 17.1.................................................................. 17
2.3.1.6. Windows Guest OS Support in Release 17.0.................................................................. 17
2.3.2. Linux Guest OS Support.................................................................................................................... 18
2.3.2.1. Linux Guest OS Support in Release 17.5.......................................................................... 18
2.3.2.2. Linux Guest OS Support in Release 17.4.......................................................................... 19
2.3.2.3. Linux Guest OS Support in Release 17.3.......................................................................... 19
2.3.2.4. Linux Guest OS Support in Release 17.2.......................................................................... 20
2.3.2.5. Linux Guest OS Support in Release 17.1.......................................................................... 20
2.3.2.6. Linux Guest OS Support in Release 17.0.......................................................................... 21
2.4. NVIDIA CUDA Toolkit Version Support................................................................................................21
2.5. XenMotion with vGPU Support...............................................................................................................22
2.6. Multiple vGPU Support............................................................................................................................... 23
2.6.1. vGPUs that Support Multiple vGPUs Assigned to a VM.................................................... 23
2.6.2. Maximum Number of vGPUs Supported per VM.................................................................. 24
2.6.3. Hypervisor Releases that Support Multiple vGPUs Assigned to a VM........................ 25

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | ii
2.7. Peer-to-Peer CUDA Transfers over NVLink Support.................................................................... 25
2.7.1. vGPUs that Support Peer-to-Peer CUDA Transfers............................................................. 25
2.7.2. Hypervisor Releases that Support Peer-to-Peer CUDA Transfers.................................26
2.7.3. Guest OS Releases that Support Peer-to-Peer CUDA Transfers................................... 26
2.7.4. Limitations on Support for Peer-to-Peer CUDA Transfers................................................26
2.8. Unified Memory Support........................................................................................................................... 26
2.8.1. vGPUs that Support Unified Memory......................................................................................... 27
2.8.2. Guest OS Releases that Support Unified Memory............................................................... 27
2.8.3. Limitations on Support for Unified Memory........................................................................... 28
2.9. NVIDIA Deep Learning Super Sampling (DLSS) Support........................................................... 28
Chapter 3. Known Product Limitations........................................................................................ 30
3.1. vGPUs of different sizes on the same GPU are not supported.............................................. 30
3.2. NVENC does not support resolutions greater than 4096×4096............................................30
3.3. Nested Virtualization Is Not Supported by NVIDIA vGPU.......................................................... 31
3.4. Issues occur when the channels allocated to a vGPU are exhausted..................................31
3.5. Total frame buffer for vGPUs is less than the total frame buffer on the physical
GPU...........................................................................................................................................................................32
3.6. Issues may occur with graphics-intensive OpenCL applications on vGPU types with
limited frame buffer........................................................................................................................................35
3.7. In pass through mode, all GPUs connected to each other through NVLink must be
assigned to the same VM............................................................................................................................ 35
3.8. vGPU profiles with 512 Mbytes or less of frame buffer support only 1 virtual display
head on Windows 10...................................................................................................................................... 36
3.9. NVENC requires at least 1 Gbyte of frame buffer........................................................................36
3.10. VM running an incompatible NVIDIA vGPU guest driver fails to initialize vGPU when
booted..................................................................................................................................................................... 37
3.11. Single vGPU benchmark scores are lower than pass-through GPU...................................38
3.12. nvidia-smi fails to operate when all GPUs are assigned to GPU pass-through
mode........................................................................................................................................................................ 39
3.13. Windows Aero is disabled on Citrix Virtual Apps and Desktops session using 3 or
4 monitors in 2560×1600 resolution......................................................................................................41
3.14. VMs configured with large memory fail to initialize vGPU when booted......................... 41
3.15. vGPU host driver RPM upgrade fails.................................................................................................42
Chapter 4. Resolved Issues................................................................................................................43
4.1. Issues Resolved in Release 17.5.............................................................................................................43
4.2. Issues Resolved in Release 17.4.............................................................................................................43
4.3. Issues Resolved in Release 17.3.............................................................................................................43
4.4. Issues Resolved in Release 17.2.............................................................................................................44
4.5. Issues Resolved in Release 17.1.............................................................................................................45

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | iii
4.6. Issues Resolved in Release 17.0.............................................................................................................45
Chapter 5. Known Issues.................................................................................................................... 46
5.1. 17.0-17.3 Only: vGPU manager is unstable or randomly crashes with GPUs based
on NVIDIA Ampere and later architectures......................................................................................... 46
5.2. CATIA performance is degraded with large assembly visualization...................................... 46
5.3. 17.0-17.3 Only: Blue screen crash occurs with Tesla M10 after only the vGPU
Manager is upgraded...................................................................................................................................... 47
5.4. 17.0, 17.1 Only: Disabling or disconnecting a display can cause a TDR on a Windows
vGPU VM................................................................................................................................................................48
5.5. 17.0, 17.1 Only: XID error 120 causes multiple issues with NVIDIA vGPU on GPUs
with a GSP............................................................................................................................................................49
5.6. 17.0, 17.1 Only: XID error 119 causes the hypervisor host to hang or crash when
multiple vGPU VMs are shut down..........................................................................................................49
5.7. 17.0, 17.1 Only: Desktop is corrupted with XID errors 13 and 31 after vGPU VM is
migrated or suspended and resumed.................................................................................................... 50
5.8. NVIDIA Control Panel is not available in multiuser environments.......................................... 50
5.9. NVIDIA Control Panel crashes if a user session is disconnected and reconnected......52
5.10. CUDA profilers cannot gather hardware metrics on NVIDIA vGPU.................................... 53
5.11. NVIDIA vGPU software graphics driver for Windows sends a remote call to
ngx.download.nvidia.com............................................................................................................................... 53
5.12. Multiple RDP session reconnections on Windows Server 2022 can consume all
frame buffer........................................................................................................................................................ 54
5.13. NLS client fails to acquire a license with the error The allowed time to process
response has expired...................................................................................................................................... 55
5.14. With multiple active sessions, NVIDIA Control Panel incorrectly shows that the
system is unlicensed.......................................................................................................................................56
5.15. VP9 and AV1 decoding with web browsers are not supported on Microsoft
Windows Server 2019.................................................................................................................................... 56
5.16. Ubuntu guest driver initialization fails with vGPUs and GPUs that support SR-IOV
....57
5.17. nvidia-smi ignores the second NVIDIA vGPU device added to a Microsoft Windows
Server 2016 VM.................................................................................................................................................58
5.18. After an upgrade of the Linux graphics driver from an RPM package in a licensed
VM, licensing fails............................................................................................................................................. 59
5.19. After an upgrade of the Linux graphics driver from a Debian package, the driver
is not loaded into the VM.............................................................................................................................60
5.20. Desktop session freezes when a VM is migrated to or from a host running an
NVIDIA vGPU software 14 release............................................................................................................60
5.21. The reported NVENC frame rate is double the actual frame rate...................................... 61
5.22. Hypervisor host reboots when multiple cloned VMs are simultaneously powered
on or migrated....................................................................................................................................................62

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | iv
5.23. NVENC does not work with Teradici Cloud Access Software on Windows..................... 62
5.24. A licensed client might fail to acquire a license if a proxy is set......................................... 63
5.25. Session connection fails with four 4K displays and NVENC enabled on a 2Q, 3Q,
or 4Q vGPU.......................................................................................................................................................... 64
5.26. Disconnected sessions cannot be reconnected or might be reconnected very
slowly with NVWMI installed....................................................................................................................... 65
5.27. Linux VM hangs after vGPU migration to a host running a newer vGPU manager
version.....................................................................................................................................................................65
5.28. Idle Teradici Cloud Access Software session disconnects from Linux VM......................66
5.29. No virtual GPU types are listed in Citrix XenCenter.................................................................. 67
5.30. NVIDIA vGPU software graphics driver fails to load after upgrade on XenServer
......68
5.31. Windows guest VMs with vGPUs or GPUs with large BAR memory settings fail to
boot to the desktop in UEFI mode.......................................................................................................... 69
5.32. Migrated VM with more than two vGPUs crashes on destination host........................... 70
5.33. Driver upgrade in a Linux guest VM with multiple vGPUs might fail.................................70
5.34. NVIDIA Control Panel fails to start if launched too soon from a VM without
licensing information.......................................................................................................................................71
5.35. VNC client session goes blank and console VNC is corrupted when the guest driver
is uninstalled........................................................................................................................................................71
5.37. Suspend and resume between hosts running different versions of the vGPU
manager fails.......................................................................................................................................................72
5.38. On Linux, the frame rate might drop to 1 after several minutes........................................73
5.39. Citrix XenCenter displays misleading information about vGPU types.............................. 74
5.40. Citrix Virtual Apps and Desktops connection freezes initially.............................................. 75
5.41. DWM crashes randomly occur in Windows VMs........................................................................ 76
5.42. NVIDIA Control Panel fails to launch in a platform layer or published image................ 76
5.43. Remote desktop session freezes with assertion failure and XID error 43 after
migration................................................................................................................................................................77
5.44. Citrix Virtual Apps and Desktops session freezes when the desktop is unlocked
..... 77
5.45. NVIDIA vGPU software graphics driver fails after Linux kernel upgrade with DKMS
enabled................................................................................................................................................................... 78
5.46. On XenServer, all vGPUs in a VM must be of the same type................................................79
5.47. Console VGA cannot be disabled........................................................................................................ 80
5.48. Console VNC is unusable with Xorg on multiple vGPUs in a VM......................................... 80
5.49. Migration of VMs configured with vGPU stops before the migration is complete
..... 81
5.50. ECC memory settings for a vGPU cannot be changed by using NVIDIA X Server
Settings.................................................................................................................................................................. 82
5.51. Changes to ECC memory settings for a Linux vGPU VM by nvidia-smi might be
ignored.................................................................................................................................................................... 82
5.52. Incorrect GPU type shown for Quadro RTX 8000 GPUs in Citrix XenCenter................. 83

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | v
5.53. NVIDIA Notification Icon prevents log off of Citrix Published Application user
sessions..................................................................................................................................................................84
5.54. Host core CPU utilization is higher than expected for moderate workloads................. 84
5.55. Frame capture while the interactive logon message is displayed returns blank
screen...................................................................................................................................................................... 85
5.56. RDS sessions do not use the GPU with Microsoft Windows Server as guest OS...... 86
5.57. When the scheduling policy is fixed share, GPU utilization is reported as higher
than expected.....................................................................................................................................................86
5.58. nvidia-smi reports that vGPU migration is supported on all hypervisors........................87
5.59. NVIDIA Control Panel Crashes in a VM connected to two 4K displays............................. 88
5.60. vGPU guest VM driver not properly loaded on servers with more than 512 GB or
1 TB or more of system memory.............................................................................................................88
5.61. Luxmark causes a segmentation fault on an unlicensed Linux client...............................89
5.62. A segmentation fault in DBus code causes nvidia-gridd to exit on Red Hat
Enterprise Linux and CentOS..................................................................................................................... 90
5.63. No Manage License option available in NVIDIA X Server Settings by default............... 91
5.64. Licenses remain checked out when VMs are forcibly powered off.................................... 92
5.65. Memory exhaustion can occur with vGPU profiles that have 512 Mbytes or less
of frame buffer..................................................................................................................................................92
5.66. VM bug checks after the guest VM driver for Windows 10 RS2 is installed................. 94
5.67. On XenServer 7.0, VMs unexpectedly reboot and XenServer crashes or freezes...... 95
5.68. With no NVIDIA driver installed, XenServer misidentifies Tesla M10 cards....................95
5.69. GNOME Display Manager (GDM) fails to start on Red Hat Enterprise Linux 7.2 and
CentOS 7.0........................................................................................................................................................... 96
5.70. Video goes blank when run in loop in Windows Media Player.............................................. 97
5.71. Local VGA console is momentarily unblanked when Citrix Virtual Apps and
Desktops changes resolution of the VM desktop........................................................................... 97
5.72. VM bugchecks on shutdown/restart when Citrix Virtual Apps and Desktops is
installed and NVIDIA driver is uninstalled or upgraded................................................................. 98
5.73. Application frame rate may drop when running Citrix Virtual Apps and Desktops
at 2560×1600 resolution.............................................................................................................................. 99
5.74. Windows VM BSOD....................................................................................................................................99
5.75. Windows VM BSOD when upgrading NVIDIA drivers over a Citrix Virtual Apps and
Desktops session........................................................................................................................................... 100
5.76. XenCenter does not allow vGPUs to be selected as a GPU type for Linux VMs...... 101
5.77. If X server is killed on a RHEL7 VM running vGPU, XenCenter console may not
automatically switch to text console...................................................................................................102
5.78. Citrix Virtual Apps and Desktops shows only a black screen when connected to
a vGPU VM.........................................................................................................................................................102

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | vi
Chapter 1. Release Notes

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

Note: The most current version of the documentation for this release of NVIDIA vGPU
software can be found online at NVIDIA Virtual GPU Software Documentation.

1.1. NVIDIA vGPU Software Driver

Versions
Each release in this release family of NVIDIA vGPU software includes a specific version of
the NVIDIA Virtual GPU Manager, NVIDIA Windows driver, and NVIDIA Linux driver.

NVIDIA vGPU NVIDIA Virtual GPU NVIDIA Windows NVIDIA Linux Driver
Software Version Manager Version Driver Version Version
17.5 550.144.02 553.62 550.144.03
17.4 550.127.06 553.24 550.127.05
17.3 550.90.05 552.74 550.90.07
17.2 550.90.05 552.55 550.90.07
17.1 550.54.16 551.78 550.54.15
17.0 550.54.10 551.61 550.54.14

For details of which XenServer releases are supported, see Hypervisor Software Releases.

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 1
Release Notes

1.2. Compatibility Requirements for the

NVIDIA vGPU Manager and Guest
VM Driver
The releases of the NVIDIA vGPU Manager and guest VM drivers that you install must be
compatible. If you install an incompatible guest VM driver release for the release of the
vGPU Manager that you are using, the NVIDIA vGPU fails to load.
See VM running an incompatible NVIDIA vGPU guest driver fails to initialize vGPU when
booted.

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

Compatible NVIDIA vGPU Manager and Guest VM Driver Releases

The following combinations of NVIDIA vGPU Manager and guest VM driver releases are
compatible with each other.

‣ NVIDIA vGPU Manager with guest VM drivers from the same release
‣ NVIDIA vGPU Manager with guest VM drivers from different releases within the same
major release branch
‣ NVIDIA vGPU Manager from a later major release branch with guest VM drivers from
the previous branch

Note:

When NVIDIA vGPU Manager is used with guest VM drivers from a different release within
the same branch or from the previous branch, the combination supports only the features,
hardware, and software (including guest OSes) that are supported on both releases.

For example, if vGPU Manager from release 17.5 is used with guest drivers from release
16.4, the combination does not support Windows Server 2019 because NVIDIA vGPU
software release 17.5 does not support Windows Server 2019.

The following table lists the specific software releases that are compatible with the
components in the NVIDIA vGPU software 17 major release branch.

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 2
Release Notes

NVIDIA vGPU
Software
Component Releases Compatible Software Releases
NVIDIA vGPU Manager 17.0 through ‣ Guest VM driver releases 17.0 through 17.5
17.5
‣ All guest VM driver 16.x releases

Guest VM drivers 17.0 through NVIDIA vGPU Manager releases 17.0 through 17.5
17.5

Incompatible NVIDIA vGPU Manager and Guest VM Driver Releases

The following combinations of NVIDIA vGPU Manager and guest VM driver releases are
incompatible with each other.

‣ NVIDIA vGPU Manager from a later major release branch with guest VM drivers from
a production branch two or more major releases before the release of the vGPU
Manager
‣ NVIDIA vGPU Manager from an earlier major release branch with guest VM drivers
from a later branch
The following table lists the specific software releases that are incompatible with the
components in the NVIDIA vGPU software 17 major release branch.

NVIDIA vGPU
Software
Component Releases Incompatible Software Releases
NVIDIA vGPU Manager 17.0 through All guest VM driver releases 15.x and earlier
17.5
Guest VM drivers 17.0 through All NVIDIA vGPU Manager releases 16.x and earlier
17.5

1.3. Updates in Release 17.5

New Features in Release 17.5
‣ Security updates - see Security Bulletin: NVIDIA GPU Display Driver - January 2025,
which is posted shortly after the release date of this software and is listed on the
NVIDIA Product Security page
‣ Miscellaneous bug fixes

Hardware and Software Support Introduced in Release 17.5

‣ Newly supported guest OS releases:

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 3
Release Notes

‣ Windows 11 24H2
‣ Newly supported remoting solutions:
‣ Citrix Virtual Apps and Desktops version 7 2411

1.4. Updates in Release 17.4

New Features in Release 17.4
‣ Security updates - see Security Bulletin: NVIDIA GPU Display Driver - October 2024,
which is posted shortly after the release date of this software and is listed on the
NVIDIA Product Security page
‣ Miscellaneous bug fixes

Newly Supported Hardware and Software in Release 17.4

‣ Newly supported remoting solutions:
‣ Citrix Virtual Apps and Desktops version 7 2407

1.5. Updates in Release 17.3

New Features in Release 17.3
‣ Security updates - see Security Bulletin: NVIDIA GPU Display Driver - July 2024, which
is posted shortly after the release date of this software and is listed on the NVIDIA
Product Security page

Feature Support Withdrawn in Release 17.3

‣ Guest OSes no longer supported:
‣ Red Hat Enterprise Linux 7.9

1.6. Updates in Release 17.2

New Features in Release 17.2
‣ Security updates - see Security Bulletin: NVIDIA GPU Display Driver - June 2024, which
is posted shortly after the release date of this software and is listed on the NVIDIA
Product Security page
‣ Miscellaneous bug fixes

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 4
Release Notes

Hardware and Software Support Introduced in Release 17.2

‣ Newly supported graphics cards:
‣ NVIDIA L20 liquid cooled
‣ Newly supported guest OS releases:
‣ Red Hat Enterprise Linux 9.4 and 8.10
‣ Newly supported remoting solutions:
‣ Citrix Virtual Apps and Desktops version 7 2402

Feature Support Withdrawn in Release 17.2

‣ Guest OSes no longer supported:
‣ Red Hat Enterprise Linux 9.3, 9.0, 8.9, and 8.6

1.7. Updates in Release 17.1

New Features in Release 17.1
‣ Resolution of an issue that affects graphics cards that are supported only by NVIDIA
AI Enterprise.

1.8. Updates in Release 17.0

New Features in Release 17.0
‣ Distribution of a release of the Virtual GPU Manager and the NVIDIA vGPU software
graphics driver for Linux that is based on NVIDIA Linux open GPU kernel modules
‣ Support in the NVML API and the nvidia-smi command for getting information
about vGPUs with different amounts of frame buffer on the same physical GPU
‣ An option to configure guest VMs or physical hosts to acquire NVIDIA vGPU software
licenses when a user logs in instead of at boot time
‣ Miscellaneous bug fixes

Newly Supported Hardware and Software in Release 17.0

‣ Newly supported graphics cards:
‣ NVIDIA RTX 5880 Ada
‣ Newly supported guest OSes:

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 5
Release Notes

‣ Microsoft Windows 11 23H2

‣ Red Hat Enterprise Linux 9.3

Feature Support Withdrawn in Release 17.0

‣ Graphics cards no longer supported:
‣ Tesla M6
‣ Tesla M60
‣ Tesla P4
‣ Tesla P6
‣ Tesla P40
‣ Tesla P100 PCIe 12 GB
‣ Tesla P100 PCIe 16 GB
‣ Tesla P100 SXM2 16 GB
‣ Guest OSes no longer supported:
‣ Windows Server 2019

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 6
Chapter 2. Validated Platforms

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

2.1. Supported NVIDIA GPUs and

Validated Server Platforms
This release of NVIDIA vGPU software on XenServer provides support for several NVIDIA
GPUs running on validated server hardware platforms.
For a list of validated server platforms, refer to NVIDIA GRID Certified Servers.
The supported products for each type of NVIDIA vGPU software deployment depend on
the GPU.

GPUs Based on the NVIDIA Ada Lovelace Architecture

Supported NVIDIA vGPU
, ,
123
Mixed vGPU Configuration Software Products
Frame
Buffer Size
(Mixed-Size NVIDIA GPU Pass
GPU SR-IOV Mode) Series vGPU Through
NVIDIA L40S XenServer 8 N/A XenServer 8 ‣ vWS ‣ vWS
‣ vPC ‣ vApps
Citrix Citrix
‣ vApps
Hypervisor 8.2 Hypervisor 8.2

NVIDIA L40 XenServer 8 N/A XenServer 8 ‣ vWS ‣ vWS

‣ vPC ‣ vApps
Citrix Citrix
‣ vApps
Hypervisor 8.2 Hypervisor 8.2

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 7
Validated Platforms

Supported NVIDIA vGPU

, ,
123
Mixed vGPU Configuration Software Products
Frame
Buffer Size
(Mixed-Size NVIDIA GPU Pass
GPU SR-IOV Mode) Series vGPU Through
NVIDIA L20 XenServer 8 N/A XenServer 8 ‣ vWS ‣ vWS
‣ vPC ‣ vApps
Citrix Citrix
‣ vApps
Hypervisor 8.2 Hypervisor 8.2

NVIDIA L20 XenServer 8 N/A XenServer 8 ‣ vWS ‣ vWS

liquid cooled
‣ vPC ‣ vApps
Citrix Citrix
‣ vApps
Hypervisor 8.2 Hypervisor 8.2

NVIDIA L4 XenServer 8 N/A XenServer 8 ‣ vWS ‣ vWS

‣ vPC ‣ vApps
Citrix Citrix
‣ vApps
Hypervisor 8.2 Hypervisor 8.2

NVIDIA L2 XenServer 8 N/A XenServer 8 ‣ vWS ‣ vWS

‣ vPC ‣ vApps
Citrix Citrix
‣ vApps
Hypervisor 8.2 Hypervisor 8.2

NVIDIA RTX XenServer 8 N/A XenServer 8 ‣ vWS ‣ vWS

6000 Ada
‣ vPC ‣ vApps
Citrix Citrix
‣ vApps
Hypervisor 8.2 Hypervisor 8.2

NVIDIA RTX XenServer 8 N/A XenServer 8 ‣ vWS ‣ vWS

5880 Ada
‣ vPC ‣ vApps
Citrix Citrix
‣ vApps
Hypervisor 8.2 Hypervisor 8.2

NVIDIA RTX XenServer 8 N/A XenServer 8 ‣ vWS ‣ vWS

5000 Ada
‣ vPC ‣ vApps
Citrix Citrix
‣ vApps
Hypervisor 8.2 Hypervisor 8.2

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 8
Validated Platforms

GPUs Based on the NVIDIA Ampere Architecture

Supported NVIDIA vGPU
, ,
123
Mixed vGPU Configuration Software Products
Frame
Buffer Size
(Mixed-Size NVIDIA GPU Pass
GPU SR-IOV Mode) Series vGPU Through
NVIDIA A404 XenServer 8 N/A XenServer 8 ‣ vWS ‣ vWS
‣ vPC ‣ vApps
Citrix Citrix
‣ vApps
Hypervisor 8.2 Hypervisor 8.2

NVIDIA A16 XenServer 8 N/A XenServer 8 ‣ vWS ‣ vWS

‣ vPC ‣ vApps
Citrix Citrix
‣ vApps
Hypervisor 8.2 Hypervisor 8.2

NVIDIA A10 XenServer 8 N/A XenServer 8 ‣ vWS ‣ vWS

‣ vPC ‣ vApps
Citrix Citrix
‣ vApps
Hypervisor 8.2 Hypervisor 8.2

NVIDIA A2 XenServer 8 N/A XenServer 8 ‣ vWS ‣ vWS

‣ vPC ‣ vApps
Citrix Citrix
‣ vApps
Hypervisor 8.2 Hypervisor 8.2

NVIDIA RTX XenServer 8 N/A XenServer 8 ‣ vWS ‣ vWS

A60004
‣ vPC ‣ vApps
Citrix Citrix
‣ vApps
Hypervisor 8.2 Hypervisor 8.2

NVIDIA RTX XenServer 8 N/A XenServer 8 ‣ vWS ‣ vWS

A55004
‣ vPC ‣ vApps
Citrix Citrix
‣ vApps
Hypervisor 8.2 Hypervisor 8.2

NVIDIA RTX XenServer 8 N/A XenServer 8 ‣ vWS ‣ vWS

A50004
‣ vPC ‣ vApps
Citrix Citrix
‣ vApps
Hypervisor 8.2 Hypervisor 8.2

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 9
Validated Platforms

GPUs Based on the NVIDIA Turing Architecture

Note: SR-IOV and the configuration of vGPUs with different amounts of frame buffer
on the same physical GPU (mixed-size mode) are not supported on GPUs based on the
™
NVIDIA Turing architecture.

Supported NVIDIA vGPU Software

, ,
123
Mixed vGPU Series Products
GPU Configuration NVIDIA vGPU GPU Pass Through
Tesla T4 XenServer 8 ‣ vWS ‣ vWS
‣ vPC ‣ vApps
Citrix Hypervisor 8.2
‣ vApps

Quadro RTX 6000 4 XenServer 8 ‣ vWS ‣ vWS

‣ vPC ‣ vApps
Citrix Hypervisor 8.2
‣ vApps

Quadro RTX 6000 XenServer 8 ‣ vWS ‣ vWS

passive4
‣ vPC ‣ vApps
Citrix Hypervisor 8.2
‣ vApps

Quadro RTX 80004 XenServer 8 ‣ vWS ‣ vWS

‣ vPC ‣ vApps
Citrix Hypervisor 8.2
‣ vApps

Quadro RTX 8000 XenServer 8 ‣ vWS ‣ vWS

passive4
‣ vPC ‣ vApps
Citrix Hypervisor 8.2
‣ vApps

GPUs Based on the NVIDIA Volta Architecture

Note: SR-IOV and the configuration of vGPUs with different amounts of frame buffer
on the same physical GPU (mixed-size mode) are not supported on GPUs based on the
NVIDIA Volta architecture.

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 10
Validated Platforms

Supported NVIDIA vGPU Software

, ,
123
Mixed vGPU Series Products
GPU Configuration NVIDIA vGPU GPU Pass Through
Tesla V100 SXM2 XenServer 8 ‣ vWS ‣ vWS
‣ vPC ‣ vApps
Citrix Hypervisor 8.2
‣ vApps

Tesla V100 SXM2 XenServer 8 ‣ vWS ‣ vWS

32GB
‣ vPC ‣ vApps
Citrix Hypervisor 8.2
‣ vApps

Tesla V100 PCIe XenServer 8 ‣ vWS ‣ vWS

‣ vPC ‣ vApps
Citrix Hypervisor 8.2
‣ vApps

Tesla V100 PCIe 32GB XenServer 8 ‣ vWS ‣ vWS

‣ vPC ‣ vApps
Citrix Hypervisor 8.2
‣ vApps

Tesla V100S PCIe XenServer 8 ‣ vWS ‣ vWS

32GB
‣ vPC ‣ vApps
Citrix Hypervisor 8.2
‣ vApps

Tesla V100 FHHL XenServer 8 ‣ vWS ‣ vWS

‣ vPC ‣ vApps
Citrix Hypervisor 8.2
‣ vApps

GPUs Based on the NVIDIA Maxwell Graphic Architecture

Note: SR-IOV and the configuration of vGPUs with different amounts of frame buffer
on the same physical GPU (mixed-size mode) are not supported on GPUs based on the
™
NVIDIA Maxwell graphic architecture.

Supported NVIDIA vGPU Software

, ,
123
Mixed vGPU Series Products
GPU Configuration NVIDIA vGPU GPU Pass Through
Tesla M10 XenServer 8 ‣ vWS ‣ vWS
‣ vPC

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 11
Validated Platforms

Supported NVIDIA vGPU Software

, ,
123
Mixed vGPU Series Products
GPU Configuration NVIDIA vGPU GPU Pass Through
Citrix Hypervisor 8.2 ‣ vApps ‣ vApps

2.1.1. Support for a Mixture of Time-Sliced vGPU

Types on the Same GPU
XenServer supports a mixture of time-sliced vGPUs with the same amount of frame
buffer from different virtual GPU series on the same physical GPU. A-series, B-series, and
Q-series vGPUs with the same amount of frame buffer, for example, A40-2B and A40-2Q,
can reside on the same physical GPU simultaneously. However, vGPUs with different
amounts of frame buffer are not supported on the same GPU.
For example, the following combinations of vGPUs are not supported on the same GPU:

‣ A40-2Q and A40-4Q

‣ A40-2B and A40-4Q

2.1.2. Switching the Mode of a GPU that

Supports Multiple Display Modes
Some GPUs support display-off and display-enabled modes but must be used in NVIDIA
vGPU software deployments in display-off mode.
The GPUs listed in the following table support multiple display modes. As shown in the
table, some GPUs are supplied from the factory in display-off mode, but other GPUs are
supplied in a display-enabled mode.
GPU Mode as Supplied from the Factory
NVIDIA A40 Display-off
NVIDIA L40 Display-off
NVIDIA L40S Display-off
NVIDIA L20 Display-off
NVIDIA L20 liquid cooled Display-off
NVIDIA RTX 5000 Ada Display enabled

1
The supported products are as follows:

‣ vWS: NVIDIA RTX Virtual Workstation

‣ vPC: NVIDIA Virtual PC
‣ vApps: NVIDIA Virtual Applications
2
N/A indicates that the deployment is not supported.
3
vApps is supported only on Windows operating systems.
4
This GPU is supported only in displayless mode. In displayless mode, local physical display connectors are disabled.

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 12
Validated Platforms

GPU Mode as Supplied from the Factory

NVIDIA RTX 6000 Ada Display enabled
NVIDIA RTX A5000 Display enabled
NVIDIA RTX A5500 Display enabled
NVIDIA RTX A6000 Display enabled

A GPU that is supplied from the factory in display-off mode, such as the NVIDIA A40 GPU,
might be in a display-enabled mode if its mode has previously been changed.
To change the mode of a GPU that supports multiple display modes, use the
displaymodeselector tool, which you can request from the NVIDIA Display Mode
Selector Tool page on the NVIDIA Developer website.

Note: Only the GPUs listed in the table support the displaymodeselector tool. Other
GPUs that support NVIDIA vGPU software do not support the displaymodeselector tool
and, unless otherwise stated, do not require display mode switching.

2.2. Hypervisor Software Releases

Reversion to the XenServer Name for Hypervisor Software
Citrix has reverted the name of its hypervisor software for releases after Citrix Hypervisor
8.2 to XenServer. All XenServer updates are identified by the single product name and
release number XenServer 8.
For more information, visit the XenServer website.

Note: The name of the Citrix virtual desktop software product and the format of its
release numbers remain unchanged.

Supported XenServer Releases

This release family of NVIDIA vGPU software is supported on the XenServer releases
listed in the table.

Note:

Support for Citrix Hypervisor requires the Premium Edition (previously Enterprise Edition)
of Citrix Hypervisor. For details, see Licensing in the Citrix documentation.

Cumulative update releases for a base release of XenServer are compatible with the base
release and can also be used with this version of NVIDIA vGPU software unless expressly
stated otherwise.

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 13
Validated Platforms

Software Releases Supported Notes

XenServer 8 XenServer 8 and all updates to This release supports
XenServer 8. XenMotion with vGPU on
suitable GPUs as listed in
XenMotion with vGPU Support.

Citrix Hypervisor 8.2 RTM build and compatible This release supports
cumulative update releases XenMotion with vGPU on
suitable GPUs as listed in
XenMotion with vGPU Support.

Supported Virtual Desktop Software Releases

This release supports only the virtual desktop software releases listed in the table. Except
where otherwise stated, HDX 3D Pro mode is supported but not required.

Software Releases Supported

Citrix Virtual Apps and

Desktops Note: All versions supported by earlier NVIDIA vGPU
software 17 releases are also supported.

Since 17.5: Version 7 2411

Since 17.4: Version 7 2407

Since 17.2: Version 7 2402

Versions 7 2311, 7 2308 7 2305, 7 2303, 7 2212, 7 2209, 7 2206,

7 2203, 7 2112, 7 2109, 7 2106, 7 2103, 7 2012, 7 2009, 7 2006, 7
2003, 7 1912, 7 1909, 7 1906, and 7 1903

XenApp/XenDesktop Version 7.15

Note: Version 7.15 is supported only in HDX 3D Pro mode.

HDX 3D Pro mode is required to ensure that the NVIDIA
GPU can be used unrestricted.

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

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 14
Validated Platforms

Use only a guest OS release that is listed as supported by NVIDIA vGPU software with your
virtualization software. To be listed as supported, a guest OS release must be supported
not only by NVIDIA vGPU software, but also by your virtualization software. NVIDIA cannot
support guest OS releases that your virtualization software does not support.
NVIDIA vGPU software supports only 64-bit guest operating systems. No 32-bit guest
operating systems are supported.

2.3.1. Windows Guest OS Support

NVIDIA vGPU software supports only the 64-bit Windows releases listed as a guest OS on
XenServer. The releases of XenServer for which a Windows 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.
Windows Enterprise multi-session is not supported.
XenMotion with vGPU is supported on supported Windows guest OS releases.

2.3.1.1. Windows Guest OS Support in Release 17.5

NVIDIA vGPU - Pass-Through GPU -
Guest OS XenServer Releases XenServer Releases
Windows Server 2022 XenServer 8.2 XenServer 8.2
XenServer 8 XenServer 8
Windows 11 24H2 and all Windows 11 releases XenServer 8 XenServer 8
supported by Microsoft up to and including this
release
Windows 10 2022 Update (22H2) and all XenServer 8.2 XenServer 8.2
Windows 10 releases supported by Microsoft
XenServer 8 XenServer 8
up to and including this release
See Note (1)

Note:
1. The hardware-accelerated GPU scheduling feature introduced in Windows 10 May
2020 Update (2004) is not supported on GPUs based on the Maxwell architecture and
is supported only in pass-through mode on GPUs based on later architectures.

2.3.1.2. Windows Guest OS Support in Release 17.4

NVIDIA vGPU - Pass-Through GPU -
Guest OS XenServer Releases XenServer Releases
Windows Server 2022 XenServer 8.2 XenServer 8.2

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 15
Validated Platforms

NVIDIA vGPU - Pass-Through GPU -

Guest OS XenServer Releases XenServer Releases
XenServer 8 XenServer 8
Windows 11 23H2 and all Windows 11 releases XenServer 8 XenServer 8
supported by Microsoft up to and including this
release
Windows 10 2022 Update (22H2) and all XenServer 8.2 XenServer 8.2
Windows 10 releases supported by Microsoft
XenServer 8 XenServer 8
up to and including this release
See Note (1)

2.3.1.3. Windows Guest OS Support in Release 17.3

NVIDIA vGPU - Pass-Through GPU -
Guest OS XenServer Releases XenServer Releases
Windows Server 2022 XenServer 8.2 XenServer 8.2
XenServer 8 XenServer 8
Windows 11 23H2 and all Windows 11 releases XenServer 8 XenServer 8
supported by Microsoft up to and including this
release
Windows 10 2022 Update (22H2) and all XenServer 8.2 XenServer 8.2
Windows 10 releases supported by Microsoft
XenServer 8 XenServer 8
up to and including this release
See Note (1)

2.3.1.4. Windows Guest OS Support in Release 17.2

NVIDIA vGPU - Pass-Through GPU -
Guest OS XenServer Releases XenServer Releases
Windows Server 2022 XenServer 8.2 XenServer 8.2
XenServer 8 XenServer 8

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 16
Validated Platforms

NVIDIA vGPU - Pass-Through GPU -

Guest OS XenServer Releases XenServer Releases
Windows 11 23H2 and all Windows 11 releases XenServer 8 XenServer 8
supported by Microsoft up to and including this
release
Windows 10 2022 Update (22H2) and all XenServer 8.2 XenServer 8.2
Windows 10 releases supported by Microsoft
XenServer 8 XenServer 8
up to and including this release
See Note (1)

2.3.1.5. Windows Guest OS Support in Release 17.1

2.3.1.6. Windows Guest OS Support in Release 17.0

NVIDIA vGPU - Pass-Through GPU -
Guest OS XenServer Releases XenServer Releases
Windows Server 2022 XenServer 8.2 XenServer 8.2
XenServer 8 XenServer 8

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 17
Validated Platforms

NVIDIA vGPU - Pass-Through GPU -

2.3.2. Linux Guest OS Support

NVIDIA vGPU software supports only the Linux distributions listed as a guest OS on
XenServer. The releases of XenServer 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.
XenMotion with vGPU is not supported on any Linux guest OS release.
Rocky Linux releases that are compatible with supported Red Hat Enterprise Linux
releases are also supported as a guest OS.

2.3.2.1. Linux Guest OS Support in Release 17.5

NVIDIA vGPU - Pass-Through GPU -
Guest OS XenServer Releases XenServer Releases
Red Hat Enterprise Linux 8.10 XenServer 8.2 XenServer 8.2
XenServer 8 XenServer 8
Red Hat Enterprise Linux 8.8 XenServer 8.2 XenServer 8.2
XenServer 8 XenServer 8
Deprecated: CentOS Linux 8 (2105) XenServer 8.2 XenServer 8.2
XenServer 8 XenServer 8
Deprecated: CentOS 7.6-7.8 XenServer 8.2 XenServer 8.2
XenServer 8 XenServer 8
Ubuntu 20.04 LTS XenServer 8.2 XenServer 8.2

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 18
Validated Platforms

NVIDIA vGPU - Pass-Through GPU -

Guest OS XenServer Releases XenServer Releases
XenServer 8 XenServer 8

2.3.2.2. Linux Guest OS Support in Release 17.4

2.3.2.3. Linux Guest OS Support in Release 17.3

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 19
Validated Platforms

2.3.2.4. Linux Guest OS Support in Release 17.2

NVIDIA vGPU - Pass-Through GPU -
Guest OS XenServer Releases XenServer Releases
Red Hat Enterprise Linux 8.10 XenServer 8.2 XenServer 8.2
XenServer 8 XenServer 8
Red Hat Enterprise Linux 8.8 XenServer 8.2 XenServer 8.2
XenServer 8 XenServer 8
Deprecated: CentOS Linux 8 (2105) XenServer 8.2 XenServer 8.2
XenServer 8 XenServer 8
Red Hat Enterprise Linux 7.9 XenServer 8.2 XenServer 8.2
XenServer 8 XenServer 8
Deprecated: CentOS 7.6-7.8 XenServer 8.2 XenServer 8.2
XenServer 8 XenServer 8
Ubuntu 20.04 LTS XenServer 8.2 XenServer 8.2
XenServer 8 XenServer 8

2.3.2.5. Linux Guest OS Support in Release 17.1

NVIDIA vGPU - Pass-Through GPU -
Guest OS XenServer Releases XenServer Releases
Red Hat Enterprise Linux 8.9 XenServer 8.2 XenServer 8.2
XenServer 8 XenServer 8
Red Hat Enterprise Linux 8.8 XenServer 8.2 XenServer 8.2
XenServer 8 XenServer 8
Red Hat Enterprise Linux 8.6 XenServer 8.2 XenServer 8.2
XenServer 8 XenServer 8
Deprecated: CentOS Linux 8 (2105) XenServer 8.2 XenServer 8.2
XenServer 8 XenServer 8
Red Hat Enterprise Linux 7.9 XenServer 8.2 XenServer 8.2
XenServer 8 XenServer 8
Deprecated: CentOS 7.6-7.8 XenServer 8.2 XenServer 8.2
XenServer 8 XenServer 8
Ubuntu 20.04 LTS XenServer 8.2 XenServer 8.2

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 20
Validated Platforms

NVIDIA vGPU - Pass-Through GPU -

Guest OS XenServer Releases XenServer Releases
XenServer 8 XenServer 8

2.3.2.6. Linux Guest OS Support in Release 17.0

2.4. NVIDIA CUDA Toolkit Version

Support
The releases in this release family of NVIDIA vGPU software support NVIDIA CUDA Toolkit
12.4.
To build a CUDA application, the system must have the NVIDIA CUDA Toolkit and the
libraries required for linking. For details of the components of NVIDIA CUDA Toolkit, refer
to NVIDIA CUDA Toolkit 12.4 Release Notes.
To run a CUDA application, the system must have a CUDA-enabled GPU and an NVIDIA
display driver that is compatible with the NVIDIA CUDA Toolkit release that was used to
build the application. If the application relies on dynamic linking for libraries, the system
must also have the correct version of these libraries.

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 21
Validated Platforms

For more information about NVIDIA CUDA Toolkit, refer to CUDA Toolkit Documentation
12.4.

Note:
If you are using NVIDIA vGPU software with CUDA on Linux, avoid conflicting installation
methods by installing CUDA from a distribution-independent runfile package. Do not
install CUDA from a distribution-specific RPM or Deb package.
To ensure that the NVIDIA vGPU software graphics driver is not overwritten when CUDA is
installed, deselect the CUDA driver when selecting the CUDA components to install.
For more information, see NVIDIA CUDA Installation Guide for Linux.

2.5. XenMotion with vGPU Support

XenMotion with vGPU is supported on all supported GPUs, but only on a subset of
supported XenServer releases and guest operating systems.

Limitations with XenMotion with vGPU Support

vGPU migration is disabled for a VM for which any of the following NVIDIA CUDA Toolkit
features is enabled:

‣ Unified memory
‣ Debuggers
‣ Profilers

Supported Hypervisor Software Releases

XenServer 8
Citrix Hypervisor 8.2

Supported Guest OS Releases

Windows only. XenMotion with vGPU is not supported on Linux.

Known Issues with XenMotion with vGPU Support

Use Case Affected GPUs Issue
Migration of a guest All GPUs that support 17.0, 17.1 Only: Desktop is corrupted with
vGPU VM XenMotion with vGPU XID errors 13 and 31 after vGPU VM is
migrated or suspended and resumed
Simultaneous All GPUs that support Hypervisor host reboots when multiple
migration of multiple XenMotion with vGPU cloned VMs are simultaneously powered on
VMs or migrated

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 22
Validated Platforms

Use Case Affected GPUs Issue

Migration between All GPUs that support Migration of VMs configured with vGPU
hosts with different XenMotion with vGPU stops before the migration is complete
ECC memory
configuration

2.6. Multiple vGPU Support

To support applications and workloads that are compute or graphics intensive, multiple
vGPUs can be added to a single VM. The assignment of more than one vGPU to a VM is
supported only on a subset of vGPUs and hypervisor software releases.

2.6.1. vGPUs that Support Multiple vGPUs

Assigned to a VM
Only Q-series vGPUs that are allocated all of the physical GPU's frame buffer are
supported.

Multiple vGPU Support on the NVIDIA Ada Lovelace Architecture

Board vGPU
NVIDIA L40S L40S-48Q
NVIDIA L40 L40-48Q
NVIDIA L20 L20-48Q

NVIDIA L20 liquid cooled

NVIDIA L4 L4-24Q
NVIDIA L2 L2-24Q
NVIDIA RTX 6000 Ada RTX 6000 Ada-48Q
NVIDIA RTX 5880 Ada RTX 5880 Ada-48Q
NVIDIA RTX 5000 Ada RTX 5000 Ada-32Q

Multiple vGPU Support on the NVIDIA Ampere GPU Architecture

Board vGPU
NVIDIA A40 A40-48Q See Note (1).
NVIDIA A16 A16-16Q See Note (1).
NVIDIA A10 A10-24Q See Note (1).
NVIDIA A2 A2-16Q See Note (1).

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 23
Validated Platforms

Board vGPU
NVIDIA RTX A6000 A6000-48Q See Note (1).
NVIDIA RTX A5500 A5500-24Q See Note (1).
NVIDIA RTX A5000 A5000-24Q See Note (1).

Multiple vGPU Support on the NVIDIA Turing GPU Architecture

Board vGPU
Tesla T4 T4-16Q
Quadro RTX 6000 RTX6000-24Q
Quadro RTX 6000 passive RTX6000P-24Q
Quadro RTX 8000 RTX8000-48Q
Quadro RTX 8000 passive RTX8000P-48Q

Multiple vGPU Support on the NVIDIA Volta GPU Architecture

Board vGPU
Tesla V100 SXM2 32GB V100DX-32Q
Tesla V100 PCIe 32GB V100D-32Q
Tesla V100S PCIe 32GB V100S-32Q
Tesla V100 SXM2 V100X-16Q
Tesla V100 PCIe V100-16Q
Tesla V100 FHHL V100L-16Q

Multiple vGPU Support on the NVIDIA Maxwell GPU Architecture

Board vGPU
Tesla M10 M10-8Q

Note:

1. This type of vGPU cannot be assigned with other types of vGPU to the same VM.

2.6.2. Maximum Number of vGPUs Supported

per VM
NVIDIA vGPU software supports up to a maximum of 16 vGPUs per VM.

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 24
Validated Platforms

2.6.3. Hypervisor Releases that Support Multiple

vGPUs Assigned to a VM
All hypervisor releases that support NVIDIA vGPU software are supported.

2.7. Peer-to-Peer CUDA Transfers over

NVLink Support
Peer-to-peer CUDA transfers enable device memory between vGPUs on different GPUs
that are assigned to the same VM to be accessed from within the CUDA kernels. NVLink
is a high-bandwidth interconnect that enables fast communication between such vGPUs.
Peer-to-Peer CUDA transfers over NVLink are supported only on a subset of vGPUs,
XenServer releases, and guest OS releases.

2.7.1. vGPUs that Support Peer-to-Peer CUDA

Transfers
Only Q-series vGPUs that are allocated all of the physical GPU's frame buffer on physical
GPUs that support NVLink are supported.

Peer-to-Peer CUDA Transfer Support on the NVIDIA Ampere GPU

Architecture
Board vGPU
NVIDIA A40 A40-48Q
NVIDIA A10 A10-24Q
NVIDIA RTX A6000 A6000-48Q
NVIDIA RTX A5500 A5500-24Q
NVIDIA RTX A5000 A5000-24Q

Peer-to-Peer CUDA Transfer Support on the NVIDIA Turing GPU

Architecture
Board vGPU
Quadro RTX 6000 RTX6000-24Q
Quadro RTX 6000 passive RTX6000P-24Q
Quadro RTX 8000 RTX8000-48Q
Quadro RTX 8000 passive RTX8000P-48Q

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 25
Validated Platforms

Peer-to-Peer CUDA Transfer Support on the NVIDIA Volta GPU Architecture

Board vGPU
Tesla V100 SXM2 32GB V100DX-32Q
Tesla V100 SXM2 V100X-16Q

2.7.2. Hypervisor Releases that Support Peer-to-

Peer CUDA Transfers
Peer-to-Peer CUDA transfers over NVLink are supported on all hypervisor releases that
support the assignment of more than one vGPU to a VM. For details, see Multiple vGPU
Support.

2.7.3. Guest OS Releases that Support Peer-to-

Peer CUDA Transfers
Linux only. Peer-to-Peer CUDA transfers over NVLink are not supported on Windows.

2.7.4. Limitations on Support for Peer-to-Peer

CUDA Transfers
‣ NVSwitch is not supported. Only direct connections are supported.
‣ PCIe is not supported.
‣ SLI is not supported.

2.8. Unified Memory Support

Unified memory is a single memory address space that is accessible from any CPU or
GPU in a system. It creates a pool of managed memory that is shared between the CPU
and GPU to provide a simple way to allocate and access data that can be used by code
running on any CPU or GPU in the system. Unified memory is supported only on a subset
of vGPUs and guest OS releases.

Note: Unified memory is disabled by default. If used, you must enable unified memory
individually for each vGPU that requires it by setting a vGPU plugin parameter. NVIDIA
CUDA Toolkit profilers are supported and can be enabled on a VM for which unified
memory is enabled.

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 26
Validated Platforms

2.8.1. vGPUs that Support Unified Memory

Only Q-series vGPUs that are allocated all of the physical GPU's frame buffer on physical
GPUs that support unified memory are supported.

Unified Memory Support on the NVIDIA Ada Lovelace GPU Architecture

Board vGPU
NVIDIA L40 L40-48Q
NVIDIA L40S L40S-48Q
NVIDIA L20 L20-48Q

NVIDIA L20 liquid cooled

NVIDIA L4 L4-24Q
NVIDIA L2 L2-24Q
NVIDIA RTX 6000 Ada RTX 6000 Ada-48Q
NVIDIA RTX 5880 Ada RTX 5880 Ada-48Q
NVIDIA RTX 5000 Ada RTX 5000 Ada-32Q

Unified Memory Support on the NVIDIA Ampere GPU Architecture

Board vGPU
NVIDIA A40 A40-48Q
NVIDIA A16 A16-16Q
NVIDIA A10 A10-24Q
NVIDIA A2 A2-16Q
NVIDIA RTX A6000 A6000-48Q
NVIDIA RTX A5500 A5500-24Q
NVIDIA RTX A5000 A5000-24Q

2.8.2. Guest OS Releases that Support Unified

Memory
Linux only. Unified memory is not supported on Windows.

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 27
Validated Platforms

2.8.3. Limitations on Support for Unified Memory

‣ Only Q-series vGPUs that are allocated all of the physical GPU's frame buffer on
physical GPUs that support unified memory are supported. Fractional time-sliced
vGPUs are not supported.
‣ When unified memory is enabled for a VM, XenMotion with vGPU is disabled for the
VM.

2.9. NVIDIA Deep Learning Super

Sampling (DLSS) Support
NVIDIA vGPU software supports NVIDIA DLSS on NVIDIA RTX Virtual Workstation.
Supported DLSS versions: 2.0. Version 1.0 is not supported.
Supported GPUs:

‣ NVIDIA L40
‣ NVIDIA L40S
‣ NVIDIA L20
‣ NVIDIA L20 liquid cooled
‣ NVIDIA L4
‣ NVIDIA L2
‣ NVIDIA RTX 6000 Ada
‣ NVIDIA RTX 5880 Ada
‣ NVIDIA RTX 5000 Ada
‣ NVIDIA A40
‣ NVIDIA A16
‣ NVIDIA A2
‣ NVIDIA A10
‣ NVIDIA RTX A6000
‣ NVIDIA RTX A5500
‣ NVIDIA RTX A5000
‣ Tesla T4
‣ Quadro RTX 8000
‣ Quadro RTX 8000 passive
‣ Quadro RTX 6000

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 28
Validated Platforms

‣ Quadro RTX 6000 passive

Note: NVIDIA graphics driver components that DLSS requires are installed only if a
supported GPU is detected during installation of the driver. Therefore, if the creation of
VM templates includes driver installation, the template should be created from a VM that
is configured with a supported GPU while the driver is being installed.

Supported applications: only applications that use nvngx_dlss.dll version 2.0.18 or

newer

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 29
Chapter 3. Known Product
Limitations

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

3.1. vGPUs of different sizes on the

same GPU are not supported
XenServer supports a mixture of time-sliced vGPUs with the same amount of frame
buffer from different virtual GPU series on the same physical GPU. A-series, B-series, and
Q-series vGPUs with the same amount of frame buffer, for example, A40-2B and A40-2Q,
can reside on the same physical GPU simultaneously. However, vGPUs with different
amounts of frame buffer are not supported on the same GPU.

3.2. NVENC does not support

resolutions greater than
4096×4096
Description
The NVIDIA hardware-based H.264 video encoder (NVENC) does not support resolutions
greater than 4096×4096. This restriction applies to all NVIDIA GPU architectures and
is imposed by the GPU encoder hardware itself, not by NVIDIA vGPU software. The
maximum supported resolution for each encoding scheme is listed in the documentation
for NVIDIA Video Codec SDK. This limitation affects any remoting tool where H.264
encoding is used with a resolution greater than 4096×4096. Most supported remoting
tools fall back to software encoding in such scenarios.

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 30
Known Product Limitations

Workaround
®
If your GPU is based on a GPU architecture later than the NVIDIA Maxwell architecture,
use H.265 encoding. H.265 is more efficient than H.264 encoding and has a maximum
resolution of 8192×8192. On GPUs based on the NVIDIA Maxwell architecture, H.265 has
the same maximum resolution as H.264, namely 4096×4096.

Note: Resolutions greater than 4096×4096 are supported only by the H.265 decoder that
64-bit client applications use. The H.265 decoder that 32-bit applications use supports a
maximum resolution of 4096×4096.

Because the client-side Workspace App on Windows is a 32-bit application, resolutions

greater than 4096×4096 are not supported for Windows clients of Citrix Virtual Apps
and Desktops. Therefore, if you are using a Windows client with Citrix Virtual Apps and
Desktops, ensure that you are using H.264 hardware encoding with the default Use video
codec for compression Citrix graphics policy setting, namely Actively Changing Regions.
This policy setting encodes only actively changing regions of the screen (for example, a
window in which a video is playing). Provided that the number of pixels along any edge of
the actively changing region does not exceed 4096, H.264 encoding is offloaded to the
NVENC hardware encoder.

3.3. Nested Virtualization Is Not

Supported by NVIDIA vGPU
NVIDIA vGPU deployments do not support nested virtualization, that is, running a
hypervisor in a guest VM. For example, enabling the Hyper-V role in a guest VM running
the Windows Server OS is not supported because it entails enabling nested virtualization.
Similarly, enabling Windows Hypervisor Platform is not supported because it requires the
Hyper-V role to be enabled.

3.4. Issues occur when the channels

allocated to a vGPU are exhausted
Description
Issues occur when the channels allocated to a vGPU are exhausted and the guest VM to
which the vGPU is assigned fails to allocate a channel to the vGPU. A physical GPU has a
fixed number of channels and the number of channels allocated to each vGPU is inversely
proportional to the maximum number of vGPUs allowed on the physical GPU.

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 31
Known Product Limitations

When the channels allocated to a vGPU are exhausted and the guest VM fails to allocate
a channel, the following errors are reported on the hypervisor host or in an NVIDIA bug
report:

Jun 26 08:01:25 srvxen06f vgpu-3[14276]: error: vmiop_log: (0x0): Guest attempted to

allocate channel above its max channel limit 0xfb
Jun 26 08:01:25 srvxen06f vgpu-3[14276]: error: vmiop_log: (0x0): VGPU message 6
failed, result code: 0x1a
Jun 26 08:01:25 srvxen06f vgpu-3[14276]: error: vmiop_log: (0x0):
0xc1d004a1, 0xff0e0000, 0xff0400fb, 0xc36f,
Jun 26 08:01:25 srvxen06f vgpu-3[14276]: error: vmiop_log: (0x0): 0x1,
0xff1fe314, 0xff1fe038, 0x100b6f000, 0x1000,
Jun 26 08:01:25 srvxen06f vgpu-3[14276]: error: vmiop_log: (0x0):
0x80000000, 0xff0e0200, 0x0, 0x0, (Not logged),
Jun 26 08:01:25 srvxen06f vgpu-3[14276]: error: vmiop_log: (0x0): 0x1, 0x0
Jun 26 08:01:25 srvxen06f vgpu-3[14276]: error: vmiop_log: (0x0): , 0x0

Workaround
Use a vGPU type with more frame buffer, thereby reducing the maximum number of
vGPUs allowed on the physical GPU. As a result, the number of channels allocated to each
vGPU is increased.

3.5. Total frame buffer for vGPUs is less

than the total frame buffer on the
physical GPU
Some of the physical GPU's frame buffer is used by the hypervisor on behalf of the VM
for allocations that the guest OS would otherwise have made in its own frame buffer. The
frame buffer used by the hypervisor is not available for vGPUs on the physical GPU. In
NVIDIA vGPU deployments, frame buffer for the guest OS is reserved in advance, whereas
in bare-metal deployments, frame buffer for the guest OS is reserved on the basis of the
runtime needs of applications.
If error-correcting code (ECC) memory is enabled on a physical GPU that does not have
HBM2 memory, the amount of frame buffer that is usable by vGPUs is further reduced.
All types of vGPU are affected, not just vGPUs that support ECC memory.
On all GPUs that support ECC memory and, therefore, dynamic page retirement,
additional frame buffer is allocated for dynamic page retirement. The amount that is
allocated is inversely proportional to the maximum number of vGPUs per physical GPU. All
GPUs that support ECC memory are affected, even GPUs that have HBM2 memory or for
which ECC memory is disabled.
The approximate amount of frame buffer that NVIDIA vGPU software reserves can be
calculated from the following formula:
max-reserved-fb = vgpu-profile-size-in-mb÷16 + 16 + ecc-adjustments + page-retirement-
allocation + compression-adjustment

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 32
Known Product Limitations

max-reserved-fb
The maximum total amount of reserved frame buffer in Mbytes that is not available for
vGPUs.
vgpu-profile-size-in-mb
The amount of frame buffer in Mbytes allocated to a single vGPU. This amount
depends on the vGPU type. For example, for the T4-16Q vGPU type, vgpu-profile-size-
in-mb is 16384.
ecc-adjustments
The amount of frame buffer in Mbytes that is not usable by vGPUs when ECC is
enabled on a physical GPU that does not have HBM2 memory.

‣ If ECC is enabled on a physical GPU that does not have HBM2 memory ecc-
adjustments is fb-without-ecc/16, which is equivalent to 64 Mbytes for every Gbyte
of frame buffer assigned to the vGPU. fb-without-ecc is total amount of frame
buffer with ECC disabled.
‣ If ECC is disabled or the GPU has HBM2 memory, ecc-adjustments is 0.
page-retirement-allocation
The amount of frame buffer in Mbytes that is reserved for dynamic page retirement.

‣ On GPUs based on the NVIDIA Maxwell GPU architecture, page-retirement-

allocation = 4÷max-vgpus-per-gpu.
‣ On GPUs based on NVIDIA GPU architectures after the Maxwell architecture, page-
retirement-allocation = 128÷max-vgpus-per-gpu
max-vgpus-per-gpu
The maximum number of vGPUs that can be created simultaneously on a physical
GPU. This number varies according to the vGPU type. For example, for the T4-16Q
vGPU type, max-vgpus-per-gpu is 1.
compression-adjustment
The amount of frame buffer in Mbytes that is reserved for the higher compression
overhead in vGPU types with 12 Gbytes or more of frame buffer on GPUs based on the
Turing architecture.
compression-adjustment depends on the vGPU type as shown in the following table.
vGPU Type Compression Adjustment (MB)
T4-16Q 28

T4-16C
T4-16A

RTX6000-12Q 32

RTX6000-12C
RTX6000-12A

RTX6000-24Q 104

RTX6000-24C
RTX6000-24A

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 33
Known Product Limitations

vGPU Type Compression Adjustment (MB)

RTX6000P-12Q 32

RTX6000P-12C
RTX6000P-12A

RTX6000P-24Q 104

RTX6000P-24C
RTX6000P-24A

RTX8000-12Q 32

RTX8000-12C
RTX8000-12A

RTX8000-16Q 64

RTX8000-16C
RTX8000-16A

RTX8000-24Q 96

RTX8000-24C
RTX8000-24A

RTX8000-48Q 238

RTX8000-48C
RTX8000-48A

RTX8000P-12Q 32

RTX8000P-12C
RTX8000P-12A

RTX8000P-16Q 64

RTX8000P-16C
RTX8000P-16A

RTX8000P-24Q 96

RTX8000P-24C
RTX8000P-24A

RTX8000P-48Q 238

RTX8000P-48C
RTX8000P-48A

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 34
Known Product Limitations

For all other vGPU types, compression-adjustment is 0.

Note: In VMs running Windows Server 2012 R2, which supports Windows Display Driver
Model (WDDM) 1.x, an additional 48 Mbytes of frame buffer are reserved and not available
for vGPUs.

3.6. Issues may occur with graphics-

intensive OpenCL applications on
vGPU types with limited frame
buffer
Description
Issues may occur when graphics-intensive OpenCL applications are used with vGPU types
that have limited frame buffer. These issues occur when the applications demand more
frame buffer than is allocated to the vGPU.
For example, these issues may occur with the Adobe Photoshop and LuxMark OpenCL
Benchmark applications:

‣ When the image resolution and size are changed in Adobe Photoshop, a program error
may occur or Photoshop may display a message about a problem with the graphics
hardware and a suggestion to disable OpenCL.
‣ When the LuxMark OpenCL Benchmark application is run, XID error 31 may occur.

Workaround
For graphics-intensive OpenCL applications, use a vGPU type with more frame buffer.

3.7. In pass through mode, all GPUs

connected to each other through
NVLink must be assigned to the
same VM
Description
In pass through mode, all GPUs connected to each other through NVLink must be
assigned to the same VM. If a subset of GPUs connected to each other through NVLink is
passed through to a VM, unrecoverable error XID 74 occurs when the VM is booted. This

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 35
Known Product Limitations

error corrupts the NVLink state on the physical GPUs and, as a result, the NVLink bridge
between the GPUs is unusable.

Workaround
Restore the NVLink state on the physical GPUs by resetting the GPUs or rebooting the
hypervisor host.

3.8. 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 M10-0B
‣ Tesla M10-0Q

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

3.9. 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 M10-0B

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 36
Known Product Limitations

‣ Tesla M10-0Q

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

3.10. VM running an incompatible NVIDIA

vGPU guest driver fails to initialize
vGPU when booted
Description
A VM running a version of the NVIDIA guest VM driver that is incompatible with the
current release of Virtual GPU Manager will fail to initialize vGPU when booted on a
XenServer platform running that release of Virtual GPU Manager.
A guest VM driver is incompatible with the current release of Virtual GPU Manager in
either of the following situations:

‣ The guest driver is from a release in a branch two or more major releases before the
current release, for example release 9.4.
In this situation, the XenServer VM’s /var/log/messages log file reports the following
error:
vmiop_log: (0x0): Incompatible Guest/Host drivers: Guest VGX version is older
than the minimum version supported by the Host. Disabling vGPU.
‣ The guest driver is from a later release than the Virtual GPU Manager.
In this situation, the XenServer VM’s /var/log/messages log file reports the following
error:
vmiop_log: (0x0): Incompatible Guest/Host drivers: Guest VGX version is newer
than the maximum version supported by the Host. Disabling vGPU.

In either situation, 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)

Resolution
Install a release of the NVIDIA guest VM driver that is compatible with current release of
Virtual GPU Manager.

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 37
Known Product Limitations

3.11. 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 specifying
frame_rate_limiter=0 in the vGPU's plugin parameters.

‣ Citrix Hypervisor 8.1 or later: Specify frame_rate_limiter=0 in the extra_args

parameter for the group to which the vGPU belongs:
[root@xenserver ~]# xe vgpu-param-set uuid=vgpu-uuid extra_args=frame_rate_limiter=0
‣ Citrix Hypervisor earlier than 8.1: Specify frame_rate_limiter=0 in the VM’s
platform:vgpu_extra_args parameter:
[root@xenserver ~]# xe vm-param-set uuid=vm-uuid
platform:vgpu_extra_args="frame_rate_limiter=0"

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 FRL
can be reverted back to its default setting in one of the following ways:

‣ Removing the vGPU plugin's parameters:

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 38
Known Product Limitations

‣ Removing frame_rate_limiter=0 from the extra_args or vgpu_extra_args key

‣ Setting frame_rate_limiter=1. For example:
‣ Citrix Hypervisor 8.1 or later:
[root@xenserver ~]# xe vgpu-param-set uuid=vgpu-uuid
extra_args=frame_rate_limiter=1

‣ Citrix Hypervisor earlier than 8.1:

[root@xenserver ~]# xe vm-param-set uuid=vm-uuid
platform:vgpu_extra_args="frame_rate_limiter=1"

3.12. 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@xenserver-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 XenServer dom0.
To confirm that all GPUs are operating in pass-through mode, use XenCenter’s GPU tab to
review current GPU assignment:

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 39
Known Product Limitations

Resolution
N/A

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 40
Known Product Limitations

3.13. Windows Aero is disabled on Citrix

Virtual Apps and Desktops session
using 3 or 4 monitors in 2560×1600
resolution
Description
Windows Aero may be disabled when Citrix Virtual Apps and Desktops is connected to a
VM with a vGPU or passthrough GPU, with 3 or 4 monitors at 2560×1600 resolution.
This limitation is a limitation of Windows 7. For details, see the Microsoft knowledge base
article Desktop background disappears with very large extended desktop on Windows 7.

3.14. 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 vGPU 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)

When this error occurs, VGPU message failed messages and XID error messages are
written to the XenServer VM’s /var/log/messages log file.

Resolution
vGPU reserves a portion of the VM’s framebuffer for use in GPU mapping of VM system
memory. The reservation is sufficient to support up to 32GB of system memory, and may
be increased to accommodate up to 64GB by specifying enable_large_sys_mem=1 in the
vGPU's plugin parameters:

‣ Citrix Hypervisor 8.1 or later: Specify enable_large_sys_mem=1 in the extra_args

parameter for the group to which the vGPU belongs:
[root@xenserver ~]# xe vgpu-param-set uuid=vgpu-uuid extra_args=enable_large_sys_mem=1
‣ Citrix Hypervisor earlier than 8.1: Specify enable_large_sys_mem=1 in the VM’s
platform:vgpu_extra_args parameter:

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 41
Known Product Limitations

[root@xenserver ~]# xe vm-param-set uuid=vm-uuid

platform:vgpu_extra_args="enable_large_sys_mem=1"

The setting takes effect the next time the VM is started or rebooted. With this setting
in place, less GPU FB is available to applications running in the VM. To accommodate
system memory larger than 64GB, the reservation can be further increased by specifying
extra_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 of 64M is
sufficient to support 64GB of RAM. We recommend adding 2M of reservation for
each additional 1GB of system memory. For example, to support 96GB of RAM, set
extra_fb_reservation to 128:

‣ Citrix Hypervisor 8.1 or later:

extra_args="enable_large_sys_mem=1,extra_fb_reservation=128"
‣ Citrix Hypervisor earlier than 8.1:
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 plugin's parameters:

‣ Citrix Hypervisor 8.1 or later: Removing the extra_args key the from group to
which the vGPU belongs
‣ Citrix Hypervisor earlier than 8.1: Removing the vgpu_extra_args key from the
platform parameter
‣ Removing enable_large_sys_mem from the extra_args or vgpu_extra_args key
‣ Setting enable_large_sys_mem=0

3.15. vGPU host driver RPM upgrade fails

Description
Upgrading vGPU host driver RPM fails with an error message about failed dependencies
on the console.
[root@xenserver ~]# rpm –U NVIDIA-vGPU-xenserver-6.5-352.46.x86_64.rpm
error: Failed dependencies:
NVIDIA-vgx-xenserver conflicts with NVIDIA-vGPU-xenserver-6.5-352.46.x86_64
[root@xenserver ~]#

Resolution
Uninstall the older vGPU RPM before installing the latest driver.
Use the following command to uninstall the older vGPU RPM:
[root@xenserver ~]# rpm –e NVIDIA-vgx-xenserver

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 42
Chapter 4. Resolved Issues

Only resolved issues that have been previously noted as known issues or had a noticeable
user impact are listed. The summary and description for each resolved issue indicate the
effect of the issue on NVIDIA vGPU software before the issue was resolved.

4.1. Issues Resolved in Release 17.5

No resolved issues are reported in this release for XenServer.

4.2. Issues Resolved in Release 17.4

Bug ID Summary and Description
4621829 17.0-17.3 Only: vGPU manager is unstable or randomly crashes with GPUs
based on NVIDIA Ampere and later architectures

With GPUs based on the NVIDIA Ampere and later architectures, the
NVIDIA Virtual GPU Manager becomes unstable or randomly crashes.
When this issue occurs, all guest VMs on the hypervisor host that are
configured with NVIDIA vGPU crash. On Windows VMs, the crash is a
blue-screen crash with the bug check VIDEO_TDR_FAILURE and Timeout
Detection and Recovery (TDR) error 116.

4631262 17.0-17.3 Only: Blue screen crash occurs with Tesla M10 after only the
vGPU Manager is upgraded

If the NVIDIA vGPU Manager on a hypervisor host with a Tesla M10 GPU is
upgraded but the Windows guest VM driver is not upgraded, a blue screen
crash occurs.

4.3. Issues Resolved in Release 17.3

No resolved issues are reported in this release for XenServer.

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 43
Resolved Issues

4.4. Issues Resolved in Release 17.2

Bug ID Summary and Description
4558671 17.0, 17.1 Only: Disabling or disconnecting a display can cause a TDR on a
Windows vGPU VM

Disabling or disconnecting a display can cause a Timeout Detection and

Recovery (TDR) error on a Windows VM that is configured with NVIDIA
vGPU. The TDR error might cause a VM crash or intermittent black screens
with remoting solutions such as Omnissa Horizon. When this error occurs,
TDR error, XID error 44, and XID error 109 messages are written to the
log file on the hypervisor host.

3964376 17.0, 17.1 Only: Desktop is corrupted with XID errors 13 and 31 after
vGPU VM is migrated or suspended and resumed

When a vGPU VM is migrated or suspended and resumed, the remote

desktop session window is corrupted. XID error 13, XID error 31, or both
errors might also occur.

4600308 17.0, 17.1 Only: XID error 120 causes multiple issues with NVIDIA vGPU
on GPUs with a GSP

XID error 120 causes multiple issues with VMs configured with NVIDIA
vGPU on a physical GPU that includes a GPU System Processor (GSP), such
as GPUs based on the NVIDIA Ada Lovelace GPU architecture. Examples of
these issues include:

‣ VMs hang or crash.

‣ VMs fail to power on after hanging or a crashing.
‣ The hypervisor host crashes.

4644559 17.0, 17.1 Only: XID error 119 causes the hypervisor host to hang or crash
when multiple vGPU VMs are shut down

When multiple VMs configured with NVIDIA vGPU are shut down
simultaneously, XID error 119 causes the hypervisor host to hang or crash.
This issue affects VMs configured with NVIDIA vGPU on a physical GPU
that includes a GPU System Processor (GSP), such as GPUs based on the
NVIDIA Ada Lovelace GPU architecture.

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 44
Resolved Issues

4.5. Issues Resolved in Release 17.1

No resolved issues are reported in this release for XenServer.

4.6. Issues Resolved in Release 17.0

Bug ID Summary and Description
3973158 Pixelation occurs on a Windows VM configured with a Tesla T4 vGPU

Users might experience poor graphics quality on a Windows VM that is

configured with a vGPU on a Tesla T4 GPU. This issue can cause random
pixelation on the entire screen, or only on some patches of the screen. No
errors are reported or written to the log files when this issue occurs.

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 45
Chapter 5. Known Issues

5.1. 17.0-17.3 Only: vGPU manager is

unstable or randomly crashes with
GPUs based on NVIDIA Ampere and
later architectures
Description
With GPUs based on the NVIDIA Ampere and later architectures, the NVIDIA Virtual GPU
Manager becomes unstable or randomly crashes. When this issue occurs, all guest VMs
on the hypervisor host that are configured with NVIDIA vGPU crash. On Windows VMs,
the crash is a blue-screen crash with the bug check VIDEO_TDR_FAILURE and Timeout
Detection and Recovery (TDR) error 116.

Status
Resolved in NVIDIA vGPU software 17.4

Ref. #
4621829

5.2. CATIA performance is degraded

with large assembly visualization
Description
On Windows VMs configured with NVIDIA vGPU, the performance of the CATIA
application is degraded if the Optimize CGR for large assembly visualization setting is
enabled.

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 46
Known Issues

Workaround
In NVIDIA Control Panel, on the Manage 3D settings page, set Threaded optimization to
Off.

Status
Open

Ref. #
4480745

5.3. 17.0-17.3 Only: Blue screen crash

occurs with Tesla M10 after only
the vGPU Manager is upgraded
Description
If the NVIDIA vGPU Manager on a hypervisor host with a Tesla M10 GPU is upgraded but
the Windows guest VM driver is not upgraded, a blue screen crash occurs.

Version
This issue affects any Windows VM running a guest VM driver 16.x release on a
hypervisor host running an NVIDIA vGPU Manager 17.x release.

Workaround
Upgrade the guest VM driver to the driver from the same NVIDIA vGPU software release
as the NVIDIA vGPU Manager.

Status
Resolved in NVIDIA vGPU software 17.4

Ref. #
4631262

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 47
Known Issues

5.4. 17.0, 17.1 Only: Disabling or

disconnecting a display can cause a
TDR on a Windows vGPU VM
Description
Disabling or disconnecting a display can cause a Timeout Detection and Recovery (TDR)
error on a Windows VM that is configured with NVIDIA vGPU. The TDR error might cause a
VM crash or intermittent black screens with remoting solutions such as Omnissa Horizon.
When this error occurs, TDR error, XID error 44, and XID error 109 messages are
written to the log file on the hypervisor host.

Status
Resolved in NVIDIA vGPU software 17.2
After upgrading to a release in which this issue is resolved, you must set a registry key
value in the guest VM for the vGPU to avoid this issue.
1. Obtain the driver key of the vGPU.
a). In Device Manager, expand Display Device, context-click the vGPU and from the
menu that pops up, choose Properties.
b). In the Properties window that opens, click the Details tab and in the Property
drop-down list, select Driver key.
2. Open the Registry Editor and navigate to the Windows registry key Computer
\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\driver-key.
driver-key
The driver key for the vGPU that you got in the previous step, for example,
{4d36e968-e325-11ce-bfc1-08002be10318}\0001.
3. Add the R550_4558671 = 1 DWord (REG_DWORD) registry value.
4. Restart the guest VM to reload the graphics driver.

Ref. #
4558671

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 48
Known Issues

5.5. 17.0, 17.1 Only: XID error 120

causes multiple issues with NVIDIA
vGPU on GPUs with a GSP
Description
XID error 120 causes multiple issues with VMs configured with NVIDIA vGPU on a physical
GPU that includes a GPU System Processor (GSP), such as GPUs based on the NVIDIA Ada
Lovelace GPU architecture. Examples of these issues include:

‣ VMs hang or crash.

‣ VMs fail to power on after hanging or a crashing.
‣ The hypervisor host crashes.

Status
Resolved in NVIDIA vGPU software 17.2

Ref. #
4600308

5.6. 17.0, 17.1 Only: XID error 119

causes the hypervisor host to hang
or crash when multiple vGPU VMs
are shut down
Description
When multiple VMs configured with NVIDIA vGPU are shut down simultaneously, XID error
119 causes the hypervisor host to hang or crash. This issue affects VMs configured with
NVIDIA vGPU on a physical GPU that includes a GPU System Processor (GSP), such as
GPUs based on the NVIDIA Ada Lovelace GPU architecture.

Status
Resolved in NVIDIA vGPU software 17.2

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 49
Known Issues

Ref. #
4644559

5.7. 17.0, 17.1 Only: Desktop is

corrupted with XID errors 13 and
31 after vGPU VM is migrated or
suspended and resumed
Description
When a vGPU VM is migrated or suspended and resumed, the remote desktop session
window is corrupted. XID error 13, XID error 31, or both errors might also occur.
When this issue occurs, error messages similar to the following examples are written to
the log file on the hypervisor host:
Apr 8 11:27:28 smc220-0008 kernel: NVRM: Xid (PCI:0000:4b:00): 31, pid=6327,
name=nvidia-vgpu-mgr, Ch 00000701
...
Apr 8 11:27:29 smc220-0008 nvidia-vgpu-mgr[6327]: error: vmiop_log: (0x0): XID 31
detected on physical_chid:0x701, guest_chid:0x1
Apr 8 11:27:29 smc220-0008 nvidia-vgpu-mgr[6327]: error: vmiop_log: (0x0): MMU
Exception data for XID 31: addrLo 0x0, addHi 0x0, faultType 0 engineId 1

Status
Resolved in NVIDIA vGPU software 17.2

Ref. #
3964376

5.8. NVIDIA Control Panel is not

available in multiuser environments
Description
After the NVIDIA vGPU software graphics driver for Windows is installed, the NVIDIA
Control Panel app might be missing from the system. This issue typically occurs in the
following situations:

‣ Multiple users connect to virtual machines by using remote desktop applications such
as Microsoft RDP, Omnissa Horizon, and Citrix Virtual Apps and Desktops.

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 50
Known Issues

‣ VM instances are created by using Citrix Machine Creation Services (MCS) or VMware
Instant Clone technology.
‣ Roaming user desktop profiles are deployed.
This issue occurs because the NVIDIA Control Panel app is now distributed through the
Microsoft Store. The NVIDIA Control Panel app might fail to be installed when the NVIDIA
vGPU software graphics driver for Windows is installed if the Microsoft Store app is
disabled, the system is not connected to the Internet, or installation of apps from the
Microsoft Store is blocked by your system settings.
To determine whether the NVIDIA Control Panel app is installed on your system, use the
Windows Settings app or the Get-AppxPackage Windows PowerShell command.

‣ To use the Windows Settings app:

1. From the Windows Start menu, choose Settings > Apps > Apps & feautures .
2. In the Apps & features window, type nvidia control panel in the search box and
confirm that the NVIDIA Control Panel app is found.
‣ To use the Get-AppxPackageWindows PowerShell command:
1. Run Windows PowerShell as Administrator.
2. Determine whether the NVIDIA Control Panel app is installed for the current user.
PS C:\> Get-AppxPackage -Name NVIDIACorp.NVIDIAControlPanel
3. Determine whether the NVIDIA Control Panel app is installed for all users.
PS C:\> Get-AppxPackage -AllUsers -Name NVIDIACorp.NVIDIAControlPanel

This example shows that the NVIDIA Control Panel app is installed for the users
Administrator, pliny, and trajan.
PS C:\> Get-AppxPackage -AllUsers -Name NVIDIACorp.NVIDIAControlPanel

Name : NVIDIACorp.NVIDIAControlPanel
Publisher : CN=D6816951-877F-493B-B4EE-41AB9419C326
Architecture : X64
ResourceId :
Version : 8.1.964.0
PackageFullName :
NVIDIACorp.NVIDIAControlPanel_8.1.964.0_x64__56jybvy8sckqj
InstallLocation : C:\Program Files\WindowsApps
\NVIDIACorp.NVIDIAControlPanel_8.1.964.0_x64__56jybvy8sckqj
IsFramework : False
PackageFamilyName : NVIDIACorp.NVIDIAControlPanel_56jybvy8sckqj
PublisherId : 56jybvy8sckqj
PackageUserInformation :
{S-1-12-1-530092550-1307989247-1105462437-500 [Administrator]: Installed,

S-1-12-1-530092550-1307989247-1105462437-1002 [pliny]: Installed,

S-1-12-1-530092550-1307989247-1105462437-1003 [trajan]: Installed}

IsResourcePackage : False
IsBundle : False
IsDevelopmentMode : False
NonRemovable : False
IsPartiallyStaged : False
SignatureKind : Store
Status : Ok

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 51
Known Issues

Preventing this Issue

If your system does not allow the installation apps from the Microsoft Store, download
and run the standalone NVIDIA Control Panel installer that is available from NVIDIA
Licensing Portal. For instructions, refer to Virtual GPU Software User Guide.
If your system can allow the installation apps from the Microsoft Store, ensure that:

‣ The Microsoft Store app is enabled.

‣ Installation of Microsoft Store apps is not blocked by your system settings.
‣ No local or group policies are set to block Microsoft Store apps.

Workaround
If the NVIDIA Control Panel app is missing, install it separately from the graphics driver by
downloading and running the standalone NVIDIA Control Panel installer that is available
from NVIDIA Licensing Portal. For instructions, refer to Virtual GPU Software User Guide.
If the issue persists, contact NVIDIA Enterprise Support for further assistance.

Status
Open

Ref. #
3999308

5.9. NVIDIA Control Panel crashes if a

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

Version
This issue affects all supported Windows Server guest OS releases.

Status
Open

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 52
Known Issues

Ref. #
4086605

5.10. CUDA profilers cannot gather

hardware metrics on NVIDIA vGPU
Description
NVIDIA CUDA Toolkit profilers cannot gather hardware metrics on NVIDIA vGPU. This issue
affects only traces that gather hardware metrics. Other traces are not affected by this
issue and work normally.

Version
This issue affects NVIDIA vGPU software releases starting with 15.2.

Status
Open

Ref. #
4041169

5.11. NVIDIA vGPU software graphics

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

Workaround
Before running the NVIDIA vGPU software graphics driver installer, disable the remote call
to ngx.download.nvidia.com by setting the following Windows registry key:
[HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\NGXCore]

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 53
Known Issues

"EnableOTA"=dword:00000000

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

Status
Open

Ref. #
4031840

5.12. Multiple RDP session reconnections

on Windows Server 2022 can
consume all frame buffer
Description
Multiple RDP session reconnections in a Windows Server 2022 guest VM can consume
all the frame buffer of a vGPU or physical GPU. When this issue occurs, users' screens
becomes black, their sessions are disconnected but left intact, and they cannot log on
again. The following error message is written to the event log on the hypervisor host:
The Desktop Window Manager process has exited.
(Process exit code: 0xe0464645, Restart count: 1, Primary display device ID: )

Version
This issue affects only the Windows Server 2022 guest OS.

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

Status
Open

Ref. #
3583766

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 54
Known Issues

5.13. NLS client fails to acquire a license

with the error The allowed
time to process response has
expired
Description
A licensed client of NVIDIA License System (NLS) fails to acquire a license with the error
The allowed time to process response has expired. This error can affect clients of a
Cloud License Service (CLS) instance or a Delegated License Service (DLS) instance.
This error occurs when the time difference between the system clocks on the client and
the server that hosts the CLS or DLS instance is greater than 10 minutes. A common
cause of this error is the failure of either the client or the server to adjust its system
clock when daylight savings time begins or ends. The failure to acquire a license is
expected to prevent clock windback from causing licensing errors.

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

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

Status
Not a bug

Ref. #
3859889

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 55
Known Issues

5.14. With multiple active sessions,

NVIDIA Control Panel incorrectly
shows that the system is
unlicensed
Description
In an environment with multiple active desktop sessions, the Manage License page of
NVIDIA Control Panel shows that a licensed system is unlicensed. However, the nvidia-
smi command and the management interface of the NVIDIA vGPU software license server
correctly show that the system is licensed. When an active session is disconnected and
reconnected, the NVIDIA Display Container service crashes.
The Manage License page incorrectly shows that the system is unlicensed because of
stale data in NVIDIA Control Panel in an environment with multiple sessions. The data
is stale because NVIDIA Control Panel fails to get and update the settings for remote
sessions when multiple sessions or no sessions are active in the VM. The NVIDIA Display
Container service crashes when a session is reconnected because the session is not
active at the moment of reconnection.

Status
Open

Ref. #
3761243

5.15. VP9 and AV1 decoding with web

browsers are not supported on
Microsoft Windows Server 2019
Description
VP9 and AV1 decoding with web browsers are not supported on Microsoft Windows
Server 2019 and later supported releases. This issue occurs because starting with
Windows Server 2019, the required codecs are not included with the OS and are not
available through the Microsoft Store app. As a result, hardware decoding is not available

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 56
Known Issues

for viewing YouTube videos or using collaboration tools such as Google Meet in a web
browser.

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

Status
Not an NVIDIA bug

Ref. #
200756564

5.16. Ubuntu guest driver initialization

fails with vGPUs and GPUs that
support SR-IOV
Description
Initialization of the NVIDIA vGPU software graphics driver fails for Ubuntu guest VMs
configured with NVIDIA vGPUs or pass-through GPUs that support SR-IOV. An NVIDIA
vGPU that supports SR-IOV resides on a physical GPU that supports SR-IOV with NVIDIA
vGPU software, such as a GPU based on the NVIDIA Ampere architecture. This issue
affects only guest VMs running a version of the Ubuntu OS with kernel version 5.13 or
later, such as Ubuntu 20.04.
The failure of the driver to initialize is caused by an issue with extended Message Signaled
Interrupts (MSI-X). When this issue occurs, the following error message is written to the
kernel log file /var/log/kern.log in the guest VM:
RmInitAdapter failed!

Status
Open

Ref. #
3660894

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 57
Known Issues

5.17. nvidia-smi ignores the second

NVIDIA vGPU device added to a
Microsoft Windows Server 2016
VM
Description
After a second NVIDIA vGPU device is added to a Microsoft Windows Server 2016 VM, the
device does not appear in the output from the nvidia-smi command. This issue occurs
only if the VM is already running NVIDIA vGPU software for the existing NVIDIA vGPU
device when the second device is added to the VM.
The nvidia-smi command cannot retrieve the guest driver version, license status, and
accounting mode of the second NVIDIA vGPU device.
nvidia-smi vgpu --query
GPU 00000000:37:00.0
Active vGPUs : 1
vGPU ID : 3251695793
VM ID : 3575923
VM Name : SVR-Reg-W(P)-KuIn
vGPU Name : GRID V100D-32Q
vGPU Type : 185
vGPU UUID : 29097249-2359-11b2-8a5b-8e896866496b
Guest Driver Version : 551.78
License Status : Licensed
Accounting Mode : Disabled
...
GPU 00000000:86:00.0
Active vGPUs : 1
vGPU ID : 3251695797
VM ID : 3575923
VM Name : SVR-Reg-W(P)-KuIn
vGPU Name : GRID V100D-32Q
vGPU Type : 185
vGPU UUID : 2926dd83-2359-11b2-8b13-5f22f0f74801
Guest Driver Version : Not Available
License Status : N/A
Accounting Mode : N/A

Version
This issue affects only VMs that are running Microsoft Windows Server 2016 as a guest
OS.

Workaround
To avoid this issue, configure the guest VM with both NVIDIA vGPU devices before
installing the NVIDIA vGPU software graphics driver.

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 58
Known Issues

If you encounter this issue after the VM is configured, use one of the following
workarounds:

‣ Reinstall the NVIDIA vGPU software graphics driver.

‣ Forcibly uninstall the Microsoft Basic Display Adapter and reboot the VM.
‣ Upgrade the guest OS on the VM to Microsoft Windows Server 2019.

Status
Not an NVIDIA bug

Ref. #
3562801

5.18. After an upgrade of the Linux

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

Workaround
Perform a clean installation of the NVIDIA vGPU software graphics driver for Linux from
an RPM package.
1. Remove the currently installed driver.
2. Install the new version of the driver.
$ rpm -iv nvidia-linux-grid-550_550.144.03_amd64.rpm

Status
Open

Ref. #
3512766

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 59
Known Issues

5.19. After an upgrade of the Linux

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

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

‣ Reboot the VM.

‣ Remove the nvidia module from the Linux kernel and reinsert it into the kernel.
1. Remove the nvidia module from the Linux kernel.
$ sudo rmmod nvidia
2. Reinsert the nvidia module into the Linux kernel.
$ sudo modprobe nvidia

Status
Not a bug

Ref. #
200748806

5.20. Desktop session freezes when a

VM is migrated to or from a host
running an NVIDIA vGPU software
14 release
Description
When a VM configured with a Tesla V100 or Tesla T4 vGPU is migrated between a host
running an NVIDIA vGPU software 14 release and a host running a an NVIDIA vGPU

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 60
Known Issues

software 13 release, the remote desktop session freezes. After the session freezes, the
VM must be rebooted to recover the session. This issue occurs only when the NVIDIA
hardware-based H.264/HEVC video encoder (NVENC) is enabled.

Version
The issue affects migrations between a host running an NVIDIA vGPU software 14 release
and a host running an NVIDIA vGPU software 13 release.

Workaround
Disable NVENC.

Status
Open

Ref. #
3512790

5.21. The reported NVENC frame rate is

double the actual frame rate
Description
The frame rate in frames per second (FPS) for the NVIDIA hardware-based H.264/HEVC
video encoder (NVENC) reported by the nvidia-smi encodersessions command and
NVWMI is double the actual frame rate. Only the reported frame rate is incorrect. The
actual encoding of frames is not affected.
This issue affects only Windows VMs that are configured with NVIDIA vGPU.

Status
Open

Ref. #
2997564

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 61
Known Issues

5.22. Hypervisor host reboots

when multiple cloned VMs are
simultaneously powered on or
migrated
Description
When multiple cloned VMs are simultaneously powered on or migrated, the hypervisor
host reboots. No crash dump is generated and no error messages related to the reboot
are written to the log files daemon.log or kern.log.

Version
This issue affects only Citrix Hypervisor 8.2.

Status
Open

Ref. #
200726850

5.23. NVENC does not work with Teradici

Cloud Access Software on Windows
Description
The NVIDIA hardware-based H.264/HEVC video encoder (NVENC) does not work with
Teradici Cloud Access Software on Windows. This issue affects NVIDIA vGPU and GPU
pass through deployments.
This issue occurs because the check that Teradici Cloud Access Software performs on
the DLL signer name is case sensitive and NVIDIA recently changed the case of the
company name in the signature certificate.

Status
Not an NVIDIA bug

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 62
Known Issues

This issue is resolved in the latest 21.07 and 21.03 Teradici Cloud Access Software
releases.

Ref. #
200749065

5.24. A licensed client might fail to

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

Workaround
Perform this workaround on each affected licensed client.
1. Add the address of the NVIDIA vGPU software license server to the system
environment variable NO_PROXY.
The address must be specified exactly as it is specified in the client's license server
settings either as a fully-qualified domain name or an IP address. If the NO_PROXY
environment variable contains multiple entries, separate the entries with a comma (,).
If high availability is configured for the license server, add the addresses of the
primary license server and the secondary license server to the system environment
variable NO_PROXY.
2. Restart the NVIDIA driver service that runs the core NVIDIA vGPU software logic.

‣ On Windows, restart the NVIDIA Display Container service.

‣ On Linux, restart the nvidia-gridd service.

Status
Closed

Ref. #
200704733

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 63
Known Issues

5.25. Session connection fails with four

4K displays and NVENC enabled on
a 2Q, 3Q, or 4Q vGPU
Description
Desktop session connections fail for a 2Q, 3Q, or 4Q vGPU that is configured with four 4K
displays and for which the NVIDIA hardware-based H.264/HEVC video encoder (NVENC) is
enabled. This issue affects only Teradici Cloud Access Software sessions on Linux guest
VMs.
This issue is accompanied by the following error message:
This Desktop has no resources available or it has timed out

This issue is caused by insufficient frame buffer.

Workaround
Ensure that sufficient frame buffer is available for all the virtual displays that are
connected to a vGPU by changing the configuration in one of the following ways:

‣ Reducing the number of virtual displays. The number of 4K displays supported with
NVENC enabled depends on the vGPU.

vGPU 4K Displays Supported with NVENC Enabled

2Q 1
3Q 2
4Q 3
‣ Disabling NVENC. The number of 4K displays supported with NVENC disabled
depends on the vGPU.

vGPU 4K Displays Supported with NVENC Disabled

2Q 2
3Q 2
4Q 4
‣ Using a vGPU type with more frame buffer. Four 4K displays with NVENC enabled on
any Q-series vGPU with at least 6144 MB of frame buffer are supported.

Status
Not an NVIDIA bug

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 64
Known Issues

Ref. #
200701959

5.26. Disconnected sessions cannot

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

Workaround
Uninstall NVWMI.

Status
Open

Ref. #
3262923

5.27. Linux VM hangs after vGPU

migration to a host running a newer
vGPU manager version
Description
When a Linux VM configured with a Tesla V100 or Tesla T4 vGPU is migrated from a host
that is running a vGPU manager 11 release before 11.6 to a host that is running a vGPU
manager 13 release, the VM hangs. After the migration, the destination host and VM
become unstable. When this issue occurs, XID error 31 is written to the log files on the
destination hypervisor host.

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 65
Known Issues

Version
This issue affects migration from a host that is running a vGPU manager 11 release
before 11.6 to a host that is running a vGPU manager 13 release.

Workaround
If the VM is configured with a Tesla T4 vGPU, perform the following sequence of steps
before attempting the migration:
1. Upgrade the host that is running a vGPU manager 11 release to release 11.6 or a later
vGPU manager 11 release.
2. Disconnect any remoting tool that is using NVENC.

Note: You cannot use this workaround for a VM that is configured with a Tesla V100 vGPU.

Status
Open

Ref. #
200691445

5.28. Idle Teradici Cloud Access Software

session disconnects from Linux VM
Description
After a Teradici Cloud Access Software session has been idle for a short period of time,
the session disconnects from the VM. When this issue occurs, the error messages NVOS
status 0x19 and vGPU Message 21 failed are written to the log files on the hypervisor
host. This issue affects only Linux guest VMs.

Status
Open

Ref. #
200689126

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 66
Known Issues

5.29. No virtual GPU types are listed in

Citrix XenCenter
Description
No virtual GPU (vGPU) types are listed on the Select virtual GPU type drop-down list in
Citrix XenCenter. However, the command nvidia-smi vgpu -s lists all supported vGPU
types. This issue occurs because the driver version number of the Virtual GPU Manager
contains multiple decimal points and is misinterpreted by Citrix XenCenter.

Version
Citrix Hypervisor 8.2

Resolution
Apply Hotfix XS82E002 - For Citrix Hypervisor 8.2 from Citrix.

Status
Not an NVIDIA bug. Resolved by Citrix in hotfix XS82E002 for Citrix Hypervisor 8.2

Ref. #
200653755

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 67
Known Issues

5.30. NVIDIA vGPU software graphics

driver fails to load after upgrade on
XenServer
Description
NVIDIA vGPU software graphics driver fails to load after an upgrade of NVIDIA vGPU
software from an 11.x release to a 12.x release on XenServer. This issue occurs because
the hypervisor name in the RPM package name has changed from xenserver to
CitrixHypervisor.

The attempted upgrade fails its dependency checks as follows:

[root@localhost ~]# rpm -Uvh NVIDIA-vGPU-CitrixHypervisor-8.2-550.144.02.x86_64.rpm
error: Failed dependencies:
NVIDIA-vGPU-xenserver conflicts with NVIDIA-vGPU-
CitrixHypervisor-1:8.2-550.144.02.x86_64

Workaround
1. Determine the full name of the installed RPM package for the Virtual GPU Manager.
[root@localhost ~]# rpm -qa | grep NV
NVIDIA-vGPU-xenserver-8.2-535.183.04.x86_64
2. Remove the installed RPM package for the Virtual GPU Manager.
[root@localhost ~]# rpm -ev NVIDIA-vGPU-xenserver-8.2-535.183.04.x86_64
Preparing packages...
NVIDIA-vGPU-xenserver-1:8.2-535.183.04.x86_64
3. Perform a fresh installation of the latest RPM package for the Virtual GPU Manager.
[root@localhost ~]# rpm -ivh NVIDIA-vGPU-CitrixHypervisor-8.2-550.144.02.x86_64.rpm
Preparing... ################################# [100%]
Updating / installing...
1:NVIDIA-vGPU-CitrixHypervisor-1:8.################################# [100%]
4. Reboot the hypervisor host.
[root@localhost ~]# reboot

Status
Open

Ref. #
200682984

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 68
Known Issues

5.31. Windows guest VMs with vGPUs

or GPUs with large BAR memory
settings fail to boot to the desktop
in UEFI mode
Description
Windows guest VMs configured with vGPUs or physical GPUs that have large BAR
memory settings fail to boot to the desktop in UEFI mode. The VM can be reached
through its IP address but the desktop session is blank after the connection to the VM is
established.
By default, Citrix Hypervisor creates a VM in UEFI boot mode and the boot mode of a VM
cannot be changed after the VM is created.

Version
Citrix Hypervisor 8.2

Workaround
Delete the VM and re-create it, selecting BIOS Boot mode when you specify the
installation method for the OS software on the new VM.

Status
Open

Ref. #
200676622

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 69
Known Issues

5.32. Migrated VM with more than two

vGPUs crashes on destination host
Description
When a VM that is configured with more than two vGPUs is migrated, the VM crashes on
the destination host. When this issue occurs, the log file on the hypervisor host is flooded
with NVOS status messages 0x23, 0x33, 0x5, and 0x21 and vGPU failure messages 4, 6, 7,
9, 12, 14, 19, 21, 23, 26, 32, 43, 54, and 56.

Status
Open

Ref. #
200660221

5.33. Driver upgrade in a Linux guest VM

with multiple vGPUs might fail
Description
Upgrading the NVIDIA vGPU software graphics driver in a Linux guest VM with multiple
vGPUs might fail. This issue occurs if the driver is upgraded by overinstalling the new
release of the driver on the current release of the driver while the nvidia-gridd service is
running in the VM.

Workaround
1. Stop the nvidia-gridd service.
2. Try again to upgrade the driver.

Status
Open

Ref. #
200633548

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 70
Known Issues

5.34. NVIDIA Control Panel fails to start

if launched too soon from a VM
without licensing information
Description
If NVIDIA licensing information is not configured on the system, any attempt to start
NVIDIA Control Panel by right-clicking on the desktop within 30 seconds of the VM being
started fails.

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

Status
Open

Ref. #
200623179

5.35. VNC client session goes blank and

console VNC is corrupted when the
guest driver is uninstalled
Description
When the NVIDIA vGPU software graphics driver is uninstalled from a Windows 10 guest
VM for which the boot mode is UEFI, the VNC client session goes blank and console VNC
is corrupted.
This issue affects only Windows 10 guest VMs for which the boot mode is UEFI. It does
not affect Windows 10 guest VMs for which the boot mode is BIOS.

Workaround
Reboot the VM by using Citrix XenCenter.

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 71
Known Issues

Status
Not an NVIDIA bug

Ref. #
200609669

5.36. Citrix Virtual Apps and Desktops

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

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

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

Status
Not an NVIDIA bug

Ref. #
200608675

5.37. Suspend and resume between

hosts running different versions of
the vGPU manager fails
Description
Suspending a VM configured with vGPU on a host running one version of the vGPU
manager and resuming the VM on a host running a version from an older main release

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 72
Known Issues

branch fails. For example, suspending a VM on a host that is running the vGPU manager
from release 17.5 and resuming the VM on a host running the vGPU manager from
release 16.9 fails. When this issue occurs, the error There were no servers available
to complete the specified operation is reported on Citrix XenCenter.

Status
Not an NVIDIA bug

Ref. #
200602087

5.38. On Linux, the frame rate might

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

Workaround
1. If necessary, stop the Xorg server.
# /etc/init.d/xorg stop
2. In a plain text editor, edit the /etc/X11/xorg.conf file to set the options to disable
DPMS and disable the screen saver.
a). In the Monitor section, set the DPMS option to false.
Option "DPMS" "false"
b). At the end of the file, add a ServerFlags section that contains option to disable
the screen saver.
Section "ServerFlags"
Option "BlankTime" "0"
EndSection
c). Save your changes to /etc/X11/xorg.conf file and quit the editor.
3. Start the Xorg server.
# etc/init.d/xorg start

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 73
Known Issues

Status
Open

Ref. #
200605900

5.39. Citrix XenCenter displays

misleading information about vGPU
types
Description
The GPU type drop-down list in the Citrix XenCenter management GUI displays
misleading information about the maximum combined resolution supported by Q-series
and B-series vGPU types. The GUI lists the maximum number of displays supported
and the highest resolution supported in a manner that implies a maximum combined
resolution higher than is actually supported. These vGPU types support the number
of displays listed only at resolutions lower than the resolution listed and support the
resolution listed only with fewer displays than the number listed.
For example, as shown in the following screen capture, the GUI lists a resolution of
5120×2880 and four displays for the V100-1Q vGPU type. However, this vGPU type
supports only one display at a resolution of 5120×2880 and supports a maximum of four
displays only at resolutions of 2560×1600 and lower.

Version
All supported XenServer versions.

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 74
Known Issues

Workaround
For information about display configurations supported by Q-series and B-series vGPU
types, see Virtual GPU Software User Guide.

Status
Not an NVIDIA bug

Ref. #
200556224

5.40. Citrix Virtual Apps and Desktops

connection freezes initially
Description
When -0B and -0Q vGPU types are used with Citrix Virtual Apps and Desktops
version 7 1903 and later versions, the session freezes or a black screen is seen
when the connection is first made. When this issue occurs, the error message
DXGI_ERROR_DEVICE_REMOVED is displayed. The affected versions of Citrix Virtual Apps
and Desktops use Microsoft DDAPI.

Version
Citrix Virtual Apps and Desktops version 7 1903 and later versions

Workaround
Disable the use hardware encoding for video codec Citrix policy, which is enabled by
default.

Status
Open

Ref. #
200494400

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 75
Known Issues

5.41. DWM crashes randomly occur in

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

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

Status
Not an NVIDIA bug

Ref. #
2730037

5.42. NVIDIA Control Panel fails to

launch in a platform layer or
published image
Description
When NVIDIA vGPU software is used with Citrix App Layering and a platform layer for a
vGPU is being configured, NVIDIA Control Panel might fail to launch. The driver might be
working normally or it might fail with code 31 or code 43.
For more information and a workaround for this issue, see NVDIA Control Panel fails to
launch in platform layer or published image in the Citrix Support Knowledge Center.

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 76
Known Issues

5.43. Remote desktop session freezes

with assertion failure and XID error
43 after migration
Description
After multiple VMs configured with vGPU on a single hypervisor host are migrated
simultaneously, the remote desktop session freezes with an assertion failure and XID
error 43. This issue affects only GPUs that are based on the Volta GPU architecture. It
does not occur if only a single VM is migrated.
When this error occurs, the following error messages are logged to the XenServer log file
/var/log/messages:
Jan 3 14:35:48 ch81-m1 vgpu-12[8050]: error: vmiop_log: NVOS status 0x1f
Jan 3 14:35:48 ch81-m1 vgpu-12[8050]: error: vmiop_log: Assertion Failed at
0x4b8cacf6:286
...
Jan 3 14:35:59 ch81-m1 vgpu-12[8050]: error: vmiop_log: (0x0): XID 43 detected on
physical_chid:0x174, guest_chid:0x14

Status
Open

Ref. #
200581703

5.44. Citrix Virtual Apps and Desktops

session freezes when the desktop
is unlocked
Description
When a Citrix Virtual Apps and Desktops session that is locked is unlocked by pressing
Ctrl+Alt+Del, the session freezes. This issue affects only VMs that are running Microsoft
Windows 10 1809 as a guest OS.

Version
Microsoft Windows 10 1809 guest OS

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 77
Known Issues

Workaround
Restart the VM.

Status
Not an NVIDIA bug

Ref. #
2767012

5.45. NVIDIA vGPU software graphics

driver fails after Linux kernel
upgrade with DKMS enabled
Description
After the Linux kernel is upgraded (for example by running sudo apt full-upgrade) with
Dynamic Kernel Module Support (DKMS) enabled, the nvidia-smi command fails to run.
If DKMS is enabled, an upgrade to the Linux kernel triggers a rebuild of the NVIDIA vGPU
software graphics driver. The rebuild of the driver fails because the compiler version is
incorrect. Any attempt to reinstall the driver fails because the kernel fails to build.
When the failure occurs, the following messages are displayed:
-> Installing DKMS kernel module:
ERROR: Failed to run `/usr/sbin/dkms build -m nvidia -v 550.54.14 -k
5.3.0-28-generic`:
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area...
'make' -j8 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=5.3.0-28-generic
IGNORE_CC_MISMATCH='' modules...(bad exit status: 2)
ERROR (dkms apport): binary package for nvidia: 550.54.14 not found
Error! Bad return status for module build on kernel: 5.3.0-28-generic
(x86_64)
Consult /var/lib/dkms/nvidia/ 550.54.14/build/make.log for more information.
-> error.
ERROR: Failed to install the kernel module through DKMS. No kernel module
was installed;
please try installing again without DKMS, or check the DKMS logs for more
information.
ERROR: Installation has failed. Please see the file '/var/log/nvidia-
installer.log' for details.
You may find suggestions on fixing installation problems in the README
available on the Linux driver download page at www.nvidia.com.

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 78
Known Issues

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

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

Status
Not a bug.

Ref. #
2836271

5.46. On XenServer, all vGPUs in a VM

must be of the same type
Description
When a VM on XenServer is configured with multiple vGPUs, all vGPUs must be of the
same type. XenServer does not support the assignment multiple vGPUs of different
types to a single VM.
What happens when you try to assign a different type of vGPU than the vGPUs already
assigned to a VM depends on the Citrix utility that you are using.

‣ If you are using Citrix XenCenter, only vGPUs of the same type as the vGPUs already
assigned are available for selection.
‣ If you are using the xe command, the command fails and the following error message
is displayed:
Cannot create a virtual GPU that is incompatible with the existing types on the
VM.

Status
Not an NVIDIA bug.

Ref. #
200568154

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 79
Known Issues

5.47. Console VGA cannot be disabled

Description
In Citrix Hypervisor releases since 8.1, a VM's console VGA interface cannot
be disabled by using the command xe vm-param-set uuid=vm-uuid
platform:vgpu_extra_args="disable_vnc=1".

This behavior is the result of the following changes that Citrix introduced in XenServer
release 8.1:

‣ The command xe vm-param-set for assigning plugin configuration parameters has

been withdrawn.
‣ Plugin parameters can no longer be set for vGPUs that were created by using Citrix
XenCenter. They can be set only for vGPUs that were created from the command line
by using the xe command.

Version
Since Citrix Hypervisor release 8.1

Workaround
Create the vGPU by using the xe command and specify plugin parameters for the group
to which the vGPU belongs as explained in Virtual GPU Software User Guide.

Status
Not a bug

Ref. #
200569785

5.48. Console VNC is unusable with Xorg

on multiple vGPUs in a VM
Description
If a Linux VM is configured with multiple vGPUs and the Xorg display server is running on
more than one vGPU in the VM, severe corruption in console VNC is observed.

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 80
Known Issues

Workaround
Ensure that the Xorg display server is running on only one vGPU in the VM.

Status
Not an NVIDIA bug.

Ref. #
200568261

5.49. Migration of VMs configured with

vGPU stops before the migration is
complete
Description
When a VM configured with vGPU is migrated to another host, the migration stops before
it is complete. When this issue occurs, the message The VGPU is not compatible with
any PGPU in the destination. appears in the Citrix XenCenter management GUI.

This issue occurs if the ECC memory configuration (enabled or disabled) on the source
and destination hosts are different. The ECC memory configuration on both the source
and destination hosts must be identical.

Workaround
Before attempting to migrate the VM again, ensure that the ECC memory configuration
on both the source and destination hosts are identical.

Status
Not an NVIDIA bug

Ref. #
200520027

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 81
Known Issues

5.50. ECC memory settings for a vGPU

cannot be changed by using NVIDIA
X Server Settings
Description
The ECC memory settings for a vGPU cannot be changed from a Linux guest VM by
using NVIDIA X Server Settings. After the ECC memory state has been changed on
the ECC Settings page and the VM has been rebooted, the ECC memory state remains
unchanged.

Workaround
Use the nvidia-smi command in the guest VM to enable or disable ECC memory for the
vGPU as explained in Virtual GPU Software User Guide.
If the ECC memory state remains unchanged even after you use the nvidia-smi
command to change it, use the workaround in Changes to ECC memory settings for a
Linux vGPU VM by nvidia-smi might be ignored.

Status
Open

Ref. #
200523086

5.51. Changes to ECC memory settings

for a Linux vGPU VM by nvidia-smi
might be ignored
Description
After the ECC memory state for a Linux vGPU VM has been changed by using the
nvidia-smi command and the VM has been rebooted, the ECC memory state might
remain unchanged.
This issue occurs when multiple NVIDIA configuration files in the system cause the kernel
module option for setting the ECC memory state RMGuestECCState in /etc/modprobe.d/
nvidia.conf to be ignored.

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 82
Known Issues

When the nvidia-smi command is used to enable ECC memory, the file /etc/
modprobe.d/nvidia.conf is created or updated to set the kernel module option
RMGuestECCState. Another configuration file in /etc/modprobe.d/ that contains the
keyword NVreg_RegistryDwordsPerDevice might cause the kernel module option
RMGuestECCState to be ignored.

Workaround
This workaround requires administrator privileges.
1. Move the entry containing the keyword NVreg_RegistryDwordsPerDevice from the
other configuration file to /etc/modprobe.d/nvidia.conf.
2. Reboot the VM.

Status
Open

Ref. #
200505777

5.52. Incorrect GPU type shown for

Quadro RTX 8000 GPUs in Citrix
XenCenter
Description
On the GPU tab in Citrix XenCenter, Quadro RTX 8000 GPUs are incorrectly shown as
[QUADRO RTX 6000].

However, the virtual GPU types for a Quadro RTX 8000 GPU are listed correctly.
NVIDIA vGPU software does not support systems with a mixture of GPU types. Therefore,
you can assume that any GPU in a system that you know to contain Quadro RTX 8000
GPUs that is shown as [QUADRO RTX 6000] is, in fact, a Quadro RTX 8000 GPU.

Status
Not an NVIDIA bug

Ref. #
200492607

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 83
Known Issues

5.53. NVIDIA Notification Icon prevents

log off of Citrix Published
Application user sessions
Description
By default on Windows Server operating systems, the NVIDIA Notification Icon
application is started with every Citrix Published Application user session. This application
might prevent the Citrix Published Application user session from being logged off even
after the user has quit all other applications.

Resolution
Disable the NVIDIA Notification Icon application for Citrix Published Application user
sessions as explained in Virtual GPU Software User Guide.

Status
Resolved by the provision of Windows registry keys for disabling the NVIDIA Notification
Icon application for Citrix Published Application user sessions.

Ref. #
2206368

5.54. Host core CPU utilization is higher

than expected for moderate
workloads
Description
When GPU performance is being monitored, host core CPU utilization is higher than
expected for moderate workloads. For example, host CPU utilization when only a small
number of VMs are running is as high as when several times as many VMs are running.

Workaround
Disable monitoring of the following GPU performance statistics:

‣ vGPU engine usage by applications across multiple vGPUs

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 84
Known Issues

‣ Encoder session statistics

‣ Frame buffer capture (FBC) session statistics
‣ Statistics gathered by performance counters in guest VMs

Status
Open

Ref. #
2414897

5.55. Frame capture while the interactive

logon message is displayed returns
blank screen
Description
Because of a known limitation with NvFBC, a frame capture while the interactive logon
message is displayed returns a blank screen.
An NvFBC session can capture screen updates that occur after the session is created.
Before the logon message appears, there is no screen update after the message is shown
and, therefore, a black screen is returned instead. If the NvFBC session is created after
this update has occurred, NvFBC cannot get a frame to capture.

Workaround
See Black Screen at Logon with Nvidia HDX 3D Pro enabled in the Citrix knowledge base.

Status
Not a bug

Ref. #
2115733

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 85
Known Issues

5.56. RDS sessions do not use the GPU

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

Version
This issue affects all Windows Server releases that are supported as a guest OS.

Solution
Change the local computer policy to use the hardware graphics adapter for all RDS
sessions.
1. Choose Local Computer Policy > Computer Configuration > Administrative
Templates > Windows Components > Remote Desktop Services > Remote Desktop
Session Host > Remote Session Environment .
2. Set the Use the hardware default graphics adapter for all Remote Desktop Services
sessions option.

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

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 86
Known Issues

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

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

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 87
Known Issues

5.59. NVIDIA Control Panel Crashes in a

VM connected to two 4K displays
Description
When NVIDIA Control Panel is started in a VM connected through a pass-through GPU
to two 4K displays, a Citrix HDX 3D Pro Warning pop-up window opens containing the
following error message:
Full screen applications are not supported on Citrix HDX 3D Pro. Press Ok to exit

NVIDIA Control Panel then crashes.

After the VM is rebooted, NVIDIA Control Panel is available again.

Version
Citrix Virtual Apps and Desktops 7.16

Status
Not an NVIDIA bug

Ref. #
200393766

5.60. vGPU guest VM driver not properly

loaded on servers with more than
512 GB or 1 TB or more of system
memory
Description
If PV IOMMU is enabled, support for vGPU is limited to servers with a maximum of 512
GB of system memory. On servers with more than 512 GB of system memory and PV
IOMMU enabled, the guest VM driver is not properly loaded. Device Manager marks the
vGPU with a yellow exclamation point.
If PV IOMMU is disabled, support for vGPU is limited to servers with less than 1 TB of
system memory. This limitation applies only to systems with supported GPUs based on
the Maxwell architecture, namely, Tesla M10. On servers with 1 TB or more of system

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 88
Known Issues

memory, VMs configured with vGPU fail to power on. However, support for GPU pass
through is not affected by this limitation.

Resolution
1. If PV IOMMU is enabled, disable it.
[root@xenserver ~]# /opt/xensource/libexec/xen-cmdline --set-xen iommu=dom0-passthrough
2. If the server has 1 TB or more of system memory, limit the amount of system memory
on the server to 1 TB minus 16 GB.
If the server has less than 1 TB or more of system memory, omit this step.
3. Reboot the server.

Status
Not an NVIDIA bug

Ref. #
1799582

5.61. Luxmark causes a segmentation

fault on an unlicensed Linux client
Description
If the Luxmark application is run on a Linux guest VM configured with NVIDIA vGPU that
is booted without acquiring a license, a segmentation fault occurs and the application
core dumps. The fault occurs when the application cannot allocate a CUDA object on
NVIDIA vGPUs where CUDA is disabled. On NVIDIA vGPUs that can support CUDA, CUDA
is disabled in unlicensed mode.

Status
Not an NVIDIA bug.

Ref. #
200330956

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 89
Known Issues

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

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 90
Known Issues

5.63. No Manage License option available

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

Workaround
This workaround requires sudo privileges.

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

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

1. If NVIDIA X Server Settings is running, shut it down.

2. If the /etc/nvidia/gridd.conf file does not already exist, create it by copying the
supplied template file /etc/nvidia/gridd.conf.template.
3. As root, edit the /etc/nvidia/gridd.conf file to set the EnableUI option to TRUE.
4. Start the nvidia-gridd service.
# sudo service nvidia-gridd start

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

Status
Open

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 91
Known Issues

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

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

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 92
Known Issues

‣ 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 Virtual Apps and Desktops or Omnissa
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.
When memory exhaustion occurs, the NVIDIA host driver reports Xid error 31 and Xid
error 43 in the XenServer /var/log/messages file.
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:
‣ 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 using
Windows 10 in virtual environments, complete the NVIDIA GRID vGPU Profile Sizing
Guide for Windows 10 download request form.
For more information, see also Windows 10 Optimization for XenDesktop on the
Citrix blog.

Status
Open

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 93
Known Issues

Ref. #
‣ 200130864
‣ 1803861

5.66. VM bug checks after the guest

VM driver for Windows 10 RS2 is
installed
Description
When the VM is rebooted after the guest VM driver for Windows 10 RS2 is installed, the
VM bug checks. When Windows boots, it selects one of the standard supported video
modes. If Windows is booted directly with a display that is driven by an NVIDIA driver, for
example a vGPU on XenServer, a blue screen crash occurs.
This issue occurs when the screen resolution is switched from VGA mode to a resolution
that is higher than 1920×1200.

Fix
Download and install Microsoft Windows Update KB4020102 from the Microsoft Update
Catalog.

Workaround
If you have applied the fix, ignore this workaround.
Otherwise, you can work around this issue until you are able to apply the fix by not using
resolutions higher than 1920×1200.
1. Choose a GPU profile in Citrix XenCenter that does not allow resolutions higher than
1920×1200.
2. Before rebooting the VM, set the display resolution to 1920×1200 or lower.

Status
Not an NVIDIA bug

Ref. #
200310861

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 94
Known Issues

5.67. On XenServer 7.0, VMs

unexpectedly reboot and XenServer
crashes or freezes
Description
On XenServer 7.0, VMs to which a vGPU is attached unexpectedly reboot and XenServer
crashes or freezes.
The event log in the XenServer /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 installed
‣ A fatal error on a component at bus 0, device 2, function 0
This issue occurs when page-modification logging (PML) is enabled on Intel Broadwell
CPUs running XenServer 7.0. Citrix is aware of this issue and is working on a permanent
fix.

Workaround
Disable page-modification logging (PML) as explained in XenServer 7 host crash while
starting multiple virtual machines in the Citrix Support Knowledge Center.

Status
Not an NVIDIA bug

Ref. #
1853248

5.68. With no NVIDIA driver installed,

XenServer misidentifies Tesla M10
cards
Description
An erroneous entry in the pci.ids database causes XenServer to identify Tesla M10
cards as GRID M40 when no NVIDIA driver is installed.

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 95
Known Issues

Version
XenServer 6.5 and 7.0

Workaround
None

Status
Not an NVIDIA bug

Ref. #
NVIDIA-420/1792341

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

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 96
Known Issues

5.70. Video goes blank when run in loop

in Windows Media Player
Description
When connected to a vGPU-enabled VM using Citrix Virtual Apps and Desktops, a video
played back in looping mode on Windows Media Player goes blank or freezes after a few
iterations.

Workaround
None

Status
Not an NVIDIA bug

Ref. #
1306623

5.71. Local VGA console is momentarily

unblanked when Citrix Virtual Apps
and Desktops changes resolution
of the VM desktop
Description
When Citrix Virtual Apps and Desktops establishes a remote connection to a VM using
vGPU, the VM’s local VGA console display in XenCenter is blanked (assuming the VM
local console has not been disabled by setting disable_vnc=1 in the vGPU plugin's
parameters). If the Citrix Virtual Apps and Desktops session changes resolution of the
VM’s desktop, the local VGA console momentarily unblanks, allowing a XenCenter user to
briefly view the desktop.

Workaround
Disable the VM’s local VGA console.

‣ Citrix Hypervisor 8.1 or later:

[root@xenserver ~]# xe vgpu-param-set uuid=vgpu-uuid extra_args=disable_vnc=1

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 97
Known Issues

‣ Citrix Hypervisor earlier than 8.1:

xe vm-param-set uuid=vm-uuid platform:vgpu_extra_args="disable_vnc=1"

Status
Open

Ref. #
NVIDIA-145/1375164

5.72. VM bugchecks on shutdown/

restart when Citrix Virtual Apps and
Desktops is installed and NVIDIA
driver is uninstalled or upgraded.
Description
If the Citrix Virtual Apps and Desktops agent is installed in a VM before any
NVIDIA GPU driver is installed, the VM will bugcheck (bluescreen) when the NVIDIA
driver is subsequently upgraded or uninstalled. The bugcheck code is 0x7E,
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED.

Workaround
Use one of the following workarounds:

‣ Do a force shutdown of the VM and restart it.

‣ Install the NVIDIA driver in guest VMs before installing Citrix Virtual Apps and
Desktops.

Status
Open

Ref. #
NVIDIA-295/200018125

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 98
Known Issues

5.73. Application frame rate may drop

when running Citrix Virtual Apps
and Desktops at 2560×1600
resolution.
Description
An application’s rendering frame rate may drop when running Citrix Virtual Apps
and Desktops at 2560×1600 resolution, relative to the frame rate obtained at lower
resolutions.

Fix
Using the Windows regedit utility within the VM, open the HKLM\SOFTWARE\Citrix
\Graphics registry key and create a new DWORD value, EncodeSpeed, with a value of 2.
Reboot the VM. This setting may improve the delivered frame rate at the expense of a
reduction in image quality.

Status
Open

Ref. #
NVIDIA-190/1416336

5.74. Windows VM BSOD

Description
Windows VM bugchecks on XenServer when running a large number of vGPU based VMs.
The XenServer /var/log/messages file contains these error messages:
NVRM: Xid (PCI:0000:08:00): 31, Ch 0000001e, engmask 00000111, intr 10000000
NVRM: Xid (PCI:0000:08:00): 31, Ch 00000016, engmask 00000111, intr 10000000
...
vmiop_log: error: Assertion Failed at 0xb5b898d8:4184
vmiop_log: error: 8 frames returned by backtrace
vmiop_log: error: /usr/lib/libnvidia-vgx.so(_nv000793vgx+0x69d) [0xb5b8064d]
vmiop_log: error: /usr/lib/libnvidia-vgx.so(_nv000479vgx+0x118) [0xb5b898d8]
vmiop_log: error: /usr/lib/libnvidia-vgx.so(_nv000782vgx+0x59) [0xb5b85f49]
vmiop_log: error: /usr/lib/libnvidia-vgx.so(_nv000347vgx+0x3db) [0xb5b932db]
vmiop_log: error: /usr/lib/libnvidia-vgx.so [0xb5b78e4a]
vmiop_log: error: /usr/lib/xen/bin/vgpu [0x80554be]
vmiop_log: error: /lib/libpthread.so.0 [0xb7612912]

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 99
Known Issues

vmiop_log: error: /lib/libc.so.6(clone+0x5e) [0xb76fc5ee]

vmiop_log: error: failed to initialize guest PTE entries
vmiop_log: error: failed to fill up guest PTE entries 3
vmiop_log: error: VGPU message 27 failed, result code: 0xff000003
vmiop_log: error: 0xc1d00001, 0xff010000, 0x1a77ba000, 0x0, 0x1,
vmiop_log: error: 0x1, 0x1000, 0x10202, 0xc1d00001, 0xff010000,
vmiop_log: error: 0xcaf00004, 0x0
vmiop_log: error: Timeout occurred, reset initiated.

Version
XenServer 6.2

Fix
Ensure that you are running the latest OEM firmware for your NVIDIA vGPU software
boards.

Status
Closed

Ref. #
NVIDIA-327/1632120

5.75. Windows VM BSOD when

upgrading NVIDIA drivers over a
Citrix Virtual Apps and Desktops
session
Description
Windows VM bugchecks when NVIDIA guest drivers are upgraded over a Citrix Virtual
Apps and Desktops session.
If the VM is restarted after the bugcheck, the upgraded driver loads correctly and full
functionality is available.

Fix
Upgrade Citrix Virtual Apps and Desktops to 7.6 Feature Pack 3

Status
Closed

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 100
Known Issues

Ref. #
NVIDIA-370/200130780

5.76. XenCenter does not allow vGPUs to

be selected as a GPU type for Linux
VMs
Description
When creating a new Linux VM or editing the properties of an existing Linux VM,
XenCenter does not allow vGPUs to be selected as a GPU type.
vGPU on Linux VMs is supported as a technical preview on XenServer 6.5, and does
include XenCenter integration.

Version
Affects the XenCenter integration with XenServer 6.5 only.
Resolved in the XenCenter integration with XenServer 7.0.

Workaround
Refer to XenServer vGPU Management in Virtual GPU Software User Guide for how to
configure vGPU by using the xe CLI.

Status
Closed

Ref. #
NVIDIA-360

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 101
Known Issues

5.77. If X server is killed on a RHEL7 VM

running vGPU, XenCenter console
may not automatically switch to
text console
Description
If X server is killed on a RHEL7 VM running vGPU, XenCenter console may display a
corrupted image and fail to switchover to text console.
The failure to switchover to text console is due to a bug in RHEL7, which causes X server
to not start correctly under certain configurations.

Workaround
Use CTRL+ALT+F1, F2, or F3 to switch between Linux terminals.

Status
Closed

Ref. #
NVIDIA-350/200123378

5.78. Citrix Virtual Apps and Desktops

shows only a black screen when
connected to a vGPU VM
Description
Citrix Virtual Apps and Desktops sometimes displays only a black screen when it
is connected to an NVIDIA vGPU VM. The probable cause is that the display that is
connected to the NVIDIA vGPU is entering a lower power state.

Fix
Disable all display-related power management settings.

Virtual GPU Software R550 for XenServer RN-06927-001 _v17.0 through 17.5 | 102
Known Issues

For detailed instructions, visit Microsoft power plans frequently asked questions and
from the list, select your OS version.

Status
Not an NVIDIA bug

Ref. #
1719877

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

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

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

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

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

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

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

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

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

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

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

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

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

NVIDIA Corporation | 2788 San Tomas Expressway, Santa Clara, CA 95051

http://www.nvidia.com

nvidia-ai-enterprise-user-guide
No ratings yet
nvidia-ai-enterprise-user-guide
100 pages
470.223.02 474.64 Grid Vgpu Release Notes Ubuntu
No ratings yet
470.223.02 474.64 Grid Vgpu Release Notes Ubuntu
63 pages
470.223.02 474.64 Grid Software Quick Start Guide
No ratings yet
470.223.02 474.64 Grid Software Quick Start Guide
55 pages
Grid Vgpu User Guide
No ratings yet
Grid Vgpu User Guide
261 pages
470.223.02 474.64 Grid Licensing User Guide
No ratings yet
470.223.02 474.64 Grid Licensing User Guide
39 pages
nvidia-ai-enterprise-release-notes
No ratings yet
nvidia-ai-enterprise-release-notes
46 pages
418.109 426.26 Grid Vgpu Release Notes Vmware Vsphere
No ratings yet
418.109 426.26 Grid Vgpu Release Notes Vmware Vsphere
60 pages
470.223.02-474.64-whats-new-vgpu
No ratings yet
470.223.02-474.64-whats-new-vgpu
10 pages
470.129.04-470.129.06-473.47-grid-licensing-user-guide
No ratings yet
470.129.04-470.129.06-473.47-grid-licensing-user-guide
40 pages
367.134 370.41 Grid Vgpu Release Notes Vmware Vsphere
No ratings yet
367.134 370.41 Grid Vgpu Release Notes Vmware Vsphere
32 pages
NVIDIA Virtual GPU Packaging and Licensing Guide
No ratings yet
NVIDIA Virtual GPU Packaging and Licensing Guide
16 pages
572.16-win11-win10-release-notes
No ratings yet
572.16-win11-win10-release-notes
38 pages
Vgpu Deployment Guide Horizon On Vsphere Final
No ratings yet
Vgpu Deployment Guide Horizon On Vsphere Final
277 pages
grid-software-quick-start-guide
No ratings yet
grid-software-quick-start-guide
39 pages
390.94 390.96 392.05 Grid License Server User Guide
No ratings yet
390.94 390.96 392.05 Grid License Server User Guide
58 pages
ASRock Z77 Extreme4 User Manual
No ratings yet
ASRock Z77 Extreme4 User Manual
79 pages
418.109 426.26 Grid Licensing User Guide
No ratings yet
418.109 426.26 Grid Licensing User Guide
31 pages
grid-vgpu-user-guide
No ratings yet
grid-vgpu-user-guide
314 pages
Virtual GPU Packaging and Licensing Guide
No ratings yet
Virtual GPU Packaging and Licensing Guide
22 pages
LDAT v2 User Guide 2.1
No ratings yet
LDAT v2 User Guide 2.1
69 pages
Nvidia Certified Systems
No ratings yet
Nvidia Certified Systems
25 pages
grid-license-server-release-notes
No ratings yet
grid-license-server-release-notes
21 pages
Tech-Brief-Virtual-GPU-Positioning
No ratings yet
Tech-Brief-Virtual-GPU-Positioning
26 pages
Grid Vgpu User Guide
No ratings yet
Grid Vgpu User Guide
74 pages
418.109 426.26 Grid Vgpu User Guide
No ratings yet
418.109 426.26 Grid Vgpu User Guide
164 pages
Grid Vgpu User Guide
No ratings yet
Grid Vgpu User Guide
289 pages
Nvidia Virtual PC Best Practices
No ratings yet
Nvidia Virtual PC Best Practices
17 pages
NVIDIA License Server Installation Driver Installation On Host Guest 1
No ratings yet
NVIDIA License Server Installation Driver Installation On Host Guest 1
19 pages
h19568-vdi-vsan-horizon-design-guide
No ratings yet
h19568-vdi-vsan-horizon-design-guide
38 pages
Parallels RAS GPU Accelerated Application Publishing
No ratings yet
Parallels RAS GPU Accelerated Application Publishing
42 pages
Configuring Xenserver 7.0 For Graphics May 2016
No ratings yet
Configuring Xenserver 7.0 For Graphics May 2016
21 pages
CitrixVmware GPU Deployment Guide TechPub v02d6 Final
No ratings yet
CitrixVmware GPU Deployment Guide TechPub v02d6 Final
302 pages
vGPU Wiki
No ratings yet
vGPU Wiki
24 pages
16G PowerEdge Data Processing Unit (DPU) - Features - Participant Guide
No ratings yet
16G PowerEdge Data Processing Unit (DPU) - Features - Participant Guide
65 pages
418.109 426.26 Whats New Vgpu
No ratings yet
418.109 426.26 Whats New Vgpu
6 pages
474.82 Win11 Win10 Release Notes
No ratings yet
474.82 Win11 Win10 Release Notes
24 pages
Deprecation Notices
No ratings yet
Deprecation Notices
5 pages
418.109 426.26 Grid Software Quick Start Guide
No ratings yet
418.109 426.26 Grid Software Quick Start Guide
40 pages
Cuda Compiler Driver NVCC: Reference Guide
No ratings yet
Cuda Compiler Driver NVCC: Reference Guide
43 pages
nvidia-quadro-virtual-data-center-workstation-solution-overview
No ratings yet
nvidia-quadro-virtual-data-center-workstation-solution-overview
4 pages
Philips Advance Visualization Workspace 15
100% (1)
Philips Advance Visualization Workspace 15
16 pages
Real-Time Weapons Detection System Using Computer Vision
No ratings yet
Real-Time Weapons Detection System Using Computer Vision
6 pages
Dell Emc Poweredge Servers With Nvidia Gpus and Vmware Vsphere
No ratings yet
Dell Emc Poweredge Servers With Nvidia Gpus and Vmware Vsphere
17 pages
Nvidia Virtual PC Virtual Apps Solution Overview
No ratings yet
Nvidia Virtual PC Virtual Apps Solution Overview
4 pages
Installation Guide
No ratings yet
Installation Guide
14 pages
HPE ProLiant DL365 Gen11 Quickspecs
No ratings yet
HPE ProLiant DL365 Gen11 Quickspecs
50 pages
Installation Guide
No ratings yet
Installation Guide
11 pages
367.134 370.41 Grid Vgpu User Guide
No ratings yet
367.134 370.41 Grid Vgpu User Guide
99 pages
Technical Brief Gpu Positioning Virtualized Compute and Graphics Workloads
No ratings yet
Technical Brief Gpu Positioning Virtualized Compute and Graphics Workloads
32 pages
NVIDIA vGPU and VMware Horizon - End User Computing Platform - 16321790742700010mPB
No ratings yet
NVIDIA vGPU and VMware Horizon - End User Computing Platform - 16321790742700010mPB
2 pages
Lastexception 63794637034
No ratings yet
Lastexception 63794637034
37 pages
Vgpu For Oil and Gas Brochure
No ratings yet
Vgpu For Oil and Gas Brochure
6 pages
API Reference: v11.7 August 2022
No ratings yet
API Reference: v11.7 August 2022
4 pages
Client 3 - Tech Symposia - Heterogeneous AI On Arm (Taiwan Version v2)
No ratings yet
Client 3 - Tech Symposia - Heterogeneous AI On Arm (Taiwan Version v2)
27 pages
Vmware Nvidia Grid Vgpu Faq
No ratings yet
Vmware Nvidia Grid Vgpu Faq
4 pages
Reviewers Guide Remote 3d Graphics Apps Part 3 Xenserver Vgpu
No ratings yet
Reviewers Guide Remote 3d Graphics Apps Part 3 Xenserver Vgpu
47 pages
NVIDIA CUDA Programming Guide 2.0
100% (3)
NVIDIA CUDA Programming Guide 2.0
107 pages
Cramming: Training A Language Model On A Single GPU in One Day (2022)
No ratings yet
Cramming: Training A Language Model On A Single GPU in One Day (2022)
27 pages
Vgpu Aec Brochure
No ratings yet
Vgpu Aec Brochure
6 pages
NVIDIA Virtual GPU Software QuickSpecs
No ratings yet
NVIDIA Virtual GPU Software QuickSpecs
12 pages
Particle Picking - RELION Documentation
No ratings yet
Particle Picking - RELION Documentation
19 pages
Paper 2
No ratings yet
Paper 2
13 pages
Bringing Digital Repair Manuals To The Shop Floor
No ratings yet
Bringing Digital Repair Manuals To The Shop Floor
2 pages
NVIDIA Driver Installation Quickstart
No ratings yet
NVIDIA Driver Installation Quickstart
6 pages
How to Add GPU to Syno DS1820+
No ratings yet
How to Add GPU to Syno DS1820+
6 pages
GPU Bootcamp Samhar
100% (1)
GPU Bootcamp Samhar
96 pages
Quadro Power Guidelines 4
No ratings yet
Quadro Power Guidelines 4
19 pages
Pitching TEM
No ratings yet
Pitching TEM
14 pages
Ansys191 Remote Display Virtual Desktop Support
No ratings yet
Ansys191 Remote Display Virtual Desktop Support
1 page
NVIDIA Data Center GPU Driver Release Notes 470 v3.0
No ratings yet
NVIDIA Data Center GPU Driver Release Notes 470 v3.0
14 pages
CPH Lab Manual
No ratings yet
CPH Lab Manual
14 pages
3dsmax 2023 05 May 2023
No ratings yet
3dsmax 2023 05 May 2023
10 pages
Nvidia Professional Graphics Solutions: Nvidia Laptop Gpus Nvidia Desktop Workstations Gpus Nvidia Servers Gpus
No ratings yet
Nvidia Professional Graphics Solutions: Nvidia Laptop Gpus Nvidia Desktop Workstations Gpus Nvidia Servers Gpus
2 pages
A13 Bionic Chip
No ratings yet
A13 Bionic Chip
12 pages
NCA-AIIO AI Infrastructure and Operations Practice Questions
No ratings yet
NCA-AIIO AI Infrastructure and Operations Practice Questions
12 pages
Optiplex 780 Tech Guide
No ratings yet
Optiplex 780 Tech Guide
49 pages
CS 179: GPU Computing: Recitation 1 - 4/1/16
No ratings yet
CS 179: GPU Computing: Recitation 1 - 4/1/16
18 pages
Nvidia Lawsuit
No ratings yet
Nvidia Lawsuit
18 pages
Nvidia Virtual GPU Packaging
No ratings yet
Nvidia Virtual GPU Packaging
22 pages
Ds SeMSy Compact en
No ratings yet
Ds SeMSy Compact en
3 pages
Vmware Nvidia Presentation
No ratings yet
Vmware Nvidia Presentation
38 pages
Hp Victus 15 Fa1082wm
No ratings yet
Hp Victus 15 Fa1082wm
1 page
VGA Bios Collection Sapphire RX 470 8 GB TechPowerUp
No ratings yet
VGA Bios Collection Sapphire RX 470 8 GB TechPowerUp
1 page
Graphics #Flushyourmeds Scott Barry
No ratings yet
Graphics #Flushyourmeds Scott Barry
3 pages
MIDAS
No ratings yet
MIDAS
4 pages
Fde AI
No ratings yet
Fde AI
2 pages
Thief of Thieves - Season One Free Download (v1.2.0) IGGGAMES
No ratings yet
Thief of Thieves - Season One Free Download (v1.2.0) IGGGAMES
6 pages
Gray Hat Hacking the Ethical Hacker's
From Everand
Gray Hat Hacking the Ethical Hacker's
Çağatay Şanlı
5/5 (1)
A To Z of Internet: Everything You Wanted to Know
From Everand
A To Z of Internet: Everything You Wanted to Know
Bittu Kumar
No ratings yet
Content Creation Revolution with chatGPT
From Everand
Content Creation Revolution with chatGPT
Maria Cowen
No ratings yet