# Compare virtual NUMA topology with the host before changing memory placement

> Which host and VM NUMA information should be compared before a topology change?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260908-196-compare-virtual-numa-topology-with-the-host-before-changing-memory-placement/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-08T18:13:55+00:00
- Modified: 2026-09-08T18:26:32+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 host and VM NUMA information should be compared before a topology change?

## 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.

## Article

## Source facts

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](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/configure-non-uniform-memory-access).

## Applicability

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.

## DSE recommendation

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.

## Verification

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.

## Official references

[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.

## Primary reference

- Name: Configure NUMA to Optimize Hyper-V Memory
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/configure-non-uniform-memory-access
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Compare virtual NUMA topology with the host before changing memory placement,” DSE Security, https://update.dsesecurity.com/updates/dse-20260908-196-compare-virtual-numa-topology-with-the-host-before-changing-memory-placement/
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.