A hypervisor creates copies or clones of one physical computer’s hardware resources. Each clone is presented to the user as a separate device. Users can install guest operating systems on each of the virtual machines with no ties to the host hardware.
A hypervisor isolates the operating systems from each other so that each one gets exclusive use of the resources dedicated to it. If needed, a hypervisor can allow the operating systems of separate virtual machines to interact. This connection can be used for shared access to certain files or exchanging data through the local network. This way, one computer appears to be multiple computers at the same time, and each works with its own software independent of the others.
There are two main types of hypervisors; however, there are also hybrid hypervisors, which combine the features of both types.
How do Type 1 hypervisors work?
The principle of operation of a Type 1 hypervisor
Type 1 hypervisors are also called microkernels, thin hypervisors or autonomous hypervisors run on bare metal. Type 1 hypervisors are best imagined as a compact operating system with specific functions, which is installed directly on a bare-metal server and has the main signs of an OS:
- presents an abstract set of resources for applications instead of an unordered set of hardware;
- controls the resource pool by distributing CPU time, memory, I/O devices between programs which request the use of the computer’s resources.
Security is one of the main requirements towards hypervisors, as they get full control over the hardware resources on which virtualization is run. Consequently, the hypervisor’s task is to run the machine code in a safe way while not allowing a guest OS to execute commands directly on the host machine or modify the resources reserved for other virtual machines.
Xen, VMware ESXi, Hyper-V, KVM and other hypervisors can be considered Type 1.
Xen (Xenserver, Citrix Hypervisor)
The Xen thin hypervisor was developed as part of a research project of the Cambridge University laboratory. XenSource was absorbed by Citrix in 2007; as a result, some of the products were renamed. Xen is a crossplatform hypersor which supports hardware virtualization and paravirtualization. Most of the components are located beyond the hypervisor, which is why Xen contains a minimal amount of code. Xen is a fully open-source GNU GPL 2-licensed hypervisor. This means that the product can be modified however the user needs. Some consider Xen a hybrid hypervisor due to its support for paravirtualization and hardware virtualization.
VMware ESXi
The autonomous VMware ESXi hypervisor is an Enteprise-class virtualization solution developed by VMware. Earlier, a limited version of ESXi was available for free; however, since VMware was acquired by Broadcom, the new owners dropped support for this version. The hypervisor is now only available for free within a trial period. The licensed version offers a broad set of features, such as centralized VM management on all host machines within a project using the vCenter platform. The free version, however, still performed the basic functions of a hypervisor and was one of the most popular virtualization solutions on the market.
Hyper-V
Hyper-V is hardware virtualization solution for x64 systems made by Microsoft. It is available in two variants: as a role in the server operating systems of the Windows family and as a separate product – Microsoft Hyper-V Server. When installing Hyper-V on OS Windows, the user might get the impression that the hypervisor is being installed directly on the operating system which is already running on the “bare metal”, as is the case with Type 2 hypervisors. In fact, this hypervisor is installed a level below, and the installed operating system becomes a guest OS running on one of the virtual machines. Hyper-V is one of the most popular hypervisors among SIM-Networks clients who are used to working with Microsoft products: this hypervisor was mainly made to work with Windows guest OS’.
KVM
Kernel-based Virtual Machine, KVM is a hypervisor created in October of 2006. It was quickly integrated with the main branch of the Linux 2.6.20 core. Later, KVM was adapted as a core module in FreeBSD. KVM is fully open-source through the GNU GPL and GNU LGPL license, which is why KVM QEMU was used to create SIM-Cloud. Using open-source software allows us to modify the hypervisor as needed and stay independent from vendors. KVM is also popular among SIM-Networks clients who order unique IT infrastructures built from scratch.