Unit 2 (Virtualization)

1. Introduction
=> Virtualization is the core technology behind cloud computing. It refers to
the process of creating a virtual (rather than physical) version of computing
resources such as servers, storage, or networks. Through virtualization, a
single physical machine can be divided into multiple virtual machines
(VMs), each running its own operating system and applications
independently.
 This is achieved using a software layer called a hypervisor (like
VMware, Hyper –V, or KVM), which manages and allocates hardware
resources to each virtual machine. Virtualization increases resource
utilization, reduces hardware costs, and allows scalability and
flexibility in deploying cloud services.
 In cloud computing, virtualization enables Infrastructure as a Service
(IaaS) by allowing users to access virtualized hardware resources on
demand. It also supports isolation, backup, disaster recovery, and
dynamic workload management, making cloud environments more
efficient and cost-effective.
 Virtualization is the technology that allows multiple virtual systems
to run on a single physical system, forming the foundation of cloud
computing by enabling efficient resource sharing, flexibility, and
scalability.
Difference between Type 1 and Type 2 Virtualization
Type 1 Virtualization (Bare- Type 2 Virtualization
Feature
metal Hypervisor) (Hosted Hypervisor)
Hypervisor runs directly on the
Hypervisor runs on top of
Definition
hardware a host OS
Hardware → Host OS →
Layer Position Hardware → Hypervisor → VMs
Hypervisor → VMs
Lower performance due to
Performance High performance, low latency
extra OS layer
Security More secure (smaller attack Less secure (depends on
 Type 1 Virtualization (Bare- Type 2 Virtualization
Feature
metal Hypervisor) (Hosted Hypervisor)
surface) host OS security)
Data centers, servers, cloud Personal use, testing,
Use Cases
computing development
VMware ESXi, Microsoft Hyper-V VMware Workstation,
Examples
(bare-metal), Xen, KVM VirtualBox, Parallels
Resource
Direct access to CPU, memory Indirect access via host OS
Access
Scalability Highly scalable Less scalable
Very stable for production Stability depends on host
Stability
workloads OS

1.1. Virtualization Technologies: Virtual machines, Hypervisors

(Type 1 & Type 2)
=> Virtualization technologies are the tools and methods used to create
virtual versions of computing resources such as hardware, storage,
networks, and operating systems. These technologies form the foundation
of cloud computing, enabling efficient resource utilization, flexibility, and
scalability.

1. Hardware Virtualization
 Allows multiple virtual machines (VMs) to run on a single physical
server.
 Managed by a software called a hypervisor (e.g., VMware, KVM,
Hyper-V, Xen).
 Each VM acts as an independent system with its own OS and
applications.
 Used in: IaaS (Infrastructure as a Service).

2. Operating System (OS) Virtualization

  Allows multiple isolated user-space instances (containers) to run on a
single OS kernel.
 Faster and lighter than hardware virtualization.
 Examples: Docker, LXC, OpenVZ.
 Used in: PaaS (Platform as a Service).

3. Server Virtualization
 Divides a physical server into several virtual servers.
 Improves hardware utilization and simplifies management.
 Examples: VMware vSphere, Microsoft Hyper-V

4. Storage Virtualization
 Combines multiple physical storage devices into a single virtual
storage unit.
 Simplifies storage management and improves performance and
scalability.
 Examples: Storage Area Network (SAN), Network Attached Storage
(NAS), VMware vSAN.

5. Network Virtualization
 Combines hardware and software network resources into a single,
software-based network.
 Enables flexible and programmable network management.
 Examples: VLANs, SDN (Software Defined Networking), Cisco ACI.

6. Desktop Virtualization
 Allows users to access their desktop environment from any device
remotely.
 Data and applications run on the server, not on the local device.
 Examples: VMware Horizon, Citrix Virtual Apps and Desktops.

7. Application Virtualization
  Runs applications in isolated environments without installing them
on local systems.
 Reduces conflicts between applications and simplifies updates.
 Examples: VMware ThinApp, Microsoft App-V.

Virtual Machines (VMs)

 A Virtual Machine is a software based emulation of a physical
computer.
 Each VM runs its own operating system (guest OS) and applications,
