| Previous | Next |
| STATUS_VID_CHILD_GPA_PAGE_SET_CORRUPTED | STATUS_VID_INVALID_NUMA_NODE_INDEX |
STATUS_VID_INVALID_NUMA_SETTINGS
The configured NUMA topology does not match the host
STATUS_VID_INVALID_NUMA_SETTINGS is a configuration/topology mismatch. It means the requested virtual NUMA layout cannot be reconciled with the host NUMA topology that Hyper-V sees.
Microsoft documentation notes that Hyper-V attempts NUMA-aware placement and that NUMA spanning can let a VM use resources across nodes at a performance cost. If spanning is disabled or the requested layout exceeds a node, start or migration can fail.
The complete virtual NUMA configuration is inconsistent with the physical topology Hyper-V is trying to use, rather than one isolated node index being bad. Review per-node processor and memory limits, NUMA spanning policy, and the VM's virtual NUMA settings together before changing unrelated guest parameters.
What to inspect
- Compare VM memory, vCPU count, virtual NUMA node count, and maximum processors per NUMA node with the host topology.
- Check whether the host NUMA spanning setting changed since the VM was last configured.
- For clustered hosts, compare topology and processor compatibility across possible owners.
References
- Microsoft: NUMA and virtual machines in Hyper-V
- Microsoft: configure NUMA to optimize Hyper-V memory
- Microsoft: Hyper-V architecture
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.