An Azure service that is used to provision Windows and Linux virtual machines.
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
- 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^
- 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 witherr=-71while v7 works.^3^ In the upstream driver path,GDMA_VERIFY_VF_DRIVER_VERSIONis 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. - Meaning of HWC status
0xc00000bb0xC00000BBis the standard NTSTATUS valueSTATUS_NOT_SUPPORTED.^5^ It is an error-class NTSTATUS value because codes from0xC0000000through0xFFFFFFFFrepresent 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. - 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
- 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^
rdma-coreif RDMA/DPDK is involved: mismatched kernel andrdma-coreprovider IDs can cause the MANA VF probe to fail.^9^ Capture the following from matching v6 and v7 deployments:
Deviceuname -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'1414:00baconfirms that the MANA VF is exposed; increasing VF counters confirm traffic is using it.^10^ - 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
dmesgoutput 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
GDMA_VERIFY_VF_DRIVER_VERSIONrequest and host firmware/GDMA versions. Microsoft Support can collect guest diagnostics with consent and engage internal engineering teams when required.^11^ A Linuxsosreport is also useful, although collection should not be run during a critical window because it can rarely affect the VM.^12^
References
- Azure Accelerated Networking overview
- MANA support for existing VM series
- Azure V6 Deployment: MANA Driver Handshake Fails with err=-71, V7 Works - Microsoft Q&A
- RE: [PATCH net-next] net: mana: Add a driver for Microsoft Azure Network Adapter (MANA)
- 2.3.44 FSCTL_OFFLOAD_WRITE Reply
- Use NTSTATUS Values
- Validate and optimize after modernizing to the v6 and v7 VM series
- Microsoft Azure Network Adapter overview
- Microsoft Azure Network Adapter (MANA) and DPDK on Linux
- Linux VMs with the Microsoft Azure Network Adapter
- Microsoft Azure IaaS VM logs
- Collect support information from Azure Linux virtual machines