From ff4677c59596fb92e1b08f05e2973a7939db5011 Mon Sep 17 00:00:00 2001 From: _xeroxz Date: Tue, 16 Feb 2021 03:00:24 +0000 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 061c24f..c4133a5 100644 --- a/README.md +++ b/README.md @@ -12,7 +12,7 @@ This project uses WDK and thus Windows Kernel functions to facilitate vmxlaunch. 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: -> “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” - or something like that... +> “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” ### VMCS