Supported Platforms and Features

Platforms supported by virt86

virt86 supports the following hypervisors and operating systems:

	Windows	Linux	Mac OS X
Intel HAXM	✔	✔	✔
Windows Hypervisor Platform	✔1	-	-
KVM	-	✔	-
Hypervisor.Framework	-	-	✔2

¹ Windows Hypervisor Platform requires Windows 10 SDK 10.0.17134.0 or later.
² Hypervisor.Framework support is under development. See issue #1 and the hvf branch.

Virtualization platform technologies

The hypervisor platforms themselves support the following hardware-assisted virtualization technologies:

	Intel VT-x	AMD-V
Intel HAXM	✔	-
Windows Hypervisor Platform	✔	✔
KVM	✔	✔
Hypervisor.Framework	✔	N/A

Feature matrix

These are the features exposed by each hypervisor platform:

Feature PlatformFeatures field	HAXM	WHPX	KVM	HvF1
Unrestricted Guest2 unrestrictedGuest	✔	✔	✔	?
Extended Page Tables (EPT)2 extendedPageTables	✔	✔	✔	?
Guest debugginga guestDebugging	✔ (7.3.0)	-	✔	?
Guest memory protection guestMemoryProtection	✔ (7.2.0)	-	✔	?
Dirty page tracking dirtyPageTracking	-	✔ (10.0.17763.0)	✔	?
Partial dirty bitmap queryingb partialDirtyBitmap	-	✔ (10.0.17763.0)	-	?
Large memory allocation (> 4 GiB) largeMemoryAllocation	✔ (7.1.0)	✔	✔	?
Partial GPA range unmapping partialUnmapping	✔	✔ (10.0.17763.0)	-	?
Extended VM exits extendedVMExits	-	✔3 (10.0.17763.0)	✔4	?
Custom CPUID responses customCPUIDs	-	✔ (10.0.17134.0)	✔5	?

¹ virt86 does not implement an adapter for the Hypervisor.Framework yet. See issue #1.
² Depends on the capabilities of the host's CPU.
³ VM exit on CPUID instruction, MSR access and CPU exception.
⁴ VM exit on CPU exception only.
⁵ Also provides a list of supported CPUID responses and default values in supportedCustomCPUIDs.

^a Single stepping, software and hardware breakpoints.
^b Allows querying subsets of mapped GPA ranges. If dirty page tracking is supported but partial dirty bitmap querying is not, the hypervisor will only allow querying entire mapped GPA ranges.