To be able to allot licenses to an NVIDIA License System instance, you must create at least one license server on the NVIDIA Licensing Portal. Creating a license server defines the set of licenses to be allotted.

1. In the NVIDIA Licensing Portal, navigate to the organization or virtual group for which you want to create the license server.
   1. If you are not already logged in, log in to the NVIDIA Enterprise Application Hub and click NVIDIA LICENSING PORTAL to go to the NVIDIA Licensing Portal.
   2. Optional: If your assigned roles give you access to multiple virtual groups, click View settings at the top right of the page and in the My Info window that opens, select the virtual group from the Virtual Group drop-down list, and close the My Info window.
   If no license servers have been created for your organization or virtual group, the NVIDIA Licensing Portal dashboard displays a message asking if you want to create a license server.
2. In the left navigation pane of the NVIDIA Licensing Portal dashboard, expand LICENSE SERVER and click CREATE SERVER. The Create License Server wizard is started.
   
   
   
   

   The Create License Server wizard opens.

   
   
   
   
   

3. On the Basic details page of the wizard, provide the details of your license server.
   1. Ensure that the Create legacy server option is not set. Setting this option creates a legacy NVIDIA vGPU software license server, not a license server for NVIDIA License System.
   2. In the Server Name field, enter your choice of name for the license server.
   3. In the Description field, enter a text description of the license server. This description is required and will be displayed on the details page for the license server that you are creating.
   4. Optional: If you want NVIDIA License System to automatically bind the license server to and install it on the default CLS instance, select the Express CLS Installation? option.
   5. Optional: If you want to use this license server for node-locked licenses, select the Disconnected leasing mode? option.
   6. Click Next: Select features.
4. On the Select features page of the wizard, add the licenses for the products that you want to allot to this license server. For each product, add the licenses as follows:
   1. In the list of products, select the product for which you want to add licenses.
   2. In the text-entry field in the ADDED column, enter the number of licenses for the product that you want to add.
      
      
      
      
   3. Click Next: Preview server creation.
5. On the Preview server creation page, click CREATE SERVER.
   
   
   
   

When you create a CLS instance, the instance is automatically registered with the NVIDIA Licensing Portal. This task is only necessary if you are not using the default CLS instance.

1. If you are not already logged in, log in to the NVIDIA Enterprise Application Hub and click NVIDIA LICENSING PORTAL to go to the NVIDIA Licensing Portal.
2. In the left navigation pane of the NVIDIA Licensing Portal dashboard, click SERVICE INSTANCES.
   
   
   
   
3. On the Service Instances page, from the Actions menu, choose Create cloud (CLS) instance.

   The Create cloud (CLS) instance pop-up window opens.

4. Provide the details of your cloud service instance.
   1. In the Name field, enter your choice of name for the service instance.
   2. In the Description field, enter a text description of the service instance. This description is required and will be displayed on the Service Instances page when the entry for service instance that you are creating is expanding.
5. Click CREATE CLS INSTANCE.

Binding a license server to a service instance ensures that licenses on the server are available only from that service instance. As a result, the licenses are available only to the licensed clients that are served by the service instance to which the license server is bound.

1. In the NVIDIA Licensing Portal, navigate to the organization or virtual group to which the license server belongs.
   1. If you are not already logged in, log in to the NVIDIA Enterprise Application Hub and click NVIDIA LICENSING PORTAL to go to the NVIDIA Licensing Portal.
   2. Optional: If your assigned roles give you access to multiple virtual groups, click View settings at the top right of the page and in the My Info window that opens, select the virtual group from the Virtual Group drop-down list, and close the My Info window.
2. In the left navigation pane of the NVIDIA Licensing Portal dashboard, expand LICENSE SERVERS and click LIST SERVERS.
3. In the list of license servers on the License Servers page that opens, from the Actions menu for the license server, choose Bind.
4. In the Bind Service Instance pop-up window that opens, select the service instance to which you want to bind the license server and click BIND. The Bind Service Instance pop-up window confirms that the license server has been bound to the service instance.

