| Previous | Next |
| STATUS_VID_INVALID_NUMA_SETTINGS | STATUS_VID_NOTIFICATION_QUEUE_ALREADY_ASSOCIATED |
STATUS_VID_INVALID_NUMA_NODE_INDEX
The NUMA node index is outside the host topology
STATUS_VID_INVALID_NUMA_NODE_INDEX is more precise than a general NUMA configuration failure: the specific node index supplied to VID is not valid on the host.
This can happen after migration, hardware replacement, BIOS NUMA changes, or a stale VM configuration that was valid on a different host.
VID received a NUMA node index that does not identify a node in the host topology visible to Hyper-V. Compare the stored or generated index with current host NUMA data, especially after hardware, firmware, migration, or configuration changes that may have altered topology.
What to inspect
- List the host NUMA nodes visible to Hyper-V and compare them with the requested index.
- Check cluster migration or import paths where a VM was configured on a host with a different topology.
- Verify whether NUMA node numbering changed after firmware, processor, or virtualization setting changes.
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.