while sharing the hardware resources of the host system (CPU,
memory, storage, etc.).
o Multiple VMs can run on a single physical machine.
o Each VM is isolated, so a failure in one does not affect others.
o Used widely in cloud computing to deliver Infrastructure as a
Service (IaaS).
Examples:
VMware Workstation, Oracle VirtualBox, Microsoft Hyper-V, KVM (Kernel-
based Virtual Machine)

Hypervisor
A Hypervisor (also called a Virtual Machine Monitor, VMM) is the software
layer that creates, runs, and manages virtual machines by allocating
hardware resources (CPU, memory, storage) to them.
Hypervisors are of two main types:
a) Type 1 – Bare-Metal Hypervisor
 Installed directly on the physical hardware (no underlying OS).
 Provides better performance, security, and stability.
 Commonly used in data centers and enterprise cloud environments.
Examples:
VMware ESXi, Microsoft Hyper-V (Server Core), Citrix XenServer, KVM

Diagrammatically:
Hardware  Hypervisor  Virtual Machines

b) Type 2 – Hosted Hypervisor

 Installed on top of an existing operating system.
 Easier to set up but slightly slower due to the extra OS layer.
 Commonly used for testing, development, or personal use.
Examples:
VMware Workstation, Oracle VirtualBox, Parallels Desktop

Diagrammatically:
Hardware  Host OS  Hypervisor  Virtual Machines

Difference between Type 1 and Type 2 Hypervisors

Feature Type 1 (Bare-Metal) Type 2 (Hosted)
Installation Directly on hardware On top of host OS
Performance High (near-native) Lower (extra OS layer)
Use Case Servers, Data centers Personal use, Testing
Examples ESXi, Xen, KVM VirtualBox, VMware Workstation

1.2. Overview of Containerization and Kubernetes

1. Containerization
Containerization is a lightweight virtualization technology that allows
applications to run in isolated environments called containers.
Each container includes everything needed to run an application – code,
runtime, libraries, and dependencies – ensuring it runs consistently across
different environments.

Key Features:
 Lightweight: Containers share the host operating system kernel
instead of running separate OS instances (unlike virtual machines).
  Portable: Containers can run on any system that supports container
runtime (e.g., Docker).
 Fast Deployment: Containers start quickly and use fewer resources.
 Isolation: Each container runs independently, improving security and
reliability.

Popular Tools:
 Docker – most widely used container platform.
 Podman, LXC, containerd, CRI-O – other examples.
Example:
A web app and its database can each run in separate containers,
communicating through defined ports, making it easier to deploy and scale.

2. Kubernetes (K8s)
=> Kubernetes is an open-source container orchestration platform
developed by Google to automate the deployment, scaling, and
management of containers.
It manages large numbers of containers running across multiple servers
(nodes) and ensures applications are always running as intended.

Key Functions of Kubernetes:

 Container Orchestration: Automates deployment, scaling, and
updates of containers.
 Load Balancing: Distributes traffic evenly across containers.
 Self-Healing: Automatically restarts failed containers.
 Scaling: Adds or removes containers based on demand.
 Service Discovery: Assigns IPs and DNS names to containers for
communication.
Core components:
Component Description
Smallest deployable unit; contains one or more
Pod
containers.
 Component Description
Node A physical or virtual machine that runs pods.
Cluster Group of nodes managed by Kubernetes.
Master (Control
Manages and schedules containers across nodes.
Plane)
Command-line tool for managing Kubernetes
Kubectl
clusters.

Relationship between Containerization and Kubernetes

Concept Purpose
Packages and runs applications in isolated environments
Containerization
(e.g., Docker).
Manages and automates large-scale container
Kubernetes
deployments.

2. Virtual Machine
A Virtual Machine is a software-based emulation of a physical computer. It
runs on operating system and applications just like a real computer, but it
operates inside a host system using virtualization technology.
Each VM behaves as an independent computer with its own CPU, memory,
storage, and network interface, even though these resources are actually
shared from the underlying physical hardware.

Key Components:
1. Host Machine: The physical computer that provides resources.
2. Guest Machine: The virtual system running inside the host.
3. Hypervisor: The software (like VMware, KVM, or Hyper-V) that creates
and manages VMs.

How it works:
  The hypervisor divides the physical resources of the host (CPU, RAM,
storage) into multiple virtual environments.
 Each VM runs its own operating system (guest OS) independently.
 Multiple VMs can run simultaneously on a single physical machine.

