Introduction
Hello! Welcome back to our course on Cloud Computing.
In our previous lesson, we examined the inherent challenges of virtualization, such as performance overhead, management complexity, and new security risks like hyperjacking. We established that the software component at the very heart of both the power and the problems of virtualization is the hypervisor.
This lesson zeroes in on that critical component. Our goal is to address the learning outcome: Define a hypervisor and explain its function in creating and managing virtual machines. By the end of this lesson, you will have a clear, exam-ready definition and a solid understanding of the essential roles a hypervisor plays. This knowledge is foundational for everything that follows in our study of virtualization and cloud infrastructure.
The Problem Hypervisors Solve: Underutilized Hardware
Before defining what a hypervisor is, it's crucial to understand why it was invented. In traditional computing, one physical server would typically run a single operating system and a specific application (e.g., an email server or a web server).
The problem? Most of the time, that single application didn't use the server's full processing power, memory, or network capacity. This led to massive inefficiency: datacenters were filled with expensive, power-hungry servers that were mostly idle.
Virtualization, enabled by the hypervisor, solves this problem by allowing a single physical server to run multiple, independent "virtual" servers simultaneously, dramatically increasing resource utilization.
The image below perfectly illustrates this transition.
What is a Hypervisor?
At its core, the hypervisor is the key technology that makes virtualization possible. To get a precise, exam-friendly definition, let's consult a guide from Nutanix.
What are hypervisors? A complete guide - Nutanix
This article provides a concise and clear definition of a hypervisor, which is perfect for your exam preparation.
Please read the section titled 'What is a hypervisor?' at the very beginning of the article. Pay close attention to the keywords: virtual machines (VMs), resource allocation, server virtualization, and abstraction. Note the alternative name for a hypervisor mentioned here.
From that reading, we can establish a formal definition:
Definition: A hypervisor, also known as a Virtual Machine Monitor (VMM), is a software process that creates and runs virtual machines (VMs). It works by abstracting the underlying physical hardware (the host machine) and allocating its compute, memory, storage, and networking resources to the multiple VMs (guest machines) running on it.
In simpler terms, the hypervisor is a layer of software that lets you run multiple, isolated operating systems on a single physical computer.
The Core Functions of a Hypervisor
Now that we have a definition, let's explore how a hypervisor performs its duties. Its functions can be broken down into three main areas: resource abstraction, VM management, and isolation.
This video from IBM Technology provides an excellent visual breakdown of these functions.
This video clearly explains how a hypervisor takes physical resources and divides them up for virtual machines, and why its role in security is so important.
Watch the video from 00:58 to 04:29. Pay close attention to: The essential components of a compute host that are virtualized (CPU, RAM, Network). How the hypervisor 'slices up' these physical resources to create virtual ones (vCPU, vRAM, vNIC). The crucial role the hypervisor plays in providing security and isolation between different virtual machines.
Based on the video and our definition, let's summarize the key functions for your notes.
1. Resource Abstraction and Allocation
The primary function of a hypervisor is to act as a resource manager. It sits between the physical hardware and the virtual machines.
- It takes the physical resources of the host machine—such as CPU cores, gigabytes of RAM, and network bandwidth.
- It abstracts these resources, meaning it presents them in a generic, virtualized form.
- It then allocates or "slices up" these virtual resources among the different VMs according to their needs. For example, it might assign 2 vCPUs and 4GB of RAM to VM-1, and 4 vCPUs and 8GB of RAM to VM-2, all from the same physical pool.
2. Virtual Machine Lifecycle Management
The hypervisor is responsible for the entire lifecycle of a VM. This includes:
- Creating new VMs.
- Starting (booting) the VMs.
- Suspending and resuming VMs.
- Shutting down VMs.
- Deleting VMs.
Essentially, it's the control plane for all virtual machines on the host.
3. Isolation and Security
As we saw in the previous lesson, security is a major consideration in virtual environments. A critical function of the hypervisor is to maintain strong isolation between VMs.
- It ensures that each VM operates in its own sandboxed environment.
- Processes running in one VM cannot access the memory or storage of another VM on the same host.
- If one VM crashes or is compromised by malware, the hypervisor prevents it from affecting the other VMs. This isolation is fundamental to the security model of multi-tenant cloud computing.
An Analogy for Deeper Understanding
Analogies are excellent tools for remembering complex concepts during exams. The idea of a hypervisor as a landlord managing an apartment building is a popular and effective one.
Lec-15: What is Hypervisor | Types of Hypervisor
To help solidify these concepts, let's watch a short clip that uses a helpful real-life analogy.
Watch the segment from 00:27 to 04:14. Focus on how the host machine is compared to a building, VMs to apartments, and the hypervisor to the landlord who manages all the shared resources (electricity, water, etc.) and ensures each tenant (VM) stays in their own space.
Here's how the analogy maps to the technical concepts:
| Analogy | Technical Concept |
|---|---|
| Land / Building | The physical server (Host Machine) |
| Apartments | The individual Virtual Machines (VMs) |
| Tenants in Apartments | Guest Operating Systems and Applications |
| Shared Utilities (Electricity, Water) | Physical Resources (CPU, RAM, Storage) |
| Landlord / Building Manager | The Hypervisor |
The landlord (hypervisor) ensures each apartment (VM) gets its fair share of utilities (resources) and that one tenant's activities don't disturb the others (isolation).
Conclusion
In this lesson, we have defined the hypervisor and detailed its essential functions. You now have the foundational knowledge required to understand how modern cloud infrastructure is built.
Key Takeaways for Your Exam:
- Definition: A hypervisor, or Virtual Machine Monitor (VMM), is software that creates, runs, and manages virtual machines on a single physical host.
- Core Purpose: It solves the problem of underutilized hardware by enabling multiple operating systems to run on one server.
- Key Functions:
- Resource Abstraction & Allocation: It "slices up" physical CPU, RAM, and network resources and assigns them to VMs.
- VM Management: It controls the entire lifecycle of a VM (create, start, stop).
- Isolation: It provides a strong security boundary, ensuring that VMs cannot interfere with one another.
Preview of the Next Lesson:
Now that we know what a hypervisor is and what it does, the next logical question is: how is it implemented? In our next lesson, we will explore the two main architectural approaches: Type 1 (bare-metal) hypervisors and Type 2 (hosted) hypervisors. We will examine their distinct architectures, compare their performance and security characteristics, and see why Type 1 hypervisors are the standard for enterprise and cloud environments.