Is this page helpful?

Known Issues#

2.0.0 Only: Upgrade or Migration from NVIDIA GPU Manager for VMware vCenter 1.x to 2.0.0 fails#

Description#

A new feature in NVIDIA GPU Manager for VMware vCenter 2.0.0 for filtering compatible drivers causes upgrade or migration from 1.x to 2.0.0 to fail. This issue occurs because one of the attributes added to the drivers to support this feature is required, but drivers that were downloaded in NVIDIA GPU Manager for VMware vCenter 1.x do not have this attribute. Specifically, to support this feature, the attributes Product Name, Branch Type, and End of Support were added to the drivers and the Branch Type attribute is required.

Workaround#

Use one of the following workarounds for this issue:

  • Delete all downloaded drivers from the Downloaded Drivers page in NVIDIA GPU Manager for VMware vCenter 1.x and retry the migration.

  • Deploy NVIDIA GPU Manager for VMware vCenter afresh.

    1. Install and configure a new NVIDIA GPU Manager for VMware vCenter 2.0.0 appliance.

    2. Unregister the old 1.x NVIDIA GPU Manager for VMware vCenter appliance from vCenter.

    3. Register the NVIDIA GPU Manager for VMware vCenter with vCenter.

Status#

Resolved in NVIDIA GPU Manager for VMware vCenter 2.1.0

To resolve this issue, the default value Not Available has been added for the branch type of any drivers that were downloaded in NVIDIA GPU Manager for VMware vCenter 1.x. As a result, after an upgrade or migration from NVIDIA GPU Manager for VMware vCenter 1.x, the branch type of any drivers that were downloaded in 1.x is shown as Not Available on the Downloaded Drivers page.

Ref. ##

5192469

2.0.0 Only: NVIDIA GPU Manager for VMware vCenter 2.0.0 does not show any drivers#

Description#

As a result of the addition of caching support, NVIDIA GPU Manager for VMware vCenter 2.0.0 does not show any drivers. This issue occurs because proxy-server details are not being used in NVIDIA Licensing Portal API calls. As a result, the proxy server is blocking these API calls, preventing NVIDIA GPU Manager for VMware vCenter from receiving a response from the NVIDIA Licensing Portal.

Status#

Resolved in NVIDIA GPU Manager for VMware vCenter 2.1.0

Ref. ##

5325966

2.0.0 Only: Downloaded drivers cannot be deleted after migration from NVIDIA GPU Manager for VMware vCenter 1.x to 2.0.0#

Description#

After migration from NVIDIA GPU Manager for VMware vCenter 1.x to 2.0.0, any drivers that were downloaded in NVIDIA GPU Manager for VMware vCenter 1.x are moved to the new appliance but cannot be deleted. This issue occurs because one of the attributes added to the drivers to support a new feature in NVIDIA GPU Manager for VMware vCenter 2.0.0 is required, but drivers that were downloaded in NVIDIA GPU Manager for VMware vCenter 1.x do not have this attribute. Any attempt to delete a driver that was downloaded in NVIDIA GPU Manager for VMware vCenter 1.x fails because the deletion request requires this attribute and, if it is missing, the deletion request is terminated.

Status#

Resolved in NVIDIA GPU Manager for VMware vCenter 2.1.0

Ref. ##

5347226

2.0.0 Only: NVIDIA GPU Manager for VMware vCenter 2.0.0 cannot resolve DNS names in the .local domain#

Description#

As a result of the upgrade of the base OS to Ubuntu 24.04.1, NVIDIA GPU Manager for VMware vCenter 2.0.0 cannot resolve DNS names in the .local domain. This issue occurs because Ubuntu 24.04.1 uses multicast DNS (mDNS) to resolve .local domain names. To resolve a .local domain name, the system first checks local entries and then tries mDNS on the local network. If no match is found, the lookup is stopped and doesn’t proceed to standard DNS, causing failures in resolving .local domain names through standard DNS servers.

