Delegated License Service Release Notes

NVIDIA Delegated License Service Release Notes

Release information for all users of NVIDIA Delegated License Service.

This document summarizes current status, information on supported platforms, and known issues with NVIDIA^® License System release 2.0.1.

1.1. Supported Platforms

1.1.1. Supported Hypervisors

For deployment in a virtual machine, the Delegated License Server (DLS) component of the NVIDIA License System is supplied as a virtual appliance. The virtual appliance must be installed on a supported hypervisor software release.

The following hypervisor software releases are supported:

• Citrix Hypervisor 8.2
• Linux Kernel-based Virtual Machine (KVM) hypervisors with QEMU 2.12.0 (qemu-kvm-2.12.0-64.el8.2.27782638)
• Microsoft Windows Server with Hyper-V 2019 Datacenter edition
• Red Hat Virtualization 4.3
• VMware vSphere Hypervisor (ESXi) 6.7, 7.0, 7.0.2, and 7.0.3

1.1.2. Supported Container Orchestration Platforms

For deployment on a bare-metal OS, the Delegated License Server (DLS) component of the NVIDIA License System is supplied as a containerized software image. The containerized software image must be deployed on a supported container orchestration platform.

The following container orchestration platform releases are supported:

• Docker 20.10.17 with Docker Compose 2.6.0
• Kubernetes 1.23.8
• Red Hat OpenShift Container Platform 4.10.18 with Kubernetes 1.23.5
• VMware Tanzu Application Platform 1.1 with Kubernetes 1.23.6

1.1.3. Supported NVIDIA vGPU Software Releases

NVIDIA License System supports NVIDIA vGPU software graphics drivers starting with NVIDIA vGPU software release 13.0 as licensed clients.

1.1.4. Web Browser Requirements

NVIDIA License System and NVIDIA Licensing Portal were tested with Google Chrome version 86.0.4240.111 (Official Build) (64-bit).

1.2. Changes in this Release

• Miscellaneous bug fixes as listed in Resolved Issues

A container orchestration platform cannot control or restrict access to the OS on which the platform is running. Therefore, containerized DLS software images cannot support the features of VM-based DLS virtual appliances that rely on the ability of the appliance to control the underlying OS.

Containerized DLS software images do not support the following features, for which equivalent functionality is available through standard OS interfaces:

• Log archive settings
• NTP configuration
• Static IP address configuration
• DLS diagnostics user configuration
• Disk expansion

Because a container orchestration platform cannot control the underlying OS, the following limitations also apply to containerized DLS software images:

• Online migration from a VM-based DLS virtual appliance to a containerized DLS software image is not supported because the destination containerized DLS software image retains its IP address even after data migration.

  Instead, you must use offline migration when migrating from a VM-based DLS virtual appliance to a containerized DLS software image.

• When the secondary node is removed from an HA cluster, the containerized DLS software image that hosts the node is not shut down.

  Instead, you must shut down the DLS software container manually.

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 License System before the issue was resolved.

4.1. Online DLS migration fails with HTTP error 500 for IPv4 address configuration on mixed network

Description

On a mixed IPv4 and IPv6 network infrastructure, online migration of a DLS instance hosted on a VM with an IPv4 address fails. After the data has been migrated from the existing DLS appliance, the migration cannot be confirmed on the new DLS appliance because the ACKNOWLEDGE MIGRATION button does not appear in the management interface on the new DLS appliance. Furthermore, the IPv4 address of the VM that hosts the new DLS appliance is not displayed in the management interface on the new DLS appliance. Any attempt to set IP address of the VM from the management interface fails with HTTP error 500. This issue occurs because, during initialization, the DLS application ignores IPv4 addresses on an network in which IPv6 is also configured.

Workaround

Prevent the DLS application from setting an IPv6 address when the application starts.

1. Create the DLS sudo user account.

   1. From the hypervisor, log in as the user dls_system to the VM that hosts the DLS virtual appliance.

      You don’t need to provide a password to log in as the dls_system user.

   2. Run the /etc/adminscripts/enable_sudo.sh script.

      Copy

      Copied!

                  
      
                  
      $ /etc/adminscripts/enable_sudo.sh
              

   3. When prompted, provide a password for this user.

      The sudo user with elevated privileges rsu_admin is created.

2. Log in as the user rsu_admin to the VM that hosts the DLS virtual appliance.

