Provisioning vGPU-enabled Citrix Virtual Apps and Desktop machines
Citrix Hypervisor/ESX hypervisor supports NVIDIA virtual GPU (vGPU) solutions that consist of NVIDIA data center GPUs and vGPU software licensing components. The underlying data center GPUs in the Citrix Hypervisor host is unknown to Citrix Provisioning. Citrix Provisioning only uses the vGPU software settings in the template and propagates it to the VMs provisioned by the Citrix Virtual Apps and Desktops Setup Wizard.
Requirements
- An NVIDIA vGPU certified server capable of hosting Citrix Hypervisor and NVIDIA vGPU software.
- Supported hypervisors: Nutanix AHV, Citrix XenServer 6.2 or newer, or vSphere 6.0 or newer.
- NVIDIA vGPU software: NVIDIA vApps, vPC or RTX Virtual Workstation.
- NVIDIA drivers: NVIDIA Graphics Driver or NVIDIA RTX Enterprise Driver.
- The Citrix Provisioning release that corresponds to the Citrix Virtual Apps and Desktops release you are using. The Citrix Virtual Apps and Desktops Setup Wizard only supports the corresponding Citrix Virtual Apps and Desktops controller.
- To provision machines using the Citrix Virtual Apps and Desktops Setup Wizard, you must use Citrix Provisioning 1912 LTSR or later.
Note:
Citrix Virtual Apps and Desktops supports power management for virtual machine (VM) catalogs, but not for physical machine catalogs.
Provisioning procedures
Prepare the master VM
- Prepare the master VM with vGPU enabled.
- Install the NVIDIA drivers.
- Join the machine operating system to Active Directory.
- Install the Citrix Provisioning target device software.
- Using the Citrix Provisioning Imaging Wizard, create a master virtual disk image. If you plan to use the Citrix Virtual Apps and Desktops Setup Wizard to provision machines, select the Target Device Optimizer option.
- Create a template from the master to use during provisioning, using the CVAD Setup Wizard.
Prepare the template VM
Use the information in this section to set up a template VM for provisioned targets. When preparing the template VM, consider:
- the template uses an attached write cache. This cache is small, approximately 8–16 MB, and can be used for environments requiring a workaround for the SAN policy method.
- the write cache can also be used in environments applying the UseTemplateCache method.
- the attached disk ensures that the provisioned target device recognizes the storage controller.
- booting a VM is a verification process ensuring that the VM used as a template functions with the virtual disk. If the template VM does not boot, the failure is recognized quickly without waiting to provision more VMs.
To prepare the template VM:
- Create a template VM with the same properties as the master VM. Assign a hard drive to the template VM to use for write cache.
- Create a device record in the Citrix Provisioning database with the MAC address of the template VM.
- Assign the virtual disk to the template VM, and then set the device to boot from virtual disk.
- PXE boot the VM.
- Format the write-cache disk.
Install the Citrix Virtual Apps and Desktops Virtual Delivery Agent
- Using the Citrix Provisioning console, set the virtual disk image mode toPrivate Image.
- Install the Citrix Virtual Apps and Desktops Virtual Delivery Agent (VDA) and point the VDA to the Citrix Virtual Apps and Desktops Server during the installation.Note:Alternatively, you can install both the VDA and the target device software before creating the virtual disk image. Both install methods require the new template VM to have a formatted write-cache hard drive.
- Reboot the VM, and then shut the VM down.
- Convert the VM to a template.
Create Citrix Virtual Apps and Desktops VMs
- Using the Citrix Provisioning console, set the virtual disk image mode toStandard Image.
- Choose the preferred write cache method.
- Select from the following provisioning methods:
- Deploying virtual desktops to VMs using the Citrix Virtual Apps and Desktops Setup Wizard
- Using the Streamed VM Setup Wizard
Create Citrix Virtual Apps and Desktops machine catalogs
When choosing between creating physical or virtual/blade server machine catalogs, it is important to consider the different advantages and requirements. For example, VM machine catalogs allow for power Citrix Virtual Apps and Desktops management while physical machine catalogs do not.
Physical machine catalogs
Device names must exist in Citrix Provisioning device collection and in Active Directory.
Tip:
The Citrix Virtual Apps and Desktops host record is not required and the VM record names are not verified.
- Start the Citrix Virtual Apps and Desktops Machine Catalog Setup Wizard, then selectWindows Desktop OSon theOperating Systempage.
- On theMachine Managementpage, forThis Machine Catalog usesselectMachines that are not power managed, for example, physical machines.
- ForDeploy machines using:selectCitrix Provisioning. Power management is not provided by Citrix Virtual Apps and Desktops.
- ForUser ExperienceselectUsers connectto a random desktop each time they log on.
- Enter the provisioning server’s IP address for the device collection.
- Identify the domain where all device Active Directory records are stored and the VDA version level, then clickConnect.
- In the structure that appears, select theCitrix Provisioning devicecollection where all the vGPU devices are located, and then clickNext. Device records are stored in an exclusive device collection.
- Enter a machine catalog name and description, and then clickFinish.
Create a Delivery Group and associate it with the machine catalog
For details on creating a Delivery Group, see theCitrix Virtual Apps and Desktops documentation.
Citrix Provisioning and Citrix Virtual Apps and Desktops cloud considerations
Within a cloud, you create a machine catalog and deploy it to those machines using Citrix Provisioning by pointing the catalog to a provisioning collection. If you use Citrix Provisioning with a cloud, all the machines within the provisioning collection must be associated with Active Directory accounts.
For more information, seeCitrix Provisioning managed by Citrix Cloud.