| Previous | Next |
| STATUS_VID_RESERVE_PAGE_SET_TOO_SMALL | STATUS_VID_MBP_COUNT_EXCEEDED_LIMIT |
STATUS_VID_MBP_ALREADY_LOCKED_USING_RESERVED_PAGE
The memory-block page is already locked through reserve pages
STATUS_VID_MBP_ALREADY_LOCKED_USING_RESERVED_PAGE indicates an overlapping or repeated lock attempt on a memory-block page that already uses reserve-page backing.
The page is already locked with reserve-page backing, so another lock or map request would overlap an established VID state. Compare the second request with the original page index and reserve-page allocation instead of treating the failure as a generic shortage of host memory.
This status helps separate “not enough reserve pages” from “the same memory-block page is already in a locked state.” The investigation should focus on duplicate or overlapping operations.
What to inspect
- Check whether the same GPA page range was submitted twice.
- Find whether a previous lock was expected to be released before the second request.
- Look for overlapping device-assignment, migration, or save/restore operations against the same range.
References
- Microsoft: WHvMapGpaRange
- Microsoft: Hyper-V live migration troubleshooting
- Microsoft: Windows Hypervisor Platform API definitions
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.
