| Previous | Next |
| STATUS_HV_INVALID_PROXIMITY_DOMAIN_INFO | STATUS_HV_INACTIVE |
STATUS_HV_NO_DATA
The diagnostic path was valid, but there was nothing to read
STATUS_HV_NO_DATA is most useful when seen in a Hyper-V debugging or diagnostic path. It indicates absence of available data for the requested read, not necessarily failure of the guest workload being debugged.
Do not diagnose it from the NTSTATUS alone. The important context is the channel being read, the previous operation on that channel, and whether the transport was expected to have produced data by that point.
What to verify
- The debug or diagnostic endpoint being queried and whether it is enabled for the target partition.
- Whether the caller is polling before the hypervisor has emitted data.
- The last receive, reset, reconnect, or transport-state event on the same channel.
- Whether a timeout path should treat no data as a normal empty read or as a failed diagnostic session.
Useful distinction
Keep this separate from STATUS_HV_INACTIVE. STATUS_HV_NO_DATA says no data was available for the request; STATUS_HV_INACTIVE points to lack of receive activity on the physical debugging connection since the previous operation.
References
- Microsoft: Hyper-V TLFS
- Microsoft: Using NTSTATUS values
- Microsoft Open Specifications: NTSTATUS values
- ReactOS: ntstatus.h constant definitions
Looking for a different code? Search another status or error code.