3. Use the sed command to comment out the line that sets the IPv6 address in the startup script for the DLS application.

   Copy

   Copied!

               
   
               
   $ sudo sed -i \
   "s/ipv6_address=\$(getCurrentIPv6Address)/#ipv6_address=\$(getCurrentIPv6Address)/g" \
   /etc/dls/scripts/applicationStartup.sh
           

4. Restart the DLS application.

   Copy

   Copied!

               
   
               
   $ sudo systemctl restart applicationStartup
           

For an HA cluster of DLS instances, wait until the DLS application has started before repeating this workaround for the VM that hosts the other node in the cluster.

Status

Open

Ref. #

3804294

4.2. After DLS migration, renewal of licenses checked out before the migration fails

Description

After a DLS instance is migrated to a new DLS appliance, the migrated DLS instance fails to renew licenses checked out before the migration. However, the checked out licenses remain active even after the failure to renew them. This issue does not prevent licensed clients from checking out licenses. When this issue occurs on a licensed Linux client, messages similar to the following messages are written to the standard activity log of the client:

            

            
Jan 20 13:39:56 dhcp-198-51-100-10 nvidia-gridd[2848]: Failed to renew license
Jan 20 13:41:26 dhcp-198-51-100-10 nvidia-gridd[2848]: Failed to renew license from dhcp-198-51-100-20.nvidia.com
(Info: NVIDIA Virtual PC - Error: Invalid response received from server)
        

Workaround

To avoid this issue, return all licenses checked out from the license server on the DLS instance that you want to migrate before starting the migration. To recover from this issue after migration, restart the NVIDIA driver service that runs the core NVIDIA vGPU software logic on any licensed client that fails to renew a license.

• On Windows, restart the NVIDIA Display Container LS service.
• On Linux, restart the nvidia-gridd service.

Status

Open

Ref. #

3508713

4.3. Licensed client on IPv4 network fails to acquire a license

Description

A licensed client on an IPv4 network fails to acquire a license from a DLS instance. This issue occurs because the IP address in the client configuration token through which the DLS instance is accessed is an IPv6 address. When this issue occurs, an error message reporting a generic network communication failure is written to the licensing event log. In the message, the IP address of the VM in the request from the licensed client is an IPv6 address.

            

            
Thu Sep 15 14:23:28 2022:<3>:Failed to acquire license from 2001:db8:0:4:4c83:516d:1c7:ab97 
(Info: NVIDIA Virtual PC - Error: Generic network communication failure)
        

Workaround

Prevent the DLS application from setting an IPv6 address when the application starts.

1. Create the DLS sudo user account.

   1. From the hypervisor, log in as the user dls_system to the VM that hosts the DLS virtual appliance.

      You don’t need to provide a password to log in as the dls_system user.

   2. Run the /etc/adminscripts/enable_sudo.sh script.

      Copy

      Copied!

                  
      
                  
      $ /etc/adminscripts/enable_sudo.sh
              

   3. When prompted, provide a password for this user.

      The sudo user with elevated privileges rsu_admin is created.

2. Log in as the user rsu_admin to the VM that hosts the DLS virtual appliance.

3. Use the sed command to comment out the line that sets the IPv6 address in the startup script for the DLS application.

   Copy

   Copied!

               
   
               
   $ sudo sed -i \
   "s/ipv6_address=\$(getCurrentIPv6Address)/#ipv6_address=\$(getCurrentIPv6Address)/g" \
   /etc/dls/scripts/applicationStartup.sh
           

4. Restart the DLS application.

   Copy

   Copied!

               
   
               
   $ sudo systemctl restart applicationStartup
           

For an HA cluster of DLS instances, wait until the DLS application has started before repeating this workaround for the VM that hosts the other node in the cluster.

Status

Open

Ref. #

3797900

4.4. Validation of the client configuration token fails

Description

When Network Time Protocol (NTP) servers are configured for a VM-based DLS instance, the system times on the DLS instance and the licensed client might still be different. In this situation, validation of the client configuration token fails. When the licensed client requests a license, the request fails and the following error message is displayed:

            

            
Client Configuration Token Validation Failed.
Either the token is not activated or system clock settings are tampered
        

Workaround

When configuring NTP servers on a DLS virtual appliance, specify the IP addresses, not the fully qualified domain names, of the NTP servers.

Status

Open

Ref. #

3718863

