CampusLearn
← CSC 415 Cloud Computing and Virtualization

Virtualization Technologies and Hypervisor Architecture

Notes

Fundamentals of Virtualization Virtualization is the foundational technology underpinning cloud computing. It abstracts physical computer hardware, allowing a single physical server to execute multiple independent virtual machines. Each virtual machine encapsulates its own virtual CPU, virtual memory, network interfaces, and storage volumes. This hardware abstraction maximizes hardware utilization, reduces physical server sprawl, and ensures strong workload isolation. Hypervisor Classification The software layer facilitating virtualization is known as the Virtual Machine Monitor or hypervisor. Hypervisors fall into two architectural categories. Type 1 hypervisors, also called bare-metal hypervisors, run directly on host server hardware without an intermediary host operating system. Examples include VMware ESXi, open-source KVM, and Microsoft Hyper-V. Because they interact directly with hardware instructions, Type 1 hypervisors provide low latency, superior I/O throughput, and high security, making them standard for enterprise data centers. Type 2 hypervisors, known as hosted hypervisors, run on top of an existing host operating system as application software. Examples include Oracle VM VirtualBox and VMware Workstation. While convenient for software development, desktop virtualization, and academic testing, they incur performance overhead from double scheduling through the host operating system kernel. Virtualization Techniques and Containers Full virtualization presents a complete virtual hardware representation to guest systems using binary translation or hardware-assisted CPU features such as Intel VT-x and AMD-V, allowing unmodified guest operating systems to execute. Paravirtualization modifies the guest operating system kernel so it issues hypercalls directly to the hypervisor, avoiding expensive CPU emulation. Containerization represents operating-system-level virtualization. Unlike virtual machines that bundle an entire guest operating system, containers share the underlying host Linux kernel using cgroups for resource limits and namespaces for process isolation. Containers start in milliseconds and consume significantly fewer resources than traditional virtual machines. Practical example A commercial bank headquartered in Upper Hill, Nairobi, sought to consolidate its core banking development and testing infrastructure. The IT department maintained forty standalone physical tower servers, each running at less than fifteen percent CPU utilization while consuming substantial diesel generator backup power during national grid outages. The systems engineering team implemented a Type 1 hypervisor solution using open-source Kernel-based Virtual Machine on three Dell PowerEdge rack servers configured as a high-availability cluster. They configured an isolated virtual local area network and mapped shared storage using an iSCSI storage area network. Critical banking applications were provisioned as separate virtual machines with dynamic memory allocation. Furthermore, microservices handling customer SMS alerts and account balance inquiries were containerized using Docker, allowing twenty container instances to run efficiently inside a single Linux virtual machine. This virtualization deployment reduced data center cooling and electricity costs by sixty percent while allowing developers to provision new sandbox testing environments in minutes rather than waiting weeks for physical procurement.

Quiz

1. Which mechanism does operating-system-level virtualization rely upon to achieve process isolation between containers?

2. What is the defining operational difference between a Type 1 and a Type 2 hypervisor?

3. How does paravirtualization achieve performance benefits over pure software-based full virtualization?

Sign in to submit and securely grade your quiz.