| Previous | Next |
| ERROR_VID_CHILD_GPA_PAGE_SET_CORRUPTED | ERROR_VID_INVALID_NUMA_NODE_INDEX |
ERROR_VID_INVALID_NUMA_SETTINGS
ERROR_VID_INVALID_NUMA_SETTINGS is HRESULT 0xC037000F in the Hyper-V virtual NUMA configuration area of the Windows virtualization stack. It applies to the relationship between configured virtual NUMA nodes and the physical host NUMA topology.
Where the result originates
The configured node count, processors per node, memory per node, or related limits cannot be represented on this host. This is a configuration validity failure, not merely a performance advisory.
Neighboring result: INVALID_NUMA_NODE_INDEX identifies one bad node reference. REMOTE_NODE_PARENT_GPA_PAGES_USED can describe a running but nonlocal placement. INVALID_NUMA_SETTINGS prevents a valid start/configuration transition.
Build an incident record
| Evidence | Why it changes the diagnosis |
|---|---|
| Host topology | Record physical NUMA nodes, logical processors, and memory per node. |
| VM topology | Keep vCPU count, virtual NUMA nodes, max processors/node, and max memory/node. |
| Dynamic Memory | Record whether enabled and how startup/maximum memory interact with virtual NUMA. |
| Mobility target | Capture source/destination host topology after migration or hardware change. |
Run narrow checks
- Return virtual NUMA settings to automatic defaults as a controlled comparison.
- Ensure no configured node exceeds host-supported processor or memory limits.
- Compare every cluster node if the VM can move.
- Do not treat NUMA spanning as a universal correction for an invalid topology.
Evaluate the condition with the same workload and VM size while varying only documented NUMA configuration or placement. Record topology on every intended host rather than inferring it from socket labels.
Interpret three controls
| Control | Interpretation | Hold constant |
|---|---|---|
| Local versus cross-node placement | Measure workload latency and throughput under both placements. This distinguishes a correctness failure from a performance advisory. | Hold guest workload and processor affinity stable while comparing it. |
| Automatic versus explicit virtual NUMA | If automatic topology removes it, compare each overridden node count, processor limit, and memory limit with host topology. | Keep VM vCPU count, memory, Dynamic Memory mode, and workload fixed. |
| Every intended destination host | A result that follows one node indicates a host-local topology or placement constraint. | Use the same VM configuration and record each host NUMA layout in the test. |
Keep neighboring states separate
A restart can change placement and make it disappear once without proving the topology is valid or performance is stable. Close the investigation only after repeatable placement and workload comparisons.
Prove the correction
The VM starts on every intended host with a topology that matches the workload design and remains valid after restart/migration.
Technical references
- Microsoft Open Specifications: HRESULT values — used to interpret this result.
- Microsoft: NUMA and Hyper-V virtual machines — used to interpret this result.
- Microsoft: configure virtual NUMA — used to interpret this result.
- Microsoft: troubleshoot Hyper-V VM performance — used to interpret this result.
Looking for a different code? Search another status or error code.