| Previous | Next |
| ERROR_HV_INVALID_REGISTER_VALUE | ERROR_HV_NX_NOT_DETECTED |
ERROR_HV_INVALID_VTL_STATE
VTL enablement occurs first for the partition and then for each VP
ERROR_HV_INVALID_VTL_STATE means the requested Virtual Trust Level conflicts with current VSM state. A VTL must be supported and enabled for the partition, enabled on the target virtual processor, and used from a caller with sufficient privilege. Each VP maintains separate per-VTL execution state.
Capture the target VTL, caller VTL, partition enabled-VTL mask, VP enabled-VTL mask, and active VTL. Verify the ordered enablement sequence before setting protections, registers, or state pages. Treating VTL1 as merely another CPU mode misses the security hierarchy: lower VTLs cannot freely read or modify higher-VTL private state.
VSM state to inspect
- VSM capability and partition privilege flags.
- Enabled VTL set for the partition and target VP.
- Active VTL and caller privilege at the failing hypercall.
- Whether VTL protection and VP context initialization completed.
References
- Microsoft TLFS: VTL hierarchy and enablement sequence
- Microsoft TLFS: VTL state errors when starting VPs
- Microsoft TLFS: VTL-qualified VP state pages
Looking for a different code? Search another status or error code.