| Previous | Next |
| STATUS_FVE_TRANSIENT_STATE | STATUS_VOLMGR_INCOMPLETE_REGENERATION |
STATUS_VID_REMOTE_NODE_PARENT_GPA_PAGES_USED
Remote NUMA placement for the VM backing pages
STATUS_VID_REMOTE_NODE_PARENT_GPA_PAGES_USED points at host placement of the memory that backs guest physical address ranges. The VM can still run, but memory was spread across NUMA nodes instead of staying local to the preferred node.
Treat it as a capacity, topology, or placement signal. Hyper-V documentation notes that NUMA spanning can let a VM use memory from multiple physical NUMA nodes, but may reduce performance when locality matters.
VID placed parent-side pages backing guest physical addresses on remote NUMA nodes, so the VM can continue while memory locality may be worse than intended. Compare host NUMA capacity and placement with the VM's virtual NUMA layout and spanning policy when investigating performance; the status is a placement warning rather than evidence of corrupted guest memory.
What to inspect
- Compare VM memory and vCPU topology with the host NUMA topology and the current NUMA spanning setting.
- Check whether the VM was started when the preferred node lacked enough free memory.
- Correlate the status with observed performance counters before treating it as a functional start failure.
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.