kHypervisor

Introduction

kHypervisor is an Open Source light-weighted Nested-Virtual Machine Monitor in Windows x64 platform. Supported multi-core , and which is extending from Hyper-platform :-)

Advantages

kHypervisor provide an light-weighted virtulized environment for debugging protected mode Guest

• VM Entry Emulation , with VMCS state check which is a good solution for debugging VMEntry fail, and locate the actual failure location.
• VM Exit Emulation
• Nested VM Exit Event
• The code is simple and minimize as a nested vmm.

Environment

• Visual Studio 2015 update 3
• Windows SDK 10
• Windowr Driver Kit 10
• VMware 12 with EPT environment.
• Supports Multi-core processor environment
• Test environment with Windows 7 x64 sp1 to Windows 10 x64 build 16299 RS3
• It onlys support restricted guest (protected - paging mode) for the present

Description

The kHypervisor is not yet completed, and it will be rapidly update on progress, please using a windbg+vmware 12 for debugging kHypervisor.  

Progress

2016-10-19 First commit, Supporting nested itself only, and nested software breakpoint exception from Level 2. And the nested-Vmm is able to dispatch this exception to L1 and help L1 to resume to L2.

2016-10-21 Fixed Ring-3 vm-exit emulation error.

2017-01-03 Reconstruct project, and Finding VMCS12 through VMCS02 by executing vmptrst

2017-01-22 GS Kernel base MSR bug fixed when Emulation VMRESUME/VMLAUNCH

2017-02-05 VPID shared between VMCS0-1 and VMCS0-2, support multi-processor.

2017-02-08 Emulate VMExit behaviour has been slightly Changed. in case of L2 is trapped by L0, and L0 emulate VMExit to L1, this time of VMRESUME will not be restore a Guest CR8 and Guest IRQL, it is until VMRESUME by L1. (L0 helps L1 resume to L2)

2017-05-28 Fixed Nested-CPUID problem, and add Nested-VMCALL.

2017-06-07 Fixed a VMExit buggy , clear the guest eflags, and reserved bit[1] == 1

2017-06-08 Adding a support for Monitor Trap Flags from L2 and perform Nested VMExit

2017-11-21 Added VM-Entry Check Emulation , Bug Fixed

2018-01-19 Added Nest-Msr Access support , plus, a better coding style changes. Add Test in Windows x64 build 16299 RS3.Release

2018-02-05 Added Nested EPT which is running in Windows 7 x64 build 7601 system. (still not test by Windows 10)

2018-03-28 Use lateste version repo of Ddimon as a being nested-target, deleted nested-vmm

2018-03-29 Added Nested EPT monitoring , when the PTE entry OF guest EPT is modified, L0 knows.

2020-03-07 Testing on DdiMon

Installation

• kHypervisor extended HyperPlatform which is created by Tandasat, it is a Nested-Virtual Machine Monitor, and DdiMon is one of Tandasat's product of HyperPlatform for test demo in kHypervisor.

  • Compiled kHypervisor.sys and DdiMon.sys by kHypervisor and NestedHypervisor respectively

  • We supports a multi-core environment

  • Enable Testsigning on x64:

    bcdedit /set testsigning on

  • Install DdiMon.sys and kHypervisor.sys by following command:

    sc create hostvmm type= kernel binPath= C:\kHypervisor.sys

    sc create nestedvmm type= kernel binPath= C:\Ddimon.sys

  • start a service as following screen capture with its expected output

Nesting with Hypervisor EPT Based Rootkit - DdiMon

Live Demo with kernel rootkit

Windows 10 x64 build 16299 RS3 Test Demo (with Nested EPT) :

Expected Output

kHypervisor can be tested by kernel/user mode with Multi-Core Processor Configuration

Kenrel mode Test

1. During the installion we could able to see a result, since we set a breakpoint as soon as the DdiMon's virtualization.

2. We can see the windbg as following result, after the DdiMon execute a breakpoint, kHypervisor will first capture the breakpoint :

3. After printed VMCS, the emulation of vmexit is done, and kHypervisor will find out which is the original handler as following, the control flow is transfer to DdiMon now. (the kHypervisor is not supposed exists by Ddimon, but it does.)

4. After the DdiMon catch up the control flow, it will normally execute a VMRESUME, since he didn't know anythings, and feel it is normal trap only :)

User Mode Test 

A INT 3 breakpoint in the system will be work as follow:

1. We start any program with x64dbg, and the debugger will break the process, and L0 should catch the exception.

2. we handled it, and we will emulate the VMExit to L1 by execute VMRESUME with L1's host VMM Handler address (guest rip == L1's host rip, the mode of VCPU will be rooted, but actually it is non-rooted, so that after the L1's VMM handled it, it called VMRESUME will trapped by L0 again. )

3. Once again trapped by VMRESUME , we emulated the VMRESUME with trapped address. Help L1 resume to L2

Turning off L1 VMM By VMCALL

EPT Modification monitoring

P.S.

With a highest stablility, better close nested-EPT or running nested-EPT in a unicore enivronment first.

TODO

• Fully Support CPU Feature from vCPU aspect.
• EPT virtualization
• APIC virtualization
• Unrestricted guest support (vbox) , such as virtual 8086 mode.

Related Project(s)

https://github.com/tandasat/HyperPlatform
https://github.com/tandasat/ddimon

License

This software is released under the MIT License, see LICENSE.