#From scratch install
#From scratch software
#From scratch code
#From scratch series

LetвЂ™s get started! Installing ToolsДЇirst, we need to install Visual Studio with WDK (Windows Driver Kit).

You can use the comments below to notify me about these possible errors. In contrast, Windows never tries to manage any unexpected exception and shows a Blue Screen Of Death whenever an unexpected exception occurs therefore, you might get lots of BSODs while testing your hypervisor.Д¬onsidering the fact that I might (and will) make mistakes like misinformation, wrong implementation, or forget about mentioning some essential explanations in these series, I should say sorry in advance, and IвЂ™ll be glad and open to every comment that tells me the mistakes in the technical details. Linux kernel manages faults like #GP and other exceptions and tries to avoid the kernel panic and keep the system up thus, itвЂ™s better to test something like a hypervisor or any CPU-related programs.

#From scratch code

These concepts are platform independent, which means you can easily run the same code routine in both Linux or Windows and expect the same behavior from the CPU, but I prefer to use Windows as its more easily debuggable (at least for me.), but I try to give some examples for Linux systems whenever needed. The rest of these tutorials mainly focus on VT-x because Intel CPUs are more popular and widely used. For example, Intel and AMD use different instruction sets for virtualization. Because the type 2 hypervisor has to go through the operating system and is managed by the OS, the type 2 hypervisor (and its virtual machines) will run less efficiently (slower) than type 1 hypervisors.Д®ven though most of the concepts about the virtualization in Intel and AMD processors are the same, but there are some differences between Intel VT-x and AMD-V. With a type 1 hypervisor, there is no operating system to load as the hypervisor itself has the necessary functions to manage the system boot and startup.Д¬ontrary to a type 1 hypervisor, a type 2 hypervisor loads inside an operating system, just like any other application. A type 1 hypervisor has direct access to the hardware. The вЂњtype 1вЂќ hypervisor is called a вЂњbare-metal hypervisorвЂќ or вЂњnativeвЂќ because it runs directly on a bare-metal physical server. The CPU flag for VT-x capability is вЂњ VMXвЂќ which stands for Virtual Machine e Xtension.ДЄMD, on the other hand, developed its first generation of virtualization extensions under the codename вЂњ PacificaвЂќ and initially published them as AMD Secure Virtual Machine (SVM), but later marketed them under the trademark AMD Virtualization, abbreviated AMD-V. Intel introduced (VT-x technology) that was previously codenamed вЂњ VanderpoolвЂќ on November 13, 2005, in Pentium 4 series.

VMware WorkstationвЂ™s Nested-VirtualizationД«oth Intel and AMD support virtualization in their modern CPUs.

Disabling The Driver Signature Enforcement (DSE).

Moreover, you can learn how the вЂњVMMвЂќ module of the HyperDbg Debugger works internally.

#From scratch software

If you follow this tutorial, youвЂ™ll be able to create your own virtual environment and understand how VMWare, VirtualBox, KVM, and other virtualization software use processorsвЂ™ facilities to create a virtual environment. As the name implies, this course contains technical details to create a basic Virtual Machine based on hardware virtualization.

#From scratch series

Further Reading D.Welcome to the first part of a multi-part series of tutorials called вЂњ Hypervisor From ScratchвЂќ. Clone the Filesystem and Apache Resources 9.7. Configure the Cluster for the Filesystem 7.8. Configure the Cluster for the DRBD device 7.7.

Ensure Resources Start and Stop in Order 6.7. Ensure Resources Run on the Same Host 6.6. Add Apache HTTP Server as a Cluster Service 6.1. Prevent Resources from Moving after Recovery 6. Simplify administration using a cluster shell 3.2. Allow cluster services through firewall 2.6.2. Configure Communication Between Nodes 2.4.1.