| Previous | Next |
| ERROR_VID_INVALID_NUMA_SETTINGS | ERROR_VID_NOTIFICATION_QUEUE_ALREADY_ASSOCIATED |
ERROR_VID_INVALID_NUMA_NODE_INDEX
ERROR_VID_INVALID_NUMA_NODE_INDEX is HRESULT 0xC0370010 in the Hyper-V NUMA node addressing area of the Windows virtualization stack. It applies to a NUMA node index supplied to VID that is outside the current host or configured topology.
State and ownership model
The referenced node does not exist in the topology generation used by the operation. Look for off-by-one errors, stale cached topology, and assumptions carried across hosts.
Neighboring result: INVALID_NUMA_SETTINGS concerns the full topology; INVALID_NUMA_NODE_INDEX isolates one numeric node reference.
Capture before changing anything
| Evidence | Why it changes the diagnosis |
|---|---|
| Requested index | Record the numeric node index and operation. |
| Enumerated topology | Keep node count and identifiers from the same host and time. |
| Cache generation | Record when topology was queried relative to hardware, firmware, or migration changes. |
| Loop bounds | Capture zero/one-based conversions and selected-node algorithm. |
Reduce the case safely
- Validate index < current node count immediately before use.
- Do not persist host-local NUMA indexes across migration.
- Test single-node and sparse/high-node-count hosts.
- Prefer stable topology data structures over inferred socket numbers.
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.
What comparison can tell you
| Control | Interpretation | Hold constant |
|---|---|---|
| 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. |
| 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. |
Do not erase the evidence
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.
Closure criteria
All selections come from current enumeration, boundary tests reject node_count, and migration refreshes host-local indexes.
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.