Advantages:
 Efficient resource utilization
 Isolation between systems (one VM crash doesn’t affect others)
 Easy backup and recovery
 Enables testing and development on multiple Oss
 Supports cloud computing and server consolidation

Disadvantages
 Slower performance compared to physical machines (due to
overhead).
 Requires more RAM and CPU resources
 Complex to manage large-scale deployments

Examples:
 VMware Workstation/ESXi
 Microsoft Hyper-V
 Oracle VirtualBox
 KVM (Kernel-based Virtual Machine)

2.1. Virtual Machine Management and Configuration

Virtual Machine (VM) Management and Configuration refers to the process
of creating, allocating, monitoring, and controlling virtual machines to
ensure optimal performance, security, and resource utilization in a
virtualized or cloud environment.
It involves configuring system parameters, managing resources like CPU,
memory, and storage, and maintaining the lifecycle of VMs – from creation
to deletion.
Key Aspects of VM Management
a. VM Creation
 Creating a new VM using a hypervisor or management tool (e.g.,
VMware vSphere, Hyper-V Manager, or VirtualBox).
 Configuration includes selecting:
o Operating system (guest OS)
o CPU cores and memory.
o Storage capacity
o Network settings (NAT, bridged, host-only)
o Peripheral devices (USB, display, etc).
b. Resource Allocation
 Assigning system resources (CPU, RAM, storage, and I/O) to each VM.
 Ensures fair usage and prevents resource conflicts among VMs.
 Can use dynamic resource allocation (resources are adjusted
automatically as needed).
c. VM Monitoring
 Tracking performance metrics such as CPU usage, memory utilization,
disk I/O, and network activity
 Helps detect bottlenecks, failures, or inefficient configurations.
 Tools: VMware vCenter, Microsoft System Center, and cloud
dashboards like AWS CloudWatch.

d. VM Snapshot and Backup

 Snapshots capture the state of a VM at a specific point in time.
 Useful for rollback, testing, and disaster recovery.
 Regular backups prevent data loss.

e. VM Migration
 Moving VMs between hosts or data centers without downtime (live
migration).
 Supports load balancing and fault tolerance.
f. VM Security Management
 Configuring access controls, firewalls, and encryption.
 Keeping the guest OS updated and isolated from other VMs.

3. Configuration Management
Configuration involves setting up and maintaining the correct parameters
for the VM to function efficiently and consistently.
Key Configuration Settings:
 Hardware configuration: CPU, RAM, disk size, network adapter type.
 Software Configuration: Guest OS installation, drivers, tools, and
updates.
 Network Configuration: Assigning IP addresses, DNS, and routing
policies.
 Storage Configuration: Connecting virtual disks, shared storage, or
SAN.
 Automation: Using scripts or tools (like Ansible, Puppet, or
Terraform) to manage configuration automatically.

4. Tools for VM Management and Configuration

Tool Platform Key Features
Centralized VM management,
VMware vCenter VMware
monitoring, migration
Microsoft Hyper-V
Windows Create, configure, and monitor VMs
Manager
Cross- Lightweight VM configuration for
Oracle VirtualBox
platform development
Open-source virtualization and resource
KVM + libvirt Linux
control
OpenStack / AWS / Scalable VM orchestration and
Cloud
Azure automated configuration
3. Virtualization Level
In cloud computing, virtualization levels refer to the different layers or
approaches at which virtualization can be applied within a computer
system.
Each level virtualizes a different part of the computing environment – such
as hardware, operating system, application, or networks – to improve
flexibility, resource utilization, and scalability.

1. Instruction Set Architecture (ISA) Level Virtualization

 Virtualization happens at the processor instruction level.
 It emulates a processor’s instruction set, allowing software designed
for one CPU architecture to run on another.
 Mostly used in emulators or for cross-platform compatibility.
Example:
Bochs, QEMU (emulates x86 on ARM systems)

2. Hardware Level Virtualization

 Also known as Full Virtualization.
 The hardware is virtualized using a hypervisor that allows multiple
operating systems (VMs) to run simultaneously on a single physical
system.
 Each VM has its own OS and applications.
Example:
VMware ESXi, Microsoft Hyper-V, KVM

3. Operating System Level Virtualization

 Also called Container based virtualization.
 The OS kernel is shared among multiple isolated environments called
containers.
 Containers run as separate user-space instances but share the same
