| Previous | Next |
| ERROR_NDIS_OFFLOAD_PATH_REJECTED | ERROR_HV_INVALID_HYPERCALL_INPUT |
ERROR_HV_INVALID_HYPERCALL_CODE
What is being rejected
This status belongs to the Hyper-V hypercall ABI, before a particular operation has begun. The low 16 bits of the hypercall control value select the requested call. A code can be unknown because the guest used an operation from a different TLFS revision, called an optional interface that is not exposed by this hypervisor, or constructed the control value for the wrong ABI.
It is different from ERROR_HV_INVALID_HYPERCALL_INPUT. Here the call selector itself is not recognized; the latter says that a recognized call was invoked with an invalid control-word encoding.
What to capture
- Record the complete 64-bit hypercall control value, not only the symbolic call name.
- Check the call code against the Hyper-V TLFS version and the features actually advertised to the guest.
- Verify that the guest uses the architecturally provided hypercall interface rather than copied or substituted call-page code.
- Do not retry an unchanged call code. The useful next step is to correct feature negotiation or the call wrapper.
Microsoft Hyper-V TLFS: Hypercall interface · Linux Hyper-V TLFS header
Looking for a different code? Search another status or error code.