| Previous | Next |
| STATUS_HV_OBJECT_IN_USE | STATUS_HV_NO_DATA |
STATUS_HV_INVALID_PROXIMITY_DOMAIN_INFO
The NUMA proximity information does not match the topology Hyper-V accepts
STATUS_HV_INVALID_PROXIMITY_DOMAIN_INFO points to topology metadata. A proximity domain describes locality relationships, usually between processors and memory in a NUMA system. Hyper-V uses such information when exposing or validating a partition topology, scheduling model, or memory placement policy.
Diagnose the NUMA model rather than treating the status as a generic VM start failure. Bad node identifiers, duplicate domains, missing memory affinity, impossible processor-to-domain mappings, or stale topology after host CPU/memory changes can all make an otherwise reasonable VM configuration invalid.
What to compare
- The host NUMA topology reported by firmware and by Windows after boot.
- The VM or partition configuration that maps virtual processors and memory to proximity domains.
- Any CPU-group, hot-add, dynamic-memory, or host-firmware change since the configuration was created.
- Whether the failing environment is nested, where the exposed topology can be different from the physical host.
Useful distinction
This status is narrower than a general processor or memory error. It says the locality description itself is invalid, so changing unrelated VM settings may hide the symptom without fixing the topology mismatch.
References
- Microsoft: Hyper-V architecture
- Microsoft: Windows Hypervisor Platform API
- Linux kernel documentation: Hyper-V overview
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.