| Previous | Next |
| STATUS_TPM_ZERO_EXHAUST_ENABLED | STATUS_HV_INVALID_HYPERCALL_INPUT |
STATUS_HV_INVALID_HYPERCALL_CODE
The call code is outside the guest-visible Hyper-V interface
STATUS_HV_INVALID_HYPERCALL_CODE means the hypervisor rejected the requested hypercall number before it performed the requested operation. It is not a failure reported by the guest workload running inside a VM. Hypercalls are the guest-to-hypervisor ABI, and the set that a partition may use depends on the interface and capabilities actually exposed by its hypervisor.
Do not treat a host version string or vendor label as proof that a hypercall is available. The Hyper-V TLFS says software should discover the interface and features exposed to the partition, then select a supported path. A nested VM can expose a smaller interface than a direct Hyper-V guest even when the outer host supports more functionality.
What to capture
- The hypercall code, control word, architecture and whether the call is simple, rep, or fast.
- The
HV#1interface result and the feature/privilege data visible to the calling partition. - Whether the VM is running nested and which layer owns the rejected call.
- The feature-detection branch that selected the hypercall instead of a fallback API.
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.