{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-166-allocate-finite-vmq-resources-to-the-intended-hyper-v-interfaces/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-166-allocate-finite-vmq-resources-to-the-intended-hyper-v-interfaces/", "slug": "dse-20260908-166-allocate-finite-vmq-resources-to-the-intended-hyper-v-interfaces", "url": "https://update.dsesecurity.com/updates/dse-20260908-166-allocate-finite-vmq-resources-to-the-intended-hyper-v-interfaces/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-166-allocate-finite-vmq-resources-to-the-intended-hyper-v-interfaces.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-166-allocate-finite-vmq-resources-to-the-intended-hyper-v-interfaces/" }, "title": "Allocate finite VMQ resources to the intended Hyper-V interfaces", "summary": "Which interfaces should receive VMQ priority when hardware queue capacity is limited?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "network-infrastructure", "label": "Networks & infrastructure", "alt": "Resilient network core with engineered blue and gold data paths.", "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "slug": "networks-infrastructure", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-08T18:14:25+00:00", "modified_at": "2026-09-08T18:26:31+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 1, "word_count": 196, "potentially_affected": "Administrators evaluating VMQ-capable physical adapters on Hyper-V hosts.", "dse_recommendation": "Compare the available queues with the interfaces requesting them.", "primary_source": { "name": "Network recommendations for a Hyper-V cluster", "url": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/failover-cluster-network-recommendations", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

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.

\n

Applicability

\n

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.

\n

DSE recommendation

\n

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.

\n

Verification

\n

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.

\n

Official references

\n

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

", "content_text": "Source facts\nVMQ 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.\nApplicability\nIdentify 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.\nDSE recommendation\nCompare 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.\nVerification\nInspect 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.\nOfficial references\nMicrosoft Learn: Network recommendations for a Hyper-V cluster. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nVMQ 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).\n\n## Applicability\n\nIdentify 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.\n\n## DSE recommendation\n\nCompare 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.\n\n## Verification\n\nInspect 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.\n\n## Official references\n\n[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." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260908-166-allocate-finite-vmq-resources-to-the-intended-hyper-v-interfaces/", "url": "https://update.dsesecurity.com/updates/dse-20260908-166-allocate-finite-vmq-resources-to-the-intended-hyper-v-interfaces/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-166-allocate-finite-vmq-resources-to-the-intended-hyper-v-interfaces/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Allocate finite VMQ resources to the intended Hyper-V interfaces", "item": "https://update.dsesecurity.com/updates/dse-20260908-166-allocate-finite-vmq-resources-to-the-intended-hyper-v-interfaces/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-166-allocate-finite-vmq-resources-to-the-intended-hyper-v-interfaces/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-166-allocate-finite-vmq-resources-to-the-intended-hyper-v-interfaces/", "url": "https://update.dsesecurity.com/updates/dse-20260908-166-allocate-finite-vmq-resources-to-the-intended-hyper-v-interfaces/", "headline": "Allocate finite VMQ resources to the intended Hyper-V interfaces", "description": "Which interfaces should receive VMQ priority when hardware queue capacity is limited?", "abstract": "Which interfaces should receive VMQ priority when hardware queue capacity is limited?", "articleBody": "Source facts\nVMQ 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.\nApplicability\nIdentify 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.\nDSE recommendation\nCompare 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.\nVerification\nInspect 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.\nOfficial references\nMicrosoft Learn: Network recommendations for a Hyper-V cluster. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:14:25+00:00", "dateModified": "2026-09-08T18:26:31+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-166-allocate-finite-vmq-resources-to-the-intended-hyper-v-interfaces/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260908-166-allocate-finite-vmq-resources-to-the-intended-hyper-v-interfaces/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Allocate finite VMQ resources to the intended Hyper-V interfaces" }, "articleSection": [ "IT", "Networks & Infrastructure" ], "keywords": [ "IT", "Networks & Infrastructure", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 196, "timeRequired": "PT1M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Network recommendations for a Hyper-V cluster", "url": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/failover-cluster-network-recommendations" } } ] } }