{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-196-compare-virtual-numa-topology-with-the-host-before-changing-memory-placement/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-196-compare-virtual-numa-topology-with-the-host-before-changing-memory-placement/", "slug": "dse-20260908-196-compare-virtual-numa-topology-with-the-host-before-changing-memory-placement", "url": "https://update.dsesecurity.com/updates/dse-20260908-196-compare-virtual-numa-topology-with-the-host-before-changing-memory-placement/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-196-compare-virtual-numa-topology-with-the-host-before-changing-memory-placement.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-196-compare-virtual-numa-topology-with-the-host-before-changing-memory-placement/" }, "title": "Compare virtual NUMA topology with the host before changing memory placement", "summary": "Which host and VM NUMA information should be compared before a topology change?", "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:13:55+00:00", "modified_at": "2026-09-08T18:26:32+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 1, "word_count": 196, "potentially_affected": "Administrators configuring NUMA topology for Hyper-V workloads.", "dse_recommendation": "Create a host-to-VM topology comparison and record the problem the proposed change is intended to address.", "primary_source": { "name": "Configure NUMA to Optimize Hyper-V Memory", "url": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/configure-non-uniform-memory-access", "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

Microsoft exposes host NUMA-node information through Get-VMHostNumaNode, including logical cores and memory available per node. A VM’s virtual NUMA configuration controls node count, processors per node, and memory per node. By default, the VM uses the host’s topology. The host NUMA-spanning setting applies only where the host has multiple NUMA nodes. Microsoft documentation.

\n

Applicability

\n

Identify the physical topology, guest workload, current virtual topology, memory configuration, and intended migration hosts. Review the source’s platform requirements and the application’s NUMA guidance before changing placement settings.

\n

DSE recommendation

\n

Create a host-to-VM topology comparison and record the problem the proposed change is intended to address. Ask the application and virtualization owners to review node size and memory assumptions. Preserve the original configuration and define a representative workload measurement before making an adjustment.

\n

Verification

\n

Inspect the VM’s exposed topology and compare its placement with the approved design. Use the documented performance counters and application measurements during a controlled workload run. Record the physical host used for each test and revisit the result if the VM moves to a materially different topology.

\n

Official references

\n

Microsoft Learn: Configure NUMA to Optimize Hyper-V Memory. Source reviewed September 8, 2026.

", "content_text": "Source facts\nMicrosoft exposes host NUMA-node information through Get-VMHostNumaNode, including logical cores and memory available per node. A VM’s virtual NUMA configuration controls node count, processors per node, and memory per node. By default, the VM uses the host’s topology. The host NUMA-spanning setting applies only where the host has multiple NUMA nodes. Microsoft documentation.\nApplicability\nIdentify the physical topology, guest workload, current virtual topology, memory configuration, and intended migration hosts. Review the source’s platform requirements and the application’s NUMA guidance before changing placement settings.\nDSE recommendation\nCreate a host-to-VM topology comparison and record the problem the proposed change is intended to address. Ask the application and virtualization owners to review node size and memory assumptions. Preserve the original configuration and define a representative workload measurement before making an adjustment.\nVerification\nInspect the VM’s exposed topology and compare its placement with the approved design. Use the documented performance counters and application measurements during a controlled workload run. Record the physical host used for each test and revisit the result if the VM moves to a materially different topology.\nOfficial references\nMicrosoft Learn: Configure NUMA to Optimize Hyper-V Memory. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nMicrosoft exposes host NUMA-node information through Get-VMHostNumaNode, including logical cores and memory available per node. A VM’s virtual NUMA configuration controls node count, processors per node, and memory per node. By default, the VM uses the host’s topology. The host NUMA-spanning setting applies only where the host has multiple NUMA nodes. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/configure-non-uniform-memory-access).\n\n## Applicability\n\nIdentify the physical topology, guest workload, current virtual topology, memory configuration, and intended migration hosts. Review the source’s platform requirements and the application’s NUMA guidance before changing placement settings.\n\n## DSE recommendation\n\nCreate a host-to-VM topology comparison and record the problem the proposed change is intended to address. Ask the application and virtualization owners to review node size and memory assumptions. Preserve the original configuration and define a representative workload measurement before making an adjustment.\n\n## Verification\n\nInspect the VM’s exposed topology and compare its placement with the approved design. Use the documented performance counters and application measurements during a controlled workload run. Record the physical host used for each test and revisit the result if the VM moves to a materially different topology.\n\n## Official references\n\n[Microsoft Learn: Configure NUMA to Optimize Hyper-V Memory](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/configure-non-uniform-memory-access). 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-196-compare-virtual-numa-topology-with-the-host-before-changing-memory-placement/", "url": "https://update.dsesecurity.com/updates/dse-20260908-196-compare-virtual-numa-topology-with-the-host-before-changing-memory-placement/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-196-compare-virtual-numa-topology-with-the-host-before-changing-memory-placement/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Compare virtual NUMA topology with the host before changing memory placement", "item": "https://update.dsesecurity.com/updates/dse-20260908-196-compare-virtual-numa-topology-with-the-host-before-changing-memory-placement/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-196-compare-virtual-numa-topology-with-the-host-before-changing-memory-placement/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-196-compare-virtual-numa-topology-with-the-host-before-changing-memory-placement/", "url": "https://update.dsesecurity.com/updates/dse-20260908-196-compare-virtual-numa-topology-with-the-host-before-changing-memory-placement/", "headline": "Compare virtual NUMA topology with the host before changing memory placement", "description": "Which host and VM NUMA information should be compared before a topology change?", "abstract": "Which host and VM NUMA information should be compared before a topology change?", "articleBody": "Source facts\nMicrosoft exposes host NUMA-node information through Get-VMHostNumaNode, including logical cores and memory available per node. A VM’s virtual NUMA configuration controls node count, processors per node, and memory per node. By default, the VM uses the host’s topology. The host NUMA-spanning setting applies only where the host has multiple NUMA nodes. Microsoft documentation.\nApplicability\nIdentify the physical topology, guest workload, current virtual topology, memory configuration, and intended migration hosts. Review the source’s platform requirements and the application’s NUMA guidance before changing placement settings.\nDSE recommendation\nCreate a host-to-VM topology comparison and record the problem the proposed change is intended to address. Ask the application and virtualization owners to review node size and memory assumptions. Preserve the original configuration and define a representative workload measurement before making an adjustment.\nVerification\nInspect the VM’s exposed topology and compare its placement with the approved design. Use the documented performance counters and application measurements during a controlled workload run. Record the physical host used for each test and revisit the result if the VM moves to a materially different topology.\nOfficial references\nMicrosoft Learn: Configure NUMA to Optimize Hyper-V Memory. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:13:55+00:00", "dateModified": "2026-09-08T18:26:32+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-196-compare-virtual-numa-topology-with-the-host-before-changing-memory-placement/" }, "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-196-compare-virtual-numa-topology-with-the-host-before-changing-memory-placement/#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": "Compare virtual NUMA topology with the host before changing memory placement" }, "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": "Configure NUMA to Optimize Hyper-V Memory", "url": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/configure-non-uniform-memory-access" } } ] } }