diff options
| author | ionescu007 <ionescu007@users.noreply.github.com> | 2016-03-17 03:36:45 +0300 |
|---|---|---|
| committer | ionescu007 <ionescu007@users.noreply.github.com> | 2016-03-17 03:36:45 +0300 |
| commit | 6c7bccdc4ac6153b3f161797d498f4fcd04575ce (patch) | |
| tree | f07e117011dd99e2aa89f5dba0ad79f4bb1a1ae5 | |
| parent | f1d07f5195e23a2e9ba79c3c99e6adda5481a978 (diff) | |
Update README.md
| -rw-r--r-- | README.md | 11 |
1 files changed, 10 insertions, 1 deletions
@@ -21,7 +21,7 @@ A few projects do stand out from the fold however, such as the original Blue Pil The closest project that actually delivers a Windows-centric, modern, and supported hypervisor is HyperPlatform, and the author strongly recommends its use as a starting place for commercial and/or production-worthy hypervisor development. However, in attempting to create a generic "platform" that can be productized, HyperPlatform also suffers from a bit of bloat, making it harder to understand what truly are the basic needs of a hypervisor, and how to initialize one. -The express goal of this project, as stated above, was to minimize code in any way possible, without causing negative side-effects, and confusing on the 'bare-metal' needs. This includes: +The express goal of this project, as stated above, was to minimize code in any way possible, without causing negative side-effects, and focusing on the 'bare-metal' needs. This includes: * Minimizing use of assembly code. If it weren't for the lack of an __lgdt intrinsic, and a workaround for the behavior of a Windows API, only the first 4 instructions of the hypervisor's entry point would require assembly. As it stands, the project has a total of 10 instructions, spread throughout 3 functions. This is a maassive departure from other hypervisor projects, which often have multiple hundreds of line of assembly code. A variety of Windows-specific and compiler-specific tricks are used to achieve this, which will be described in the source code. * Reducing checks for errors which are unlikely to happen. Given a properly configured, and trusted, set of input data, instructions such as vmx_vmwrite and vmx_vmread should never fail, for example. @@ -46,6 +46,15 @@ And stop it with You must have administrative rights for usage of any of these commands. +## References + +https://github.com/upring/virtdbg +http://xenbits.xen.org/gitweb/?p=xen.git;a=summary +https://github.com/svn2github/bochs +https://github.com/rmusser01/hyperdbg +http://invisiblethingslab.com/resources/bh07/nbp-0.32-public.zip +https://github.com/tandasat/HyperPlatform + ## License ``` |