1. In the NVIDIA Licensing Portal, navigate to the organization or virtual group for which you want to install the license server.
   1. If you are not already logged in, log in to the NVIDIA Enterprise Application Hub and click NVIDIA LICENSING PORTAL to go to the NVIDIA Licensing Portal.
   2. Optional: If your assigned roles give you access to multiple virtual groups, click View settings at the top right of the page and in the My Info window that opens, select the virtual group from the Virtual Group drop-down list, and close the My Info window.
2. In the left navigation pane of the NVIDIA Licensing Portal dashboard, expand LICENSE SERVER and click LIST SERVERS.
3. In the list of license servers on the License Servers page that opens, click the name of the license server that you want to install.
4. In the License Server Details page that opens, from the Actions menu, choose Install.
5. In the Install License Server pop-up window that opens, click INSTALL SERVER.

1. Log in to the NVIDIA Enterprise Application Hub and click NVIDIA LICENSING PORTAL to go to the NVIDIA Licensing Portal.
2. If your assigned roles give you access to multiple virtual groups, select the virtual group for which you are managing licenses from the list of virtual groups at the top right of the NVIDIA Licensing Portal dashboard.
3. In the left navigation pane, click SERVICE INSTANCES.
   
   
   
   
4. On the Service Instances page that opens, from the Actions menu for the CLS instance for which you want to generate a client configuration token, choose Generate client configuration token.
5. In the Generate Client Configuration Token pop-up window that opens, select the references that you want to include in the client configuration token.
   1. From the list of scope references, select the scope references that you want to include.
      
      
      
      

      You must select at least one scope reference.

      Each scope reference specifies the license server that will fulfil a license request.

   2. Optional: Click the Fulfillment class references tab, and from the list of fulfillment class references, select the fulfillment class references that you want to include.
      
      
      
      Including fulfillment class references is optional.
   3. Click DOWNLOAD CLIENT CONFIGURATION TOKEN.
   A file named client_configuration_token_mm-dd-yyyy-hh-mm-ss.tok is saved to your default downloads folder.

Each DLS virtual appliance is configured with a user account specifically for administering the DLS. This account provides access through a web-based management interface to the NVIDIA Licensing application on the appliance. Before administering a DLS virtual appliance, you must register this user to be able to access this management interface.

1. Open a web browser and connect to the URL https://dls-vm-ip-address.

   dls-vm-ip-address

   The IP address or, if defined, the fully qualified domain name of the VM on which the DLS virtual appliance is installed.

   You can get the IP address from the management console of your hypervisor.

2. On the Set Up page that opens, click NEW INSTALLATION.
3. On the Register User page that opens, provide the credentials for the DLS administrator user.
   Note: If the DLS administrator user has already been registered, the login page opens instead of the Register User page.
   1. Optional: If you want to change the user name from the preset name dls_admin, replace the text in the Username field with your choice of user name.
   2. Provide a password for the DLS administrator user and confirm the password. The password must be at least eight characters long and is case sensitive.
   Note: You can change the DLS administrator user name and password at any time after the DLS administrator user is registered.
4. Determine whether you want to enable an additional user that will be able to access the log files for the DLS virtual appliance.

   This additional user will have the user name dls_diagnostics and the password that you provide for the dls_admin user. The dls_diagnostics user will be able to access the log files for the DLS virtual appliance by logging in to the DLS virtual appliance from the hypervisor console.

   Note: The dls_diagnostics account is not available for containerized DLS software images.
   • If you want to enable this additional user, ensure that the Create a diagnostic user option remains selected.
   • Otherwise, deselect the Create a diagnostic user option.
   Note: You can enable or disable the dls_diagnostics user at any time after the DLS administrator user is registered. Click View settings at the top right of any page in the NVIDIA Licensing application on the DLS virtual appliance. Then, in the My Info window that opens, change the setting of the Diagnotics user option.