OS.
Example:
Docker, LXC, OpenVZ

4. Library Level Virtualization

 Virtualization occurs at the library (API) level.
 A virtual library or API layer translates system calls from an
application to the host operating system.
 Enables applications designed for one OS to run on another without
modification.
Example:
Wine (runs Windows applications on Linux), Java Virtual Machine (JVM)

5. Application Level Virtualization

 The application runs in its own isolated virtual environment,
independent of the underlying OS.
 Prevents conflicts between applications and simplifies deployment.
Example:
VMware ThinApp, Microsft App-V, Citrix XenApp
6. Network Level Virtualization
 Combines multiple physical and virtual network resources into a
single logical network.
 Provides flexibility, scalability, and isolation for cloud services.
Example:
VLANs, Software Defined Networking (SDN), VMware NSX

4. Virtual Private Cloud (VPC)

A virtual Private Cloud (VPC) is a private, isolated section of a public cloud
where users can launch and manage cloud resources such as virtual
machines, storage, and databases within a secure virtual network.
It combines the scalability and flexibility of a public cloud with the security
and control of a private cloud.
Key Features:
1. Isolation:
Each VPC is logically separated from other virtual networks within the cloud
provider’s environment.
2. Custom Network Configuration:
Users can define their own IP address ranges, subnets, route tables, and
gateways.

3. Security Controls:
Includes firewalls, network access control lists (ACLs), and VPNs for secure
communication.

4. Scalability:
Allows dynamic scaling of resources as per demand.

5. Connectivity Options:
Can connect to:
 The public internet
 Corporate data centers via VPN or dedicated links (e.g., AWS Direct
Connect)
 Other VPCs (VPC peering)

Benefits:
 Enhanced security and isolation
 Customizable network setup
 High availability and scalability
 Cost-effective compared to traditional private data centers
 Integration with on-premise infrastructure

Examples:
 Amazon VPC (AWS)
  Google Cloud VPC
 Microsoft Azure Virtual Network (VNet) –equivalent to a VPC
 IBM Cloud VPC

Use Cases
 Hosting secure web applications
 Creating hybrid cloud setups
 Managing multi-tier architectures (web, app, database layers)
 Running sensitive workloads that require network isolation

5. Virtual Private Network (VPN) in Virtualization

=> A Virtual Private Network (VPN) is a secure communication tunnel
established over a public network (like the Internet) that allows remote
users or sites to connect to a private network as if they were physically
connected to it.
In virtualization and cloud computing, VPNs play a vital role in securely
connecting virtual machines (VMs), virtual networks, and remote users to
cloud environments or data centers.

How it Works
 VPN uses encryption and tunneling protocols (like PPTP, L2TP, IPsec,
or SSL) to protect data as it travels between endpoints.
 It encapsulates data packets, hiding sensitive information and
ensuring privacy and integrity.
 In a virtualized environment, VPNs connect:
o Remote clients  to virtual machines or cloud servers
o On-premise networks  to cloud-based virtual networks (like
a VPC)

VPN in Virtualized/Cloud Environments

In cloud virtualization, VPNs are used to securely link:
 On-premise infrastructure to Virtual Private Clouds (VPCs)
  Different virtual networks or data centers
 Users to their virtual desktops (VDI) or virtual servers
This enables hybrid cloud and multi-site virtualization setups while
maintaining data security.

Types of VPN Connections

Type Description Used For
Site-to-Site Connects two or more networks Linking corporate data
VPN securely over the Internet center to cloud (e.g., VPC)
Allows individual users to securely Remote employees
Remote
access a virtualized network accessing virtual servers or
Access VPN
remotely desktops
Connects a client device
Client-to- Secure virtual desktop or
(laptop/VM) to a specific site or
Site VPN VM access
virtual network

Benefits in Virtualization
 Enhanced Security: Encrypts data between VMs and remote users.
 Remote Access: Enables users to securely access virtual resources
from anywhere.
 Network Integration: Connects multiple virtual or physical networks
seamlessly.
 Cost-Effective: Reduces need for physical network connections.
 Supports Hybrid Cloud: Bridges private data centers and public
clouds securely.
Example
 In AWS, you can create a VPN connection between you on-premise
data center and your Virtual Private Cloud (VPC).
 In VMware, a VPN can connect remote users to virtual machines
