Share via

Connectivity Issue for nvidia 595 drivers with NVads_A10_v5 sku's

Lukkari, Michael (Cognizant) 0 Reputation points
2026-06-05T20:35:08.4766667+00:00

Currently having connectivity issues with nvidia 595 drivers which are required for application that is being deployed on VM with the sku NVads_A10_v5. This sku is supposed to compatible with these drivers. Are there some recommended steps that the community would recommend to be followed?

Azure Virtual Machines
Azure Virtual Machines

An Azure service that is used to provision Windows and Linux virtual machines.

1 answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-06-05T20:35:34.7133333+00:00

    For NVadsA10_v5, only specific NVIDIA vGPU driver branches are supported and must be used; using an unsupported branch such as vGPU 20 (595.xx) can cause issues.

    Key points from the supported matrix:

    • NVadsA10_v5 supports GRID/vGPU 17.x or higher, but:
      • vGPU20 (595.xx Linux/Windows drivers) is not yet supported on NVadsA10_v5.
      • vGPU18 is the latest explicitly supported vGPU branch for NVadsA10_v5 and is available in Public, China, and Azure Government regions only.
    • vGPU20 is currently supported only on NCv6 RTX PRO 6000 BSE and NCasT4_v3 series, not on NVadsA10_v5.

    Given this, recommended steps are:

    1. Verify driver branch and SKU support
      • If using the 595.xx (vGPU20) driver on NVadsA10_v5, roll back to the supported vGPU18 driver for this SKU:
        • On Linux: use the vGPU18 GRID driver for NVadsA10_v5 from the NVIDIA GRID/vGPU section for Linux N‑series VMs.
        • On Windows: use the vGPU18 GRID driver for NVadsA10_v5 from the NVIDIA GRID/vGPU section for Windows N‑series VMs.
    2. Ensure correct OS and distribution support
      • On Linux, ensure the guest OS is one of the supported distributions for the provided GRID/vGPU driver (for example, Ubuntu 20.04/22.04/24.04 LTS, RHEL 8.x/9.x, SLES 12/15, Rocky 8.4) as listed in the supported distributions table.
      • Mismatched OS/distribution and driver versions can cause instability or connectivity issues.
    3. Use the Azure-provided vGPU drivers where possible
      • For NVadsA10_v5, use the Azure‑redistributed GRID/vGPU drivers (vGPU18) rather than generic NVIDIA packages, because these are validated for Azure hosts and include the correct licensing and compatibility.
    4. Avoid mixing unsupported branches
      • The latest major driver branch (n) is only backward compatible with n‑1. Running n‑2 or older on hosts or guests when Azure rolls out a newer branch can cause failures.
      • Ensure the guest driver branch matches the supported branch for NVadsA10_v5 (currently vGPU18, not vGPU20).
    5. If issues persist on a supported driver
      • Confirm that Secure Boot and vTPM are disabled on Linux VMs if using CUDA/vGPU drivers, as installation can hang when they are enabled.
      • For Windows, consider using the NVIDIA GPU Driver Extension for Windows N‑series VMs, which installs the appropriate GRID driver for the SKU, then verify extension status and logs if there are issues.

    If the application strictly requires the 595 (vGPU20) branch, it is currently incompatible with NVadsA10_v5 according to the support matrix; consider using a SKU that supports vGPU20 (NCv6 RTX PRO 6000 BSE or NCasT4_v3) or working with the application vendor to validate against the supported vGPU18 branch on NVadsA10_v5.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.