5. Click REGISTER. The Register User page is refreshed to confirm that the user has been registered and displays a local reset secret to enable you to reset the user's password.
6. Copy the local reset secret and store it securely, for example, by clicking the clipboard icon and pasting the local reset secret into a plain text file that is readable only by you. You will need this key to reset the DLS administrator user's password.
7. Click CONTINUE TO LOGIN.
8. On the login page that opens, type the user name of the DLS administrator user, provide the password that you set for this user, and click LOGIN.

A standalone DLS instance must be registered before it can be used.

1. Log in to the DLS virtual appliance that will host the DLS instance.
2. In the left navigation pane, click SERVICE INSTANCE.
3. On the Service Instance page that opens, under Node Configuration, ensure that the Enable High Availability option is not set.
4. Click CREATE STANDALONE to start the configuration and wait for it to complete. The Service Instance page displays the progress of the standalone DLS instance configuration.

By default, a DLS instance is created with the name DEFAULT_timestamp and the description ON_PREM_SERVICE_INSTANCE. To distinguish a DLS instance on the NVIDIA Licensing Portal when multiple DLS instances are configured, change these defaults to a meaningful name and the description.

1. Log in to the DLS virtual appliance that is hosting the instance whose name and description you want to change.
2. In the left navigation pane of the NVIDIA Licensing dashboard, click SERVICE INSTANCE.
3. On the Service Instance page that opens, click EDIT.
4. In the Edit Service Instance dialog box that opens, type your choice of name and description for the instance and click UPDATE.
   Note: The instance name cannot contain special characters.
   The name and description of the instance are updated on the Service Instance page.

To be able to allot licenses to an NVIDIA License System instance, you must create at least one license server on the NVIDIA Licensing Portal. Creating a license server defines the set of licenses to be allotted.

1. In the NVIDIA Licensing Portal, navigate to the organization or virtual group for which you want to create the license server.
   1. If you are not already logged in, log in to the NVIDIA Enterprise Application Hub and click NVIDIA LICENSING PORTAL to go to the NVIDIA Licensing Portal.
   2. Optional: If your assigned roles give you access to multiple virtual groups, click View settings at the top right of the page and in the My Info window that opens, select the virtual group from the Virtual Group drop-down list, and close the My Info window.
   If no license servers have been created for your organization or virtual group, the NVIDIA Licensing Portal dashboard displays a message asking if you want to create a license server.
2. In the left navigation pane of the NVIDIA Licensing Portal dashboard, expand LICENSE SERVER and click CREATE SERVER. The Create License Server wizard is started.
   
   
   
   

   The Create License Server wizard opens.

   
   
   
   
   

3. On the Basic details page of the wizard, provide the details of your license server.
   1. Ensure that the Create legacy server option is not set. Setting this option creates a legacy NVIDIA vGPU software license server, not a license server for NVIDIA License System.
   2. In the Server Name field, enter your choice of name for the license server.
   3. In the Description field, enter a text description of the license server. This description is required and will be displayed on the details page for the license server that you are creating.
   4. Optional: If you want NVIDIA License System to automatically bind the license server to and install it on the default CLS instance, select the Express CLS Installation? option.
   5. Optional: If you want to use this license server for node-locked licenses, select the Disconnected leasing mode? option.
   6. Click Next: Select features.
4. On the Select features page of the wizard, add the licenses for the products that you want to allot to this license server. For each product, add the licenses as follows:
   1. In the list of products, select the product for which you want to add licenses.
   2. In the text-entry field in the ADDED column, enter the number of licenses for the product that you want to add.
      
      
      
      
   3. Click Next: Preview server creation.
5. On the Preview server creation page, click CREATE SERVER.
   
   
   
   

A DLS instance is created automatically when the virtual appliance on which the instance resides is installed. However, to enable the instance to be bound to a license server, you must register the instance with the NVIDIA Licensing Portal.

