| Previous | Next |
| STATUS_HV_INVALID_ALIGNMENT | STATUS_HV_ACCESS_DENIED |
STATUS_HV_INVALID_PARAMETER
The call reached Hyper-V, but one operation-specific field is invalid
STATUS_HV_INVALID_PARAMETER differs from an invalid hypercall code or invalid control encoding: Hyper-V recognized the call form and then rejected a value defined by that operation. The useful diagnostic unit is therefore the exact hypercall and its field-level contract, not the NTSTATUS value alone.
For example, HvCallPostMessage rejects a zero message type, a type with its high bit set, or a payload larger than its documented limit. Other hypercalls have different validation rules. Preserve the raw input structure and decode it according to the matching call definition rather than applying a generic “bad parameter” fix.
Evidence to retain
- The exact hypercall name/code and a decoded copy of its input parameters.
- Field values that are reserved, length-limited, enumerated, or required to be zero.
- The return status and, for rep calls, the number of completed elements.
- The interface version and feature bits that control whether a field is legal.
References
- Microsoft: Hyper-V hypercall interface
- Microsoft: Hyper-V feature and interface discovery
- Linux source: Hyper-V guest initialization
Looking for a different code? Search another status or error code.