Geoff Chappell, Software Analyst
The HV_IMPLEMENTATION_LIMITS structure collects the information that a hypervisor’s cpuid leaf 0x40000005 produces in the eax, ebx, ecx and edx registers.
The HV_IMPLEMENTATION_LIMITS is defined in Windows 8.1 and higher, having developed from an inline definition for the MsHvImplementationLimits member of the HV_CPUID_RESULT union.
The HV_IMPLEMENTATION_LIMITS structure itself is not documented. Some of its members, having previously been defined in the HV_CPUID_RESULT, are documented in the Windows Driver Kit (WDK) for Windows 7, which also provided a C-language definition in the HVGDK.H header file.
The structure anyway repackages material that Microsoft does document—or represents as documented—in the Hypervisor Top-Level Functional Specification. If the structure or its members’ previous definitions have become undocumented, it may be just that Microsoft regards the structure as no more than a convenience for Microsoft’s own programming in the loader and kernel, if not in the hypervisor itself. That said, the Specification that is offered today (12th November 2016) as the most recent version is a PDF that is three years old. Despite the Microsoft Open Specification Promise, the return of meaningful information in ecx seems not yet to be documented anywhere in any sense.
The HV_IMPLEMENTATION_LIMITS is 0x10 bytes. Names and definitions below are from type information in the symbol files for URLMON.DLL in Windows 8.1. Well might you wonder what URLMON.DLL has to do with the hypervisor such that its symbol files have type information for this structure but the kernel’s don’t!
|6.1 and higher|
|6.1 and higher|
|6.2 and higher|
|6.1 to 6.3|
|10.0 and higher|
Definition before version 6.3 means prior appearance in the HV_CPUID_RESULT union.