# Allocate finite VMQ resources to the intended Hyper-V interfaces

> Which interfaces should receive VMQ priority when hardware queue capacity is limited?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260908-166-allocate-finite-vmq-resources-to-the-intended-hyper-v-interfaces/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-08T18:14:25+00:00
- Modified: 2026-09-08T18:26:31+00:00
- Last reviewed by DSE: 2026-09-08
- Resource type: Guide
- DSE priority: Information
- Topics: IT, Networks & Infrastructure
- Reading time: 1 minutes

## What you need to know

Which interfaces should receive VMQ priority when hardware queue capacity is limited?

## Potentially affected

Administrators evaluating VMQ-capable physical adapters on Hyper-V hosts.

## DSE recommendation

Compare the available queues with the interfaces requesting them.

## Article

## 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](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/failover-cluster-network-recommendations).

## 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](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/failover-cluster-network-recommendations). Source reviewed September 8, 2026.

## Primary reference

- Name: Network recommendations for a Hyper-V cluster
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/failover-cluster-network-recommendations
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Allocate finite VMQ resources to the intended Hyper-V interfaces,” DSE Security, https://update.dsesecurity.com/updates/dse-20260908-166-allocate-finite-vmq-resources-to-the-intended-hyper-v-interfaces/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.