From 96227d9bd03481e39d59d15ae598ec099c767947 Mon Sep 17 00:00:00 2001 From: _xeroxz Date: Fri, 26 Feb 2021 01:11:44 +0000 Subject: [PATCH] Update README.md --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 3242ea5..b8c7329 100644 --- a/README.md +++ b/README.md @@ -30,10 +30,12 @@ This project uses WDK and thus Windows Kernel functions to facilitate vmxlaunch. ### Why Write A Hypervisor? -Why write a type-2 (Intel or AMD) hypervisor? "To learn" is the typical response, but to learn what? To learn VMX instructions? To learn how to write a windows kernel driver? To learn how to use windbg? Although all of the prior reasons to write a hypervisor are important, learning how to read technical documents and extract what you need from the reading material is much more valuable than all of the other stuff one might learn while writing a hypervisor. This is best summed up as the old saying goes: +Why write a type-2 (Intel or AMD) hypervisor? "To learn" is the typical response, but to learn what? To learn VMX instructions? To gain more experience with WDK? To gain more experience with windbg? Although all of the prior reasons to write a hypervisor are important, learning how to read technical documents and extract what you need from the reading material is much more valuable than all of the other stuff one might learn while writing a hypervisor. This is best summed up as the old saying goes: > “give a man a fish, he will feed himself for a day, teach a man to read the manual and he will make a hypervisor” +My second reason for learning about intel VT-x, is that hypervisors can be used to solve very complex programs, can be used to debug things which cant normally be debugged, and moniter memory accesses at a hardware level (EPT is on my to-do). + ### VMCS This section of the readme just contains notes and a list of things I stumbled on and took me a while to figure out and fix.