| Previous | Next |
| STATUS_VID_MESSAGE_QUEUE_CLOSED | STATUS_VID_STOP_PENDING |
STATUS_VID_VIRTUAL_PROCESSOR_LIMIT_EXCEEDED
The partition reached its virtual processor limit
STATUS_VID_VIRTUAL_PROCESSOR_LIMIT_EXCEEDED is a partition-capacity failure. The requested vCPU cannot be added because the limit for that partition or host configuration has already been reached.
The partition already has the maximum number of virtual processors allowed by its current configuration or host constraints. Compare the requested VP count with partition setup and Hyper-V processor limits before investigating the state of individual vCPUs, because no additional VP can be created in this condition.
This is different from invalid processor state: the request is about the number of virtual processors, not the state of one existing VP.
What to inspect
- Compare requested vCPU count with VM version, host policy, licensing, and NUMA topology limits.
- Check whether Dynamic Memory or NUMA placement constraints are being diagnosed as a CPU limit by a higher layer.
- Confirm that failed creation attempts did not leave partially-created VP objects counted against the limit.
References
- Microsoft: WHvCreateVirtualProcessor
- Microsoft: Windows Hypervisor Platform API definitions
- Microsoft: NUMA and virtual machines in Hyper-V
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.