Allocate finite VMQ resources to the intended Hyper-V interfaces

Source facts

VMQ uses hardware filtering to deliver external packet data to virtual adapters. On supported hardware, a requesting virtual adapter receives a dedicated physical-adapter queue. Not every adapter supports VMQ, and supported adapters have a finite, hardware-dependent queue count. Microsoft checks support and count with Get-NetAdapterVmq. Its recommendation increases VMQ weight for interfaces with heavy inbound traffic, such as storage or migration interfaces. Microsoft documentation.

Applicability

Identify the physical adapters, driver capabilities, virtual interfaces, current weights, and actual inbound workload. Review VMQ support for the installed platform rather than assuming every host has the same queue inventory.

DSE recommendation

Compare the available queues with the interfaces requesting them. Have the virtualization owner identify which measured inbound workloads justify priority, and preserve the current weights before adjustment. Keep queue allocation separate from a bandwidth cap or an RSS processor-profile change.

Verification

Inspect the resulting queue allocation while representative inbound workloads run. Compare host processing and application behavior with the baseline, recording which interfaces receive queues. Resolve a missing queue or unexpected allocation before copying the weight settings to other hosts with different adapters.

Official references

Microsoft Learn: Network recommendations for a Hyper-V cluster. Source reviewed September 8, 2026.