managed within a vSphere environment.
6. DNS Service and Cloud Network
=> The Domain Name System (DNS) is like the phonebook of the Internet –
It translates human-readable domain names (like [Link]) into IP
addresses (like [Link]) that computers use to identify each other
on a network.
 DNS converts domain names  IP addresses, allowing users to
access websites and cloud resources easily.

DNS in Cloud Networking

In cloud computing, DNS plays a vital role in connecting users and
applications to cloud-hosted services virtual machines, and load balancers.
Every time a user accesses a cloud application, the DNS service helps route
traffic to the correct virtual server or data center.

Key Functions of DNS in Cloud Networks

Function Description
Name Converts domain names to IP addresses for virtual
Resolution machines and cloud services.
Distributes traffic across multiple servers for performance
Load Balancing
and availability.
Failover
Automatically redirects traffic to backup servers if one fails.
Support
Directs users to the nearest data center based on location
Geo-Routing
for faster access.
Service Allows cloud applications and microservices to locate each
Discovery other dynamically.

DNS Services in Major Cloud Platforms

DNS
Cloud Provider Key Features
Service
Amazon Web Services Route 53 Scalable DNS, health checks, traffic
 DNS
Cloud Provider Key Features
Service
(AWS) management
Global DNS hosting with high
Microsoft Azure Azure DNS
availability
Google Cloud Platform High-performance DNS with low
Cloud DNS
(GCP) latency
DNS with traffic steering and DDoS
Oracle Cloud OCI DNS
protection

Role of DNS in Cloud Network

DNS helps:
 Connect users  cloud servers (VMs, containers, apps).
 Manage internal DNS zones for private virtual networks
(VPCs/VNets).
 Support multi-region and multi-cloud deployments.
 Integrate with Content Delivery Networks (CDNs) and load balancers
for global access.
Advantages of Using DNS in Cloud
 High availability and reliability
 Fast global performance (low latency)
 Automatic traffic distribution and failover
 Easy scalability with cloud growth
 Centralized DNS management via cloud consoles or APIs

Example:
When a user types:
[Link]
 The DNS resolver queries the DNS server.
 The DNS service returns the IP address of the cloud load balancer.
 The load balancer routes the request to the appropriate virtual
machine or container running in the cloud network.
7. Multihoming
 Multihoming is a networking technique in which a device, server, or
network is connected to two or more Internet Service Providers
(ISPs) or multiple network connections simultaneously.
 Multihoming provides redundancy and reliability by connecting a
network to multiple internet paths, ensuring continuous connectivity
even if one connection fails.
2. Purpose of Multihoming
 High availability (no single point of failure)
 Load balancing (distribute traffic across links)
 Better performance and speed
 Improved fault tolerance and reliability

Working Mechanism
 An organization connects its network (like a data center or cloud
server) to two or more ISPs.
 If one ISP fails or becomes slow, traffic automatically reroutes
through the other connection.
 Routers use Border Gateway Protocol (BGP) or other routing
mechanisms to manage this switching and routing.

Types of Multihoming
Type Description
Host A single host (e.g., a server or virtual machine) has multiple network
Multihoming interfaces or IP addresses connected to different networks.
Network An entire organization or data center connects to multiple ISPs for
Multihoming redundancy and load balancing.

5. Multihoming in Cloud Computing

In cloud and virtualization environments:
 Cloud providers (like AWS, Azure, GCP) use Multihoming to ensure
network resilience.
  Virtual Private Clouds (VPCs) can be connected to multiple gateways
or VPNs.
 It helps maintain continuous connectivity between on-premise
systems and cloud networks (hybrid cloud).
Example:
An AWS VPC can connect to both:
 Internet Gateway (for public traffic)
 Direct Connect or VPN Gateway (for private connection)
This setup ensures traffic continues to flow even if one path fails.

Benefits
 Redundancy: Continuous operation even if one ISP fails.
 Load Balancing: Distributes data across multiple links for efficiency.
 Improved Performance: Chooses the fastest route dynamically.
 Fault Tolerance: Ensures network reliability and uptime.
 ISP Independence: Avoids dependency on a single provider.

Challenges:
 Complex configuration (especially with BGP)
 Higher cost due to multiple ISP connections
 Requires skilled network management
 Potential routing conflicts or inefficiencies if misconfigured.

The End