Workaround#

  1. Use the web console option of the vCenter web client to log in as the user vcp_cli_user to the VM that hosts the NVIDIA GPU Manager for VMware vCenter virtual appliance.

  2. As the vcp_cli_user user, open the /etc/hosts file for editing in a plain-text editor such as vi or nano.

    Note

    Don’t use sudo.

  3. In the /etc/hosts file, add an entry with the IP and fully qualified domain name of the appliance.

    For example: 10.119.56.124 nv-gpu-mgr.example.local

  4. Save your changes and quit the editor.

  5. Repeat the attempt to register the NVIDIA GPU Manager for VMware vCenter on this vCenter server.

Status#

Resolved in NVIDIA GPU Manager for VMware vCenter 2.1.0

Ref. ##

5360714

Assignment of a static IP address fails if any properties are invalid or blank#

Description#

Network settings for a static IP address can be provided during the installation of the NVIDIA GPU Manager for VMware vCenter virtual appliance. However, these values cannot be validated before the VM that hosts the appliance is created. Therefore, if any field except DNS Server 2 is blank or if any field contains invalid data, a static IP address is not assigned to the VM. Instead, the VM obtains network settings from a DHCP server.

Workaround#

If the VM obtains network settings from a DHCP server, assign a static IP address to the VM.

  1. Register the NVIDIA GPU Manager for VMware vCenter administrator user.

  2. Update the network settings for the NVIDIA GPU Manager for VMware vCenter virtual appliance.

For instructions for how to perform these tasks, refer to GPU Manager for VMware vCenter User Guide.

Do not attempt to register the NVIDIA GPU Manager for VMware vCenter until a static IP address has been assigned to the VM that hosts the appliance.

Status#

Open

Ref. ##

4080509

Unregistering NVIDIA GPU Manager for VMware vCenter does not remove the NVIDIA GPU Manager drivers repository#

Description#

After NVIDIA GPU Manager for VMware vCenter is unregistered, the entry for NVIDIA GPU Manager drivers repository is not removed from vSphere Lifecycle Management (vLCM). This issue occurs if an NVIDIA GPU Manager for VMware vCenter for which no drivers are synchronized with vLCM is unregistered.

When this issue occurs, the following error message can be seen by selecting vSphere Client > Tasks:

A general system error occurred: Cannot find the content of online depot 
'https://nvidia-gpu-manager-appliance-ip/DriverRepo/index.xml';.
Either the depot's content has not been imported yet or has already been deleted 
or the depot was migrated from an old version of
vSphere Lifecycle Manager that does not support this operation.

Version#

This issue affects supported versions of VMware vSphere Hypervisor (ESXi) before 8.0 update 1.

Workaround#

Delete the entry in the table for NVIDIA GPU Manager drivers repository manually as explained in Modify a Download Source on the VMware Docs site.

Status#

Not an NVIDIA bug

Ref. ##

3974270

Unregistering NVIDIA GPU Manager for VMware vCenter does not remove downloaded NVIDIA GPU drivers from vLCM#

Description#

After NVIDIA GPU Manager for VMware vCenter is unregistered, the entries for downloaded NVIDIA GPU drivers are not removed from vSphere Lifecycle Management (vLCM). The downloaded drivers can still be seen by selecting vSphere Client > Lifecycle Manager > COMPONENTS.

Version#

This issue affects supported versions of VMware vSphere Hypervisor (ESXi) before 8.0 update 1.

Workaround#

Delete the entries for downloaded NVIDIA GPU drivers manually from vLCM as explained in Resetting the VMware Update Manager Database.

Caution

  • Resetting the Update Manager database is a destructive task. The following items are removed and must be reapplied after the reset:

    • Custom baselines (but not cluster images)

    • Custom download settings

    • Manually imported patches and ISO images

  • To prevent loss of data if the reset fails, back up your data before resetting the Update Manager database as follows:

    • Create a snapshot of the virtual appliance and, if the vCenter Server is part of a Linked Mode replication setup, create a snapshot of all replicating nodes.

      For instructions, refer to Take Snapshots of a Virtual Machine.

      If the reset fails, you can restore the affected virtual appliance and replicating nodes from their snapshots as explained in Revert a Virtual Machine Snapshot.

    • Note all custom configuration settings in Update Manager, for example, proxy settings, third-party download URLs, and customized baselines.

Status#

Not an NVIDIA bug