V6 vs V7 VM deployment differences

Avinash Jadhav 0 Reputation points
2026-11-19T15:52:42.8566667+00:00

1.Does Azure V6 (Standard, 2 vCPU) expose the same MANA GDMA protocol version and capabilities as Azure V7?

2.Is there any known limitation with the MANA HWC initialization or GDMA_VERIFY_VF_DRIVER_VERSION request on V6?

3.What does HWC response status 0xc00000bb indicate in the Azure MANA implementation?

4.Are there known differences in MANA firmware, host-side GDMA implementation, or HWC timeout configuration between V6 and V7?

5.Is there a known compatibility requirement for the guest Linux 6.6 MANA driver on V6?

6.Can the Azure team inspect host-side HWC request/response logs for the affected VM deployments?

Azure Virtual Machines
Azure Virtual Machines

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

0 comments No comments

1 answer

Sort by: Newest
  1. AI answer

    2026-11-19T16:09:11.3966667+00:00

    Kernel 6.6 is supported for MANA only in the documented Azure Linux 3 case; for another distribution or a custom kernel, test its listed vendor kernel or Linux 6.14+ before treating the v6 failure as a host-generation defect.^1^

    Answers to the six questions

    1. Does v6 expose the same GDMA protocol and capabilities as v7? Azure does not publicly document that v6 and v7 expose identical MANA/GDMA protocol versions, firmware revisions, or capability sets. The documented boundary is:
      • Intel v6 or later runs on MANA-capable hardware.
      • Hardware eligibility alone is insufficient; the guest OS must support MANA.
      • Networking limits are tied to VM size, not the underlying hardware.^2^
      Therefore, successful initialization on v7 does not by itself prove that the same guest-driver build is supported identically on every v6 host implementation.
    2. Known v6 limitation involving HWC initialization or GDMA_VERIFY_VF_DRIVER_VERSION? No public Microsoft documentation supplied here identifies a general v6 limitation for that request. There is, however, a closely matching public report where a v6 deployment fails the MANA handshake with err=-71 while v7 works.^3^ In the upstream driver path, GDMA_VERIFY_VF_DRIVER_VERSION is issued during probe; a nonzero response status causes initialization to fail with -EPROTO (-71).^4^ That establishes a failed version/capability negotiation, but not whether the cause is guest versioning, host firmware, or a host deployment issue.
    3. Meaning of HWC status 0xc00000bb 0xC00000BB is the standard NTSTATUS value STATUS_NOT_SUPPORTED.^5^ It is an error-class NTSTATUS value because codes from 0xC0000000 through 0xFFFFFFFF represent errors.^6^ In this HWC exchange, it means the receiving side rejected the requested operation or requested version/capability as unsupported. Public documentation does not define a more specific MANA-only interpretation, so the code alone cannot identify which version field or capability caused the rejection.
    4. Firmware, host GDMA, or timeout differences between v6 and v7 No public specification here provides per-generation:
      • MANA firmware versions
      • Host-side GDMA implementation revisions
      • HWC timeout values
      • A v6-versus-v7 protocol matrix
      Microsoft’s migration guidance explicitly requires validating that the MANA driver loads and is healthy on both v6 and v7, rather than promising identical internal implementations.^7^
    5. Linux 6.6 compatibility Kernel version alone is not a universal support declaration:
      • Azure Linux 3: kernel series 6.6, any version, is listed for MANA.
      • Other endorsed distributions have their own minimum vendor builds.
      • For non-endorsed distributions or custom kernels, Microsoft recommends Linux 6.14 or later.^1^
      • DPDK on MANA requires 6.14+ or backports of the relevant Ethernet and InfiniBand drivers.^8^
      Also check rdma-core if RDMA/DPDK is involved: mismatched kernel and rdma-core provider IDs can cause the MANA VF probe to fail.^9^ Capture the following from matching v6 and v7 deployments:
         uname -a
         cat /etc/os-release
         lspci -nn -d 1414:00ba
         modinfo mana | grep -E 'filename|version|srcversion'
         dmesg -T | grep -Ei 'mana|gdma|hwc|netvsc'
         ip -details link
         ethtool -i eth0
         ethtool -S eth0 | grep -E '^[[:space:]]+vf'
      
      Device 1414:00ba confirms that the MANA VF is exposed; increasing VF counters confirm traffic is using it.^10^
    6. Can Azure inspect host-side HWC logs? Yes, but this requires an Azure support case; host-side firmware/HWC telemetry is not customer-accessible. Open Azure portal → Help + support → Create a support request and provide:
      • Subscription/resource identifiers through the secure case—not in a public post
      • Exact v6 and v7 SKUs, region and availability zone
      • Deployment and failure timestamps in UTC
      • Image publisher/offer/SKU/version
      • Full kernel package version and whether it is vendor-provided or custom
      • Complete dmesg output around MANA/GDMA initialization
      • A successful v7 deployment and failing v6 deployment created from the same image
      • Whether Accelerated Networking, RDMA, or DPDK is enabled
      Request correlation against host-side MANA HWC request/response logs, including the decoded GDMA_VERIFY_VF_DRIVER_VERSION request and host firmware/GDMA versions. Microsoft Support can collect guest diagnostics with consent and engage internal engineering teams when required.^11^ A Linux sos report is also useful, although collection should not be run during a critical window because it can rarely affect the VM.^12^

    References

    1. Azure Accelerated Networking overview
    2. MANA support for existing VM series
    3. Azure V6 Deployment: MANA Driver Handshake Fails with err=-71, V7 Works - Microsoft Q&A
    4. RE: [PATCH net-next] net: mana: Add a driver for Microsoft Azure Network Adapter (MANA)
    5. 2.3.44 FSCTL_OFFLOAD_WRITE Reply
    6. Use NTSTATUS Values
    7. Validate and optimize after modernizing to the v6 and v7 VM series
    8. Microsoft Azure Network Adapter overview
    9. Microsoft Azure Network Adapter (MANA) and DPDK on Linux
    10. Linux VMs with the Microsoft Azure Network Adapter
    11. Microsoft Azure IaaS VM logs
    12. Collect support information from Azure Linux virtual machines
    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.