| Previous | Next |
| STATUS_HV_PROPERTY_VALUE_OUT_OF_RANGE | STATUS_HV_PARTITION_TOO_DEEP |
STATUS_HV_INSUFFICIENT_MEMORY
The failed allocation is in the hypervisor, not simply in the guest
STATUS_HV_INSUFFICIENT_MEMORY reports that Hyper-V could not obtain memory from an internal hypervisor pool for the requested operation. It should not be diagnosed only as a lack of RAM inside the guest VM; the failing allocation may belong to partition metadata, virtual processor state, mapping structures, message resources, or device-assignment state maintained by the host.
The useful question is which Hyper-V object was being created or expanded. A partition, VP, GPA mapping, CPU group, device domain, or nested-virtualization feature can consume different host-side resources and can fail at different points.
What to collect
- The operation being performed: partition creation, VP creation, memory mapping, device assignment, restore, or nested-virtualization setup.
- Host memory pressure, commit limits, VM memory configuration, dynamic-memory settings, and concurrent VM activity.
- Whether the failure follows a leak pattern after repeated create/destroy cycles.
- Adjacent Hyper-V worker, VMMS, or virtualization stack events that name the object being allocated.
Useful distinction
Do not merge it with STATUS_INSUFFICIENT_RESOURCES from a driver or service unless the failing layer is known. This NTSTATUS names a Hyper-V facility status and is most useful when correlated with the exact hypercall or virtualization-management operation.
References
- Microsoft: Hyper-V architecture
- Microsoft: Windows Hypervisor Platform API
- Microsoft Open Specifications: NTSTATUS values
- Linux kernel documentation: Hyper-V overview
Looking for a different code? Search another status or error code.