Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add content/en/hypervisor #1385

Merged
merged 15 commits into from
Nov 18, 2022
35 changes: 35 additions & 0 deletions content/en/hypervisor.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
---
title: Hypervisor
status: Feedback Appreciated
category: Technology
tags: ["application", "", ""]
---

## What it is

The Hypervisor is a software application that performs [virtualization](/virtualization/)
KiranSatyaRaj marked this conversation as resolved.
Show resolved Hide resolved
by taking the advantage of [bare metal machine](/bare-metal-machine/) resources
(CPU, Memory, Network, and Storage) , dividing them into sub-parts,
KiranSatyaRaj marked this conversation as resolved.
Show resolved Hide resolved
and allocating resources according to business logic to create [virtual machines (VM)](/virtual-machine/) and the ability to run multiple VMs simultaneously.
KiranSatyaRaj marked this conversation as resolved.
Show resolved Hide resolved
In the marketplace, they are available as Type 1 hypervisors that can be installed directly on the physical server,
iamNoah1 marked this conversation as resolved.
Show resolved Hide resolved
giving it direct access to system hardware resources.
Type 2 hypervisors, on the other hand, are installed and
executed by the operating system and allow the operating system to make hardware decisions.
## Problem it addresses
KiranSatyaRaj marked this conversation as resolved.
Show resolved Hide resolved

Traditionally, a server could only run one operating system at a time.
Devoting all the resources of the host machine to a single service was not the most effective way.
KiranSatyaRaj marked this conversation as resolved.
Show resolved Hide resolved
Considering the capabilities of a server it can run multiple applications.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The content of the rest of this section is not very accurate, or easy to follow. The aspect of having wasted a whole powerful server on just one app is an important aspect that can be followed up on. For example just saying, that a server could hold more apps, but then you have isolation and noisy neighbors problems (one highly resource-consuming app has an impact on the other ones).
Another problem of the world before virtualization is setup costs. VMs are more quickly set up than bare metal. This is one step to closing the gap between dev and ops.

Copy link
Contributor Author

@KiranSatyaRaj KiranSatyaRaj Oct 30, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm thinking these points could go into this section " acquiring a physical machine takes time, it requires a team of engineers to monitor them, whereas VMs are more quickly set up than bare metal", what do you think? @iamNoah1 and is it because a hypervisor takes away the low-level complexities (like abstraction layer over the physical hardware, it's the software monitoring and isolating the VMs sharing the same hardware) so that it is easier to set up a VM whether they are of the dev team or Ops team in a way was it attracting both the backgrounds?

There is a need for software that can provide the same environment as a physical machine to the applications within it.
Multiply the environments and commit resources to them as needed, ensuring their security simultaneously.
So that the data of one cannot be accessed by the other.

## How it helps

The Hypervisor is used to create and allocate resources to virtual machines until we reach the saturating performance of the physical machines,
KiranSatyaRaj marked this conversation as resolved.
Show resolved Hide resolved
conserving resources and reducing energy consumption.
KiranSatyaRaj marked this conversation as resolved.
Show resolved Hide resolved
A hypervisor simplifies the migration in its current state in the event of a failure on the host server.
KiranSatyaRaj marked this conversation as resolved.
Show resolved Hide resolved
The reason for this is that it maintains snapshots of the workload so that it can be transported from one machine to another.
KiranSatyaRaj marked this conversation as resolved.
Show resolved Hide resolved
In the context of [cloud computing](/cloud-computing/), the hypervisor becomes an effective tool.
Organizations can migrate their applications to the cloud to take advantage of [cloud native apps](/cloud-native-apps/) and autoscale their services.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would try to focus more on the setup speed and the degree of isolation between apps than on migrating for the rest of this section.

Over time, the use of this [multi-tenant](/multitenancy/) software has reduced computing costs.