Virtualization Lecture2
Virtualization Lecture2
Comparing Hypervisors
& Understanding
Virtual Machines
BS Informa+on Technology • 8th Semester • AGS University • Virtual Systems & Services
Lecture Outline – Unit 2
Four major plaNorms dominate enterprise virtualizaPon. Each has disPnct architecture, licensing models, and ideal use cases.
🔵 🟦 🟩 🟧
Source: IDC Virtualiza2on Market Report (approximate figures). KVM increasingly used in OpenStack/public cloud environments.
AGS University | Virtual Systems & Services | BS IT 8th Semester
VMware ESX & ESXi – The Industry Leader Comparing Hypervisors
vSphere Suite
Physical Hardware (x86 Server)
ESXi is the hypervisor; vSphere adds vCenter, vMoTon, HA, DRS, vSAN for
enterprise management.
Licensing
ESXi free (limited). vSphere Enterprise Plus needed for advanced features.
Acquired by Broadcom in 2023.
Origin: Xen hypervisor was developed at the University of Cambridge (2003) and released as open source. Citrix acquired XenSource in 2007,
creaPng XenServer. Now conPnued as XCP-ng (open source) and Citrix Hypervisor (commercial).
Paravirtualization (PV)
Dom0 (Privileged Domain) Guest OS is modified to be aware of the hypervisor — gives near-naAve
Host OS – Controls Hardware Access performance without hardware-assist.
XenMoKon
x86 / x86-64 Hardware
Live migraAon of VMs between hosts, similar to VMware vMoAon. Requires shared
storage.
Hyper-V is Microso?'s Type 1 hypervisor, built into Windows Server 2008 R2+ and Windows 10/11 Pro. It uses a microkernel architecture with
a privileged parent parPPon (equivalent to Xen's Dom0).
Live MigraKon
Child Partitions (VMs) Move running VMs between Hyper-V hosts — similar to vMoAon. Requires Failover
Guest OSes (Win/Linux) Cluster.
Hyper-V Replica
Async replicaAon of VMs to a secondary site for disaster recovery — built-in, no
Hyper-V Hypervisor extra cost.
Azure IntegraKon
Hyper-V is the hypervisor beneath Microso[ Azure. Seamless hybrid cloud
Physical Hardware scenarios.
GeneraKon 1 vs 2
Gen 2 VMs use UEFI, Secure Boot, SCSI boot — faster and more secure than Gen 1
(BIOS).
Type Type 1 (Bare-Metal) Type 1 (Bare-Metal) Type 1 (Bare-Metal) Type 1 (Kernel Module)
Guest OS Win, Linux, macOS Win, Linux (HVM/PV) Win, Linux Win, Linux, BSD
Management UI vCenter (paid) XenCenter / Xen-API Hyper-V Manager oVirt / Cockpit / CLI
License Commercial (costly) Open Source / Commercial Free (with Windows) Fully Open Source
Best For Enterprise Data Center Cloud / Open Source Microsoft Shops Linux / OpenStack Cloud
Cloud Usage Private cloud vSphere AWS (historically) Microsoft Azure Red Hat Cloud / OpenStack
DefiniKon: A Virtual Machine (VM) is a so?ware-based computer that emulates a physical machine. It runs its own operaPng system
and applicaPons, completely isolated from other VMs and the underlying physical host, sharing physical hardware resources managed
by the hypervisor.
Stored as Files
ApplicaKons
📁 A VM is just a set of files (.vmdk, .vmx) on a disk. Move files = move the
enTre computer.
Snapshoaable
📸 Capture the entire VM state in seconds. Restore instantly if anything
goes wrong.
AGS University | Virtual Systems & Services | BS IT 8th Semester
Examining CPUs in a Virtual Machine Virtual Machines
vCPU (Virtual CPU): A virtual processor presented to the guest OS. The hypervisor maps vCPUs to physical CPU cores using a scheduler.
A VM 'sees' vCPUs as real processors.
vRAM is the virtual RAM presented to a guest OS. The hypervisor maps guest physical memory to real host memory using a translaPon layer
(Extended Page Tables / Nested Paging for performance).
VMs use virtual disks — files stored on a host file system or shared storage (SAN/NAS). The guest OS sees a standard virtual disk controller
and interacts with it like physical hardware.
1 2
Hypervisor reads the VM configuraTon file (.vmx/.xml). Allocates The VM's virtual firmware initializes virtual hardware — just like a
vCPUs, vRAM, virtual disks, and vNICs as specified. physical PC BIOS POST. Loads bootloader from virtual disk.
3 4
Guest OS kernel loads into vRAM. Detects virtual hardware (virtual Guest vCPUs execute most instrucTons naTvely on physical cores (via
CPU, disk controller, NIC). Installs hypervisor drivers (VMware Tools / VT-x). Privileged instrucTons are intercepted & emulated by
Guest Additions). hypervisor.
5 6
Guest accesses vRAM. Hypervisor EPT maps guest physical→host Guest I/O requests go to virtual device drivers → hypervisor I/O stack
physical addresses. TLB used for fast repeated lookups. → physical hardware. Hypervisor queues and schedules requests
across VMs.
Clone: An exact copy of a virtual machine at a specific point in time. The clone is an independent VM with its own unique identity (MAC
address, UUID). Changes to the clone do not affect the original.
• Complete copy of the enPre virtual disk • Shares a common base disk with parent (snapshot)
• Fully independent — no dependency on source VM • Only stores the differences from the parent (delta)
• Occupies the same storage as the original VM • Creates very quickly — minimal disk space used
• OperaPons on clone don't affect source at all • Requires parent VM to remain accessible
• Best for: long-term standalone deployments • Best for: dev/test labs, VDI pools, rapid tesPng
• Slower to create (must copy enPre disk) • Performance may degrade as delta disk grows
• Recommended for producPon VM duplicates • Instant provisioning — seconds vs minutes
Template: A master image of a VM that has been converted into a non-runnable, read-only gold image. New VMs are instantly
deployed from templates — like a stamp that produces identical VMs each time.
Template Workflow
2 3 4 5
1
Build Master VM → Install OS & → Sysprep/Seal → Convert to → Deploy New
Apps (Remove unique IDs) Template VMs from Template
Snapshot: A point-in-Pme capture of a VM's complete state — including memory contents, disk state, and VM sefngs. The hypervisor
creates a delta disk to track subsequent changes. ReverPng erases all changes made a?er the snapshot.
• Before applying OS patches or so?ware updates • DON'T keep snapshots long-term — delta disks grow and slow I/O
• Before making risky configuraPon changes • DON'T use as a backup — they are NOT a backup soluPon
• Short-term tesPng in dev/test environments • DON'T snapshot databases without quiescing (data integrity risk)
• Quick rollback in case something breaks • Keep snapshot chains to 2–3 maximum for performance
OVF (Open VirtualizaKon Format): An open, vendor-neutral standard (DMTF) for packaging and distribuPng virtual appliances. Defines VM
hardware, OS, and so?ware configuraPon in a portable, interoperable format usable across different hypervisors.
.mf Manifest file. SHA hashes of all files for integrity verificaTon. Virtual Appliances
Vendors distribute pre-built servers (routers, firewalls, apps) as OVA files.
Container: A lightweight, portable unit of so?ware that packages an applicaPon and all its dependencies (libraries, configs) into a single
bundle. Containers share the host OS kernel — unlike VMs which need a full guest OS.
VM vs Container Architecture
Docker · Kubernetes · Podman Docker · Kubernetes · Podman Docker · Kubernetes · Podman Docker · Kubernetes · Podman
02 A VM is a so?ware computer stored as files, with vCPU, vRAM, vNIC and vDisk managed by the hypervisor
03 vCPUs can be overcommitted; Intel VT-x / AMD-V enables hardware-assisted virtualization for performance
04 Memory techniques: TPS deduplicaPon, ballooning, swapping, and reservaPons manage vRAM efficiently
05 vSwitches connect VMs internally; port groups & VLANs segment traffic; pNICs are shared uplinks
06 Thin/thick provisioning trade storage efficiency vs. performance; vMoPon needs shared storage
07 Full Clone = independent copy; Linked Clone = delta sharing parent; Template = gold image for deployment
08 Snapshots = point-in-Pme state — great for patching safety, NOT a backup; keep chains short
09 OVF/OVA = open portability standard; Containers share kernel, start in ms, weigh MBs vs VM GBs
BS Information Technology • 8th Semester • AGS University • Virtual Systems & Services