4.5. VM hosting a DLS appliance cannot be reached

Description

After a VM-based DLS appliance has been installed, the VM that is hosting the DLS appliance cannot be reached after it has been started. This issue occurs when a static IP address has been assigned to the VM that is hosting the DLS appliance and the subnet mask of the VM’s network was specified in an incorrect format. The subnet mask of the VM’s network must be specified in classless inter-domain routing (CIDR) format without the leading slash character (/).

Workaround

Reinstall the VM-based DLS appliance, specifying the subnet mask in the correct format, namely, CIDR format without the leading slash character (/).

To get a subnet mask in CIDR format from its decimal equivalent, refer to the table on page 2 of IETF RFC 1878: Variable Length Subnet Table For IPv4. For example, the subnet mask in CIDR format of the decimal equivalent 255.255.255.0 is 24.

Status

Not a bug

Ref. #

3741535

4.6. Client fails to acquire offline license when rebooted

Description

When a licensed client that is configured with an offline license is rebooted, the client might fail to acquire a license. When this issue occurs, the following message is written to the licensing event log file on the client:

            

            
Client fingerprint mismatch - No valid lease found in local trusted store
        

This issue occurs when the MAC addresses of the network adapters for a client change when the client is rebooted. When the MAC addresses change, the NVIDIA vGPU software graphics driver treats the client as a new client and the offline license in the client’s trusted storage database is discarded.

Typically, the MAC addresses change because the network configuration of the client has been explicitly changed by an administrator. However, the MAC address of a client can unexpectedly change when the client is rebooted for several reasons, for example:

• The client requests a license before the client’s network interfaces are initialized.
• Docker or the NVIDIA Container Runtime for Docker is installed on the client and the ifconfig command lists it as a network interface.

Status

Open

Ref. #

200665895

If necessary, you can create a predefined sudo user account for a DLS virtual appliance. This user account has the elevated privileges required to update and upgrade the Ubuntu GPL/LGPL v3 licensed Open Source Software (OSS) libraries within the DLS virtual appliance. This account provides no other access to a DLS virtual appliance.

This account is provided to comply with the terms of the GPL/LGPL v3 license under which some libraries in the Ubuntu operating system in the DLS virtual appliance are released.
CAUTION:

Perform this task for each DLS virtual appliance for which you want to create the DLS sudo user account. If the DLS virtual appliance is hosting a node in an HA cluster, the creation of the user is not automatically propagated to the other node in the cluster.

1. From the hypervisor, log in as the user dls_system to the VM that hosts the DLS virtual appliance. You don’t need to provide a password to log in as the dls_system user.
2. Run the /etc/adminscripts/enable_sudo.sh script.
   Copy

   Copied!

               
   
               
   $ /etc/adminscripts/enable_sudo.sh
           

3. When prompted, provide a password for this user.

The sudo user with elevated privileges rsu_admin is created.

The file /var/dls/sudouser is created to indicate that the Ubuntu GPL/LGPL v3 licensed OSS libraries within the DLS virtual appliance have been updated or upgraded. If the DLS virtual appliance is hosting a node in an HA cluster, this file is automatically copied to the other node in the cluster.

In addition, to update the OS or install packages on Ubuntu:

1. Test to make sure the Ubuntu repositories are reachable with the existing network settings.
2. If the repository URLs are not getting resolved, you should delete the symlink /etc/resolv.conf, and copy the default resolv.conf located at /run/NetworkManager to /etc/resolv.conf.
   Copy

   Copied!

               
   
               
   sudo rm -f /etc/resolv.conf
           

   Copy

   Copied!

               
   
               
   sudo cp /run/NetworkManager/no-stub-resolv.conf /etc/resolv.conf
           

   Note:

   Note:

   Before you copy /run/NetworkManager/resolv.conf, make sure you make a DNS server entry that will resolve the Ubuntu (or any custom) package repositories.

3. Once the OS update/upgrade is done, please restore the network configurations to their original state by executing the following commands:
   Copy

   Copied!

               
   
               
   sudo rm -f /etc/resolv.conf
           

   Copy

   Copied!

               
   
               
   sudo ln -s /run/NetworkManager/no-stub-resolv.conf /etc/resolv.conf
           

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 Maxwell, NVIDIA Pascal, NVIDIA Turing, NVIDIA Volta, 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.

Copyright

© 2022 NVIDIA Corporation. All rights reserved.