1. If you are not already logged in, log in to the NVIDIA Licensing application at the IP address of the VM on which the DLS virtual appliance is installed.
2. In the left navigation pane of the NVIDIA Licensing dashboard, click SERVICE INSTANCES.
3. On the Service Instance page that opens, click DOWNLOAD DLS INSTANCE TOKEN. A DLS instance token file that is named dls_instance_token_mm-dd-yyyy-hh-mm-ss.tok is downloaded.
4. In the NVIDIA Licensing Portal, navigate to the organization or virtual group for which you are registering the service instance.
   1. If you are not already logged in, log in to the NVIDIA Enterprise Application Hub and click NVIDIA LICENSING PORTAL to go to the NVIDIA Licensing Portal.
   2. Optional: If your assigned roles give you access to multiple virtual groups, click View settings at the top right of the page and in the My Info window that opens, select the virtual group from the Virtual Group drop-down list, and close the My Info window.
5. On the Service Instances page, from the Actions menu, choose Upload on-premises (DLS) instance token.
   
   
   
   
6. On Service Instances page that opens, click UPLOAD DLS INSTANCE TOKEN.
7. In the Upload DLS Instance Token window that opens, click SELECT INSTANCE TOKEN.
   
   
   
   
8. In the file browser that opens, navigate to the folder that contains the DLS instance token file that is named dls_instance_token_mm-dd-yyyy-hh-mm-ss.tok that you downloaded and select the file.
9. Back in the Upload DLS Instance Token window, select the For New Installation option and click UPLOAD INSTANCE TOKEN. The list of pending registrations is opened and the service instance identified by the DLS instance token that you uploaded is listed.
10. In the list of pending registrations, follow the Register link for the service instance identified by the DLS instance token that you uploaded. The service instance is added to the list of registered service instances.

Binding a license server to a service instance ensures that licenses on the server are available only from that service instance. As a result, the licenses are available only to the licensed clients that are served by the service instance to which the license server is bound.

1. In the NVIDIA Licensing Portal, navigate to the organization or virtual group to which the license server belongs.
   1. If you are not already logged in, log in to the NVIDIA Enterprise Application Hub and click NVIDIA LICENSING PORTAL to go to the NVIDIA Licensing Portal.
   2. Optional: If your assigned roles give you access to multiple virtual groups, click View settings at the top right of the page and in the My Info window that opens, select the virtual group from the Virtual Group drop-down list, and close the My Info window.
2. In the left navigation pane of the NVIDIA Licensing Portal dashboard, expand LICENSE SERVERS and click LIST SERVERS.
3. In the list of license servers on the License Servers page that opens, from the Actions menu for the license server, choose Bind.
4. In the Bind Service Instance pop-up window that opens, select the service instance to which you want to bind the license server and click BIND. The Bind Service Instance pop-up window confirms that the license server has been bound to the service instance.

1. In the NVIDIA Licensing Portal, navigate to the organization or virtual group for which the license server was created.
   1. If you are not already logged in, log in to the NVIDIA Enterprise Application Hub and click NVIDIA LICENSING PORTAL to go to the NVIDIA Licensing Portal.
   2. Optional: If your assigned roles give you access to multiple virtual groups, click View settings at the top right of the page and in the My Info window that opens, select the virtual group from the Virtual Group drop-down list, and close the My Info window.
2. In the left navigation pane of the NVIDIA Licensing Portal dashboard, expand LICENSE SERVER and click LIST SERVERS.
3. In the list of license servers on the License Servers page that opens, click the name of the license server that you want to install.
4. In the License Server Details page that opens, from the Actions menu, choose Download.
5. In the Download License File window that opens, click Download. A license server file that is named license_mm-dd-yyyy-hh-mm-ss.bin is downloaded.
6. If you are not already logged in, log in to the NVIDIA Licensing application at the IP address of the VM on which the DLS virtual appliance is installed. If a license server has not been installed on the DLS virtual appliance, the NVIDIA Licensing dashboard displays a message asking if you want to install a license server.
7. If you are updating the license server on the DLS virtual appliance, in the left navigation pane of the NVIDIA Licensing dashboard, click UPLOAD SERVER. If a license server has not been installed on the DLS virtual appliance, omit this step. The Server Upload page opens.
8. On the NVIDIA Licensing dashboard or the Server Upload page, click SELECT LICENSE SERVER FILE.
   
   
   
   
9. In the file browser that opens, navigate to the folder that contains the license server file named license_mm-dd-yyyy-hh-mm-ss.bin that you downloaded and select the file.
10. When asked if you want to install the selected file, click INSTALL.

1. If you are not already logged in, log in to the NVIDIA Licensing application at the IP address of the VM on which the DLS instance resides.
2. In the left navigation pane, click SERVICE INSTANCE.
3. On the Service Instance page that opens, from the Actions menu for the DLS instance for which you want to generate a client configuration token, choose Generate client configuration token.
   
   
   
   
4. In the Generate Client Configuration Token pop-up window that opens, select the references that you want to include in the client configuration token.
   1. From the list of scope references, select the scope references that you want to include.
      
      
      
      

      You must select at least one scope reference.

      Each scope reference specifies the license server that will fulfil a license request.

   2. Optional: Click the Fulfillment class references tab, and from the list of fulfillment class references, select the fulfillment class references that you want to include.
      
      
      
      Including fulfillment class references is optional.
   3. Optional: If you want the service instance to be identified through its IP address instead of its fully qualified domain name, select the Use IP address instead of FQDN for CCT option.
   4. Click DOWNLOAD CLIENT CONFIGURATION TOKEN.
   A file named client_configuration_token_mm-dd-yyyy-hh-mm-ss.tok is saved to your default downloads folder.

1. Copy the NVIDIA Virtual GPU Manager package file to the ESXi host.
2. Put the ESXi host into maintenance mode.

   $ esxcli system maintenanceMode set –-enable true

3. Run the esxcli command to install the NVIDIA Virtual GPU Manager from the package file.

   • For a software component, run the following command:

     $ esxcli software vib install -d /vmfs/volumes/datastore/software-component.zip

     datastore

     The name of the VMFS datastore to which you copied the software component.

     software-component

     The name of the file that contains the NVIDIA Virtual GPU Manager package in the form of a software component. Ensure that you specify the file that was extracted from the downloaded ZIP archive. For example, for VMware vSphere 7.0, software-component is NVD.NVIDIA_bootbank_NVIDIA-VMware_510.108.03-1OEM.700.0.0.8169922-offline_bundle-build-number.

   • For a VIB file, run the following command:

     $ esxcli software vib install –v directory/NVIDIA**.vib

     directory

     The absolute path to the directory to which you copied the VIB file. You must specify the absolute path even if the VIB file is in the current working directory.

4. Exit maintenance mode.

   $ esxcli system maintenanceMode set –-enable false

5. Reboot the ESXi host.

   $ reboot

6. Verify that the NVIDIA kernel driver can successfully communicate with the physical GPUs in your system by running the nvidia-smi command without any options.

   $ nvidia-smi

   If successful, the nvidia-smi command lists all the GPUs in your system.

1. Copy the NVIDIA Virtual GPU Manager RPM file to the Citrix Hypervisor dom0 shell.
2. Run the rpm command to install the package.

   [root@xenserver ~]# rpm -iv NVIDIA-**.rpm

3. Reboot the Citrix Hypervisor platform.

   [root@xenserver ~]# shutdown -r now

4. After the Citrix Hypervisor host has rebooted, verify the installation of the NVIDIA Virtual GPU Manager package for Citrix Hypervisor by checking for the NVIDIA kernel driver in the list of kernel-loaded modules.

   [root@xenserver ~]# lsmod |grep nvidia
   nvidia 8152994 0
   i2c_core 20294 2 nvidia,i2c_

If ECC memory is unsuitable for your workloads but is enabled on your GPUs, disable it. You must also ensure that ECC memory is disabled on all GPUs if you are using NVIDIA vGPU with a hypervisor software version or a GPU that does not support ECC memory with NVIDIA vGPU. If your hypervisor software version or GPU does not support ECC memory and ECC memory is enabled, NVIDIA vGPU fails to start.

1. Use nvidia-smi to list the status of all physical GPUs or vGPUs, and check for ECC noted as enabled.

   # nvidia-smi -q
   
   ==============NVSMI LOG==============
   
   Timestamp                           : Mon Dec 26 18:36:45 2022
   Driver Version                      : 510.108.03
   
   Attached GPUs                       : 1
   GPU 0000:02:00.0
   
   [...]
   
       Ecc Mode
           Current                     : Enabled
           Pending                     : Enabled
   
   [...]

2. Change the ECC status to off for each GPU for which ECC is enabled.
   • If you want to change the ECC status to off for all GPUs on your host machine or vGPUs assigned to the VM, run this command:

     # nvidia-smi -e 0

   • If you want to change the ECC status to off for a specific GPU or vGPU, run this command:

     # nvidia-smi -i id -e 0

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

     This example disables ECC for the GPU with index 0000:02:00.0.

     # nvidia-smi -i 0000:02:00.0 -e 0

3. Reboot the host or restart the VM.
4. Confirm that ECC is now disabled for the GPU or vGPU.

   # nvidia—smi —q
   
   ==============NVSMI LOG==============
   
   Timestamp                           : Mon Dec 26 18:37:53 2022
   Driver Version                      : 510.108.03
   
   Attached GPUs                       : 1
   GPU 0000:02:00.0
   [...]
   
       Ecc Mode
           Current                     : Disabled
           Pending                     : Disabled
   
   [...]

If ECC memory is suitable for your workloads and is supported by your hypervisor software and GPUs, but is disabled on your GPUs or vGPUs, enable it.

1. Use nvidia-smi to list the status of all physical GPUs or vGPUs, and check for ECC noted as disabled.

   # nvidia-smi -q
   
   ==============NVSMI LOG==============
   
   Timestamp                           : Mon Dec 26 18:36:45 2022
   Driver Version                      : 510.108.03
   
   Attached GPUs                       : 1
   GPU 0000:02:00.0
   
   [...]
   
       Ecc Mode
           Current                     : Disabled
           Pending                     : Disabled
   
   [...]

2. Change the ECC status to on for each GPU or vGPU for which ECC is enabled.
   • If you want to change the ECC status to on for all GPUs on your host machine or vGPUs assigned to the VM, run this command:

     # nvidia-smi -e 1

   • If you want to change the ECC status to on for a specific GPU or vGPU, run this command:

     # nvidia-smi -i id -e 1

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

     This example enables ECC for the GPU with index 0000:02:00.0.

     # nvidia-smi -i 0000:02:00.0 -e 1

3. Reboot the host or restart the VM.
4. Confirm that ECC is now enabled for the GPU or vGPU.

   # nvidia—smi —q
   
   ==============NVSMI LOG==============
   
   Timestamp                           : Mon Dec 26 18:37:53 2022
   Driver Version                      : 510.108.03
   
   Attached GPUs                       : 1
   GPU 0000:02:00.0
   [...]
   
       Ecc Mode
           Current                     : Enabled
           Pending                     : Enabled
   
   [...]

1. Log in to vCenter Server by using the vSphere Web Client.
2. In the navigation tree, select your ESXi host and click the Configure tab.
3. From the menu, choose Graphics and then click the Host Graphics tab.
4. On the Host Graphics tab, click Edit.
   
   
   
   
5. In the Edit Host Graphics Settings dialog box that opens, select Shared Direct and click OK.
   
   
   
   

   After you click OK, the default graphics type changes to Shared Direct.

6. Click the Graphics Devices tab to verify the configured type of each physical GPU on which you want to configure vGPU. The configured type of each physical GPU must be Shared Direct. For any physical GPU for which the configured type is Shared, change the configured type as follows:
   1. On the Graphics Devices tab, select the physical GPU and click the Edit icon.
      
      
      
      
   2. In the Edit Graphics Device Settings dialog box that opens, select Shared Direct and click OK.
      
      
      
      
7. Restart the ESXi host or stop and restart the Xorg service if necessary and nv-hostengine on the ESXi host.

   To stop and restart the Xorg service and nv-hostengine, perform these steps:

   1. VMware vSphere releases before 7.0 Update 1 only: Stop the Xorg service.

      As of VMware vSphere 7.0 Update 1, the Xorg service is no longer required for graphics devices in NVIDIA vGPU mode.

   2. Stop nv-hostengine.

      [root@esxi:~] nv-hostengine -t

   3. Wait for 1 second to allow nv-hostengine to stop.
   4. Start nv-hostengine.

      [root@esxi:~] nv-hostengine -d

   5. VMware vSphere releases before 7.0 Update 1 only: Start the Xorg service.

      As of VMware vSphere 7.0 Update 1, the Xorg service is no longer required for graphics devices in NVIDIA vGPU mode.

      [root@esxi:~] /etc/init.d/xorg start

8. In the Graphics Devices tab of the VMware vCenter Web UI, confirm that the active type and the configured type of each physical GPU are Shared Direct.
   
   
   
   

1. Open the vCenter Web UI.
2. In the vCenter Web UI, right-click the VM and choose Edit Settings.
3. Click the Virtual Hardware tab.
4. In the New device list, select Shared PCI Device and click Add. The PCI device field should be auto-populated with NVIDIA GRID vGPU.
   
   
   
   
5. From the GPU Profile drop-down menu, choose the type of vGPU you want to configure and click OK.
   Note: VMware vSphere does not support vCS. Therefore, C-series vGPU types are not available for selection from the GPU Profile drop-down menu.
6. Ensure that VMs running vGPU have all their memory reserved:
   1. Select Edit virtual machine settings from the vCenter Web UI.
   2. Expand the Memory section and click Reserve all guest memory (All locked).

1. Ensure the VM is powered off.
2. Right-click the VM in XenCenter, select Properties to open the VM’s properties, and select the GPU property. The available GPU types are listed in the GPU type drop-down list:
   
   
   
   

1. Physical GPUs only: Add the FeatureType DWord (REG_DWORD) registry value to the Windows registry key HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\GridLicensing.
   Note:

   • If you're licensing an NVIDIA vGPU, the FeatureType DWord (REG_DWORD) registry value is not required. NVIDIA vGPU software automatically selects the correct type of license based on the vGPU type.
   • If you are upgrading an existing driver, this value is already set.
   Set this value to the feature type of a GPU in pass-through mode or a bare-metal deployment:

   • 0: NVIDIA Virtual Applications
   • 2: NVIDIA RTX Virtual Workstation
2. Copy the client configuration token to the %SystemDrive%:\Program Files\NVIDIA Corporation\vGPU Licensing\ClientConfigToken folder.
3. Restart the NvDisplayContainer service.

After configuring a client with an NVIDIA vGPU software license, verify the license status by displaying the licensed product name and status.

nvidia-smi -q
==============NVSMI LOG==============

Timestamp                           : Wed Mar 31 01:49:28 2020
Driver Version                      : 440.88
CUDA Version                        : 10.0

Attached GPUs                       : 1
GPU 00000000:00:08.0
    Product Name                    : Tesla T4
    Product Brand                   : Grid
    Display Mode                    : Enabled
    Display Active                  : Disabled
    Persistence Mode                : N/A
    Accounting Mode                 : Disabled
    Accounting Mode Buffer Size     : 4000
    Driver Model
        Current                     : WDDM
        Pending                     : WDDM
    Serial Number                   : 0334018000638
    GPU UUID                        : GPU-ba2310b6-95d1-802b-f96f-5865410fe517
    Minor Number                    : N/A
    VBIOS Version                   : 90.04.21.00.01
    MultiGPU Board                  : No
    Board ID                        : 0x8
    GPU Part Number                 : 699-2G183-0200-100
    Inforom Version
        Image Version               : G183.0200.00.02
        OEM Object                  : 1.1
        ECC Object                  : 5.0
        Power Management Object     : N/A
    GPU Operation Mode
        Current                     : N/A
        Pending                     : N/A
    GPU Virtualization Mode
        Virtualization mode         : Pass-Through
    vGPU Software Licensed Product
        Product Name                : NVIDIA Virtual Compute Server
        License Status              : Licensed (Expiry: 2021-11-13 18:29:59 GMT)
    …
    …