Virtualiazation----

1. Defi
2. Levels
Operating system based Virtualization
Operating System-based Virtualization is also known as
Containerization. It allows multiple isolated user-space instances
called containers to run on a single operating system (OS) kernel.

OS
Based Virtualization
Note: Unlike traditional virtualization, where each VM requires its
own OS, OS-based virtualization allows the sharing of the same OS
while providing separate environments for running applications.
OS-Based Virtualization works as follows:
 The host OS kernel is shared among all containers, unlike full
virtualization (e.g., VMs) where each VM has its own kernel.
 The kernel enforces isolation between containers using
namespaces (for process, network, filesystem isolation) and
cgroups (control groups) for resource allocation (CPU, memory,
disk I/O, network).
  cgroups limit and prioritize resource usage (CPU, memory, disk,
network) per container.
 The kernel ensures that a container cannot exceed its allocated
resources (unless explicitly allowed).
 Namespaces prevent processes in one container from seeing or
interfering with processes in another.
 Programs inside a container cannot access resources outside
unless explicitly granted (e.g., mounted volumes, network
ports).
 The overhead comes from kernel-level isolation mechanisms
(namespaces, cgroups), but it’s minimal compared to full
virtualization.
Pros of OS-Based Virtualization
 Resource Efficiency: Operating system based virtualization
allows for greater resource efficiency as containers do not need
to emulate a complete hardware environment, which reduces
resource overhead.
 High Scalability: Containers can be quickly and easily scaled up
or down depending on the demand, which makes it easy to
respond to changes in the workload.
 Easy Management: Containers are easy to manage as they can
be managed through simple commands, which makes it easy to
deploy and maintain large numbers of containers.
 Reduced Costs: Operating system based virtualization can
significantly reduce costs, as it requires fewer resources and
infrastructure than traditional virtual machines.
  Faster Deployment: Containers can be deployed quickly,
reducing the time required to launch new applications or
update existing ones.
 Portability: Containers are highly portable, making it easy to
move them from one environment to another without requiring
changes to the underlying application.
Cons of OS-Based Virtualization
 Security: Operating system based virtualization may pose
security risks as containers share the same host operating
system, which means that a security breach in one container
could potentially affect all other containers running on the
same system.
 Limited Isolation: Containers may not provide complete
isolation between applications, which can lead to performance
degradation or resource contention.
 Complexity: Operating system based virtualization can be
complex to set up and manage, requiring specialized skills and
knowledge.
 Dependency Issues: Containers may have dependency issues
with other containers or the host operating system, which can
lead to compatibility issues and hinder deployment.
 Limited Hardware Access: Containers may have limited access
to hardware resources which can limit their ability to perform
certain tasks or applications that require direct hardware
access.
Levels of Virtualization — (WHERE virtualization happens)
👉 These describe the layer at which virtualization is implemented.
These are mostly 5 levels:
1. Instruction Set Architecture (ISA) Level
2. Hardware Abstraction Level (System Level)
3. Operating System Level (Container Level)
4. Library Support Level
5. User/Application Level

⭐ ISA-Level Virtualization (5 Easy Points)

1. Emulates One ISA on Another
ISA virtualization allows running programs made for one CPU
architecture (e.g., MIPS, ARM) on a different architecture (e.g., x86)
using instruction emulation.
2. Supports Legacy Programs
Helps execute old/legacy binary code on new hardware without
modification, improving compatibility across platforms.
3. Uses Code Interpretation or Emulation
The simplest method is interpreting each instruction one by one, but
this is slow because many target instructions are required for one
source instruction.
4. Uses Dynamic Binary Translation for Speed
Faster implementations translate blocks of source instructions into
native instructions at runtime, improving execution speed.
5. Creates a Virtual ISA (V-ISA)
A software translation layer is added so applications behave as if they
are running on their original processor, even though the actual
hardware is different.
Hardware-Based Virtualization – Easy & Good Points (5–6 Points)
 It uses hardware support (like Intel VT-x, AMD-V) to run virtual
machines efficiently without modifying the guest operating
system.
 Full virtualization is achieved by simulating a complete
hardware environment, so the guest OS runs exactly as it
would on a real physical machine.
 The hypervisor/VMM manages CPU, memory, storage, and I/O,
providing a virtual hardware layer for each VM.
 This method allows guest OS to interact with hardware directly
through the hypervisor, without going through a host OS,
making it faster and more secure.
 It offers strong isolation, because each VM behaves like an
independent machine with its own OS and resources.
 Hardware-based virtualization is more efficient than OS-based
virtualization because it does not rely on the host OS for
resource management.
Library Support Level Virtualization (5 Good Points)
 Most applications use user-level libraries/APIs instead of
directly calling the operating system, so these APIs can be
virtualized.
 Virtualization is done by intercepting and controlling API calls
between the application and the OS, called API hooking.
 It allows applications written for one environment to run in
another environment without changes.
 A popular example is WINE, which runs Windows applications
on UNIX/Linux by virtualizing Windows API calls.
 Another example is vCUDA, which allows applications inside
VMs to use GPU acceleration even if the physical GPU is on the
host machine.
User/Application-Level Virtualization (5 Good Points)
 Application-level virtualization virtualizes only the application,
not the entire operating system or hardware.
 It is also called process-level virtualization, because each
virtualized application runs as a separate isolated process.
 A virtualization layer sits on top of the OS and provides an
abstract execution environment for applications.
 It mainly works through High-Level Language (HLL) virtual
machines, where programs run on a virtual runtime instead of
directly on the OS.
 Common examples include Java Virtual Machine (JVM) and
Microsoft .NET CLR, which allow applications to run on any
system that supports the runtime.
Merits of Virtualization at Various Levels
1. Instruction Set Architecture (ISA) Level
 Allows old/legacy programs (e.g., MIPS, ARM) to run on new
hardware without modification.
 Provides portability because binaries can be translated to run
on different CPUs.

2. Hardware Level Virtualization

 Enables high performance because VMs interact directly with
hardware.
 Improves hardware utilization by allowing multiple VMs to
share CPU, memory, and I/O efficiently.

3. Operating System Level Virtualization (Containers)

 Very lightweight and fast because all containers share the same
OS kernel.
 Highly scalable since hundreds of containers can run with very
low resource overhead.
 4. Library Support Level Virtualization
 Allows applications to run on different OS environments using
API translation (e.g., WINE).
 Reduces need for full OS emulation, giving better performance
for specific applications.

5. User/Application Level Virtualization

 Enables applications written in Java/.NET to run anywhere via
JVM/CLR.
 Provides strong isolation: each application runs in a sandboxed
virtual machine.

 TOOLS AND MECHANISMS FOR

VIRTUALIZATION (10 Marks — Easy
Version)
 (Perfect for AKTU exams, using only your studied topics)


 ✅ A. MECHANISMS OF
VIRTUALIZATION (HOW IT
WORKS)
 1. Hypervisor Mechanism
 A hypervisor (VMM) creates and manages virtual machines by allocating CPU,
memory, and I/O resources. It ensures isolation so that multiple VMs can run safely
on one physical system.
 2. CPU Virtualization Mechanism
 The hypervisor divides CPU time among virtual machines using scheduling. It traps
privileged instructions and emulates them so each VM feels it has its own processor.
 3. Memory Virtualization Mechanism
  The hypervisor maps each VM’s virtual memory to physical memory using shadow
page tables. This allows each VM to use its own address space without interfering
with others.
 4. Storage Virtualization Mechanism
 Physical disks are abstracted into virtual disks (VMDK, VHD). This allows multiple
VMs to share storage and makes migration, backup, and replication easier.
 5. Network Virtualization Mechanism
 Virtual switches and virtual network adapters create isolated network environments
for each VM. This allows multiple VMs to communicate as if they are on separate
physical networks.
 6. Application-Level Virtualization Mechanism
 Applications run inside isolated runtimes (like JVM or .NET CLR) without
interacting with the underlying OS directly. This prevents library conflicts and
improves portability.
 7. Container Mechanism (OS-Level Virtualization)
 Containers use namespaces for isolation and cgroups for resource limits. They run
multiple applications in isolated user spaces while sharing the same OS kernel.


 ✅ B. TOOLS FOR VIRTUALIZATION

(WHAT IS USED)
 1. Hypervisor Tools
 Tools like VMware ESXi, Microsoft Hyper-V, and VirtualBox allow creation and
management of virtual machines. They provide features like snapshots, cloning, and
VM migration.
 2. Server Virtualization Tools
 VMware vSphere and KVM allow running multiple server instances on a single
physical server. These tools reduce hardware cost and improve utilization.
 3. Desktop Virtualization Tools
 Tools such as VMware Horizon and Citrix Virtual Desktop deliver virtual desktops to
users. These allow centralized desktop management and secure remote access.
 4. Network Virtualization Tools
 Virtual network components like VMware vSwitch and Hyper-V Virtual Switch
simulate routers, firewalls, and switches within the virtual environment.
 5. Storage Virtualization Tools
 Virtual disk systems such as VMware VMFS or Microsoft Storage Spaces combine
multiple disks into one logical pool to store VM files efficiently.
 6. Application Virtualization Tools
 Tools like Java Virtual Machine (JVM), .NET CLR, and VMware ThinApp run
applications in isolated environments, preventing dependency conflicts.

Hypervisor
Last Updated : 18 Sep, 2025

 

A hypervisor (or Virtual Machine Monitor, VMM) is software that lets

multiple operating systems run on a single physical machine. It
manages hardware resources (CPU, memory, storage) and allocates
them to virtual machines (VMs) without interference. This improves
hardware utilization, reduces costs, and provides flexibility in cloud
and server environments.
How It Works
A hypervisor runs on hardware or a host OS to create and manage
virtual machines (VMs), each with its own virtual CPU, memory,
storage, and network. It intercepts guest OS requests and translates
them to physical hardware, ensuring isolation, security, and stability.
Types of Hypervisor
There are two main types of hypervisors, each with a different
architecture:
1. Type 1 Hypervisor
A Type 1 hypervisor runs directly on the host's hardware. It doesn't
rely on a host operating system. This architecture offers better
performance and security because there is no intermediary OS. It's
the standard for enterprise-level data centers and cloud providers
like Amazon Web Services (AWS) and Microsoft Azure.
Examples: VMware ESXi, Microsoft Hyper-V, KVM (Kernel-based
Virtual Machine), and Xen.
Pros:
 High performance (direct hardware access).
 Strong security (no intermediate OS layer).
 Suitable for mission-critical workloads.
Cons:
 Requires dedicated hardware.
  Setup and management are complex compared to Type-2.
2. Type 2 Hypervisor
A Type 2 hypervisor runs on top of a conventional operating system
(like Windows, macOS, or Linux). It's essentially an application within
the host OS. This type is generally used for desktop virtualization,
development, and testing environments where a user needs to run
multiple OSs on their personal computer. Performance is slightly
lower than Type 1 due to the overhead of the host OS.
Examples: Oracle VM VirtualBox, VMware Workstation, and Parallels
Desktop.
Pros:
 Easy to install and use.
 Useful for development, testing, and malware analysis.
 Provides good host–guest integration features.
Cons:
 Slower performance (no direct hardware access).
 Security depends on the host OS; compromise of host may
affect guests.
HYPERVISOR REFERENCE MODEL
There are 3 main modules coordinates in order to emulate the
underlying hardware:
 DISPATCHER: The dispatcher behaves like the entry point of the
monitor and reroutes the instructions of the virtual machine
instance to one of the other two modules.
 ALLOCATOR: The allocator is responsible for deciding the
system resources to be provided to the virtual machine
instance. It means whenever a virtual machine tries to execute
an instruction that results in changing the machine resources
associated with the virtual machine, the allocator is invoked by
the dispatcher.
 INTERPRETER: The interpreter module consists of interpreter
routines. These are executed, whenever a virtual machine
executes a privileged instruction.
⭐ How do you manage the resources in a virtual environment?
(10 Marks)
(With headings + explanation + clean points — exactly how
examiners expect)

✅ Managing Resources in a Virtual Environment

In a virtual environment, multiple virtual machines (VMs) or
containers share the same underlying physical hardware.
Therefore, resource management is essential to ensure fairness,
performance, security, and efficient hardware utilization.
Effective resource management is performed by the hypervisor,
management tools, and monitoring systems that allocate,
control, and optimize virtualized resources like CPU, memory,
storage, and network.

⭐ 1. CPU Resource Management

 The hypervisor uses CPU scheduling to distribute processor
time among VMs.
 Techniques like time slicing, CPU pinning, and priority-based
scheduling ensure fair performance.
 CPU limits and reservations can be set → prevents one VM from
monopolizing the processor.
 Hypervisors also support virtual CPUs (vCPU), mapping them
efficiently to physical CPUs.
 ⭐ 2. Memory Resource Management
 Hypervisors allocate a fixed or dynamic memory size to each
VM.
 Memory ballooning returns unused VM memory to the host
when required.
 Memory overcommitment allows more virtual memory to be
allocated than physically present, improving utilization.
 NUMA-aware allocation ensures memory is assigned close to
the physical CPU for performance.

⭐ 3. Storage Resource Management

 Storage is managed using virtual disks such as VMDK, VHD,
QCOW2.
 Hypervisors provide thin provisioning to allocate storage only
when used, saving space.
 Storage tiers (SSD/HDD) improve performance for critical VMs.
 Snapshot and cloning features help in backup, recovery, and
testing.

⭐ 4. Network Resource Management

 Virtual switches and NICs (vNICs) isolate traffic between VMs.
 Bandwidth throttling prevents any VM from occupying entire
network bandwidth.
 VLANs, firewalls, and SDN (Software Defined Networking)
improve segmentation and security.
 Load balancers distribute traffic across VMs for high availability.

⭐ 5. Resource Monitoring and Performance Tracking

 Tools like VMware vCenter, Hyper-V Manager, Proxmox,
OpenStack monitor CPU, memory, disk, and network usage.
 Alerts and thresholds help detect overloaded or underutilized
VMs.
 Monitoring ensures proactive resource adjustments based on
workload.

⭐ 6. Dynamic Resource Allocation (DRA)

 Hypervisors automatically adjust VM resources based on real-
time demand.
 Features like VMware DRS (Distributed Resource Scheduler)
balance VMs across hosts.
 Ensures optimal performance without manual intervention.

⭐ 7. Live Migration for Load Balancing

 VMs can be moved from one host to another using Live
Migration or vMotion.
 Migration helps handle hardware failures, perform
maintenance, and balance resource usage.
 Ensures zero downtime while shifting VMs to healthier hosts.

⭐ 8. Resource Pooling and Quotas

 Administrators create resource pools to group CPU, memory,
and storage.
 Quotas ensure each department/team receives guaranteed
resources.
 Prevents resource starvation and improves fairness in multi-
tenant environments.

⭐ 9. Security-Based Resource Management

 Firewall rules, isolation mechanisms, and access-control policies
restrict unauthorized resource usage.
 Ensures safe sharing of hardware in multi-tenant cloud
environme Advantages of Virtualization (2 Lines Each)

 1. Cost-Effective
 Virtualization reduces the need for buying and maintaining
physical hardware, making IT setup cheaper. You only need
licenses and remote access instead of building full on-site
infrastructure.
 2. Efficient Operation
 Software and hardware can be updated automatically, reducing
maintenance work. It simplifies resource management and
increases the efficiency of virtual environments.
 3. Better Disaster Recovery
 VMs can be backed up, cloned, or restored quickly using
snapshots. Even during major failures, VMs can be moved to
cloud servers, ensuring high recovery success.
 4. Faster Deployment
 New VMs or resources can be created in minutes without
installing physical devices. This speeds up application
deployment and reduces setup time.
 5. Supports Digital Entrepreneurship
 Anyone can start digital services easily using virtual servers and
cloud tools. Virtualization removes the barrier of needing
expensive physical infrastructure.
 6. Saves Energy
 Since fewer physical machines are used, electricity and cooling
costs drop significantly. This improves long-term ROI and
reduces environmental impact.
 7. Improved Uptime
 Modern virtualization platforms offer 99.99% or higher uptime
guarantees. This ensures continuous access to resources with
minimal downtime.
 8. Predictable Costs
 Virtualization services come with fixed monthly or yearly
pricing. This makes budgeting easier for individuals and
businesses.


 ⭐ Disadvantages of Virtualization (2 Lines Each)

 1. High Initial Implementation Cost
 Although users save money, service providers must invest
heavily in hardware and infrastructure. This makes backend
implementation expensive.
 2. Compatibility Limitations
 Not all applications and servers support virtualization. Some
systems require hybrid setups because they cannot be fully
virtualized.
 3. Availability Issues
 If the virtual server goes offline, all hosted websites and
services become unavailable. Users depend completely on the
third-party provider’s uptime.
 4. Time-Consumption
 Even though deployment is fast, solving issues in virtual systems
may require extra steps. Managing additional layers increases
troubleshooting time.
 5. Security Risks
 Virtual environments are attractive targets for cyber-attacks. If a
vulnerability exists in the hypervisor or cloud provider, multiple
VMs can be affected.
 6. Scalability Challenges
 Growth can cause latency because multiple clients share the
same infrastructure. Resource-heavy customers may impact
smaller users in shared environments.
 7. Dependency on Multiple Connections
 Virtualization requires stable internet and coordinated cloud
systems. Without strong network links, simple tasks like saving
files become slow or impossible.

Features Full ParaVirtualizati

Virtualization on
Definition It is the first The interaction
generation of of the guest
software operating
solutions for system with the
server hypervisor to
virtualization. improve
performance
and
productivity is
known as
paravirtualizatio
n.

Security It is less secure It is more

than secure than full
paravirtualizati virtualization.
on.

Performanc Its performance Its performance

e is slow than is high than full
paravirtualizati virtualization.
on.

Guest OS It supports all The Guest OS

Modificatio the Guest OS has to be
n without any modified in
change. paravirtualizatio
n, and only a
few OS support
it.
 Guest OS It enables the It enables the
hypervisor Guest OS to run Guest OS to
independe independently. interact with
nt the hypervisor.

Potable It is more It is less

and portable and portable and
Compatible compatible. compatible.

Isolation It offers It offers less

optimum isolation.
isolation.

Efficient It is less It is more

efficient than simplified than
paravirtualizati full
on. virtualization.

Characteris It is software It is cooperative

tic based. virtualization.

Examples It is used in It is mainly used

Microsoft, in VMware and
VMware, and Xen systems.
Parallels
systems.

FULL VIRTUALIZATION
• In full virtualization, the guest operating system is unaware that
it’s running in a virtualized environment.
• The hypervisor presents a virtualized hardware environment to
the guest operating system, mimicking the underlying physical
hardware.
• Full virtualization provides broad compatibility with unmodified
guest operating systems but may incur performance overhead
due to hardware emulation.
• Examples of full virtualization include VMware ESXi with Intel
VT-x/AMD-V hardware-assisted virtualization
PARA VIR:-
• In para virtualization, the guest operating system is aware of its
virtualized environment and interacts with the hypervisor
through special paravirtualized drivers via hypercall.
• However, para virtualization requires modifications to the guest
operating system to support paravirtualized drivers.
• Paravirtualization eliminates the need for hardware emulation,
resulting in lower overhead and improved performance
compared to full virtualization.
• Examples of para virtualization include Xen hypervisor with
Xen-aware guest operating systems
 PARTIAL VIRTU:-
• Partial virtualization is a technique where the virtual machine
(VM) doesn't fully emulate the hardware stack, allowing it to
run some applications directly on the physical hardware for
improved performance. It is distinct from full virtualization,
which emulates the entire hardware stack, and is often a
precursor to full virtualization

• CPU Virtualization (Definition)

• CPU Virtualization allows multiple virtual CPUs (vCPUs) to run on top of a single
physical CPU by using hypervisor techniques such as trap-and-emulate, binary
translation, and hardware extensions (Intel VT-x, AMD-V). It gives each VM the
illusion of having its own dedicated processor.
•

• ⭐ Advantages / Pros of CPU

Virtualization (7 Points)
• 1. Efficient CPU Utilization
• Physical CPU time is shared among VMs, reducing idle processor cycles.
• 2. Isolation Between VMs
• Each VM gets its own vCPU environment, preventing interference between
workloads.
• 3. Supports Multiple OS on One CPU
• Different operating systems can run simultaneously using virtual CPUs.
• 4. Enables Server Consolidation
• Many lightly-loaded servers can be combined on one machine, reducing hardware
cost.
• 5. Hardware Independence
• Guest OS does not need to know the CPU architecture changes due to hypervisor
abstraction.
• 6. Supports Load Balancing & Migration
• Hypervisors can move vCPUs between physical cores dynamically for better
performance.
• 7. Improves Testing & Development
• Developers can simulate multiple CPU environments on a single host for testing.
•

• ⭐ Disadvantages / Cons of CPU

Virtualization (7 Points)
• 1. Performance Overhead
• VMs may run slower than native hardware due to instruction trapping and scheduling
delays.
• 2. CPU Contention
• If many VMs compete for CPU cycles, performance may degrade.
• 3. Complex Scheduling
• Hypervisor must constantly schedule vCPUs to physical CPUs, increasing
complexity.
• 4. Requires Special Hardware Support
• Needs virtualization-enabled CPUs (Intel VT-x/AMD-V); older CPUs cannot support
it.
• 5. Risk of CPU Starvation
• Improper configuration can cause some VMs to get insufficient CPU time.
• 6. Increased Latency for Real-Time Tasks
• Time-sensitive applications may suffer delays under virtualized CPU environments.
• 7. Security Vulnerabilities
• CPU side-channel attacks (e.g., Spectre, Meltdown) may affect multiple VMs on the
same physical CPU.

• Common Pitfalls of Virtualization (7–8

points, 2 lines each)
• (Perfect for 10 marks)
• 1. Performance Overhead
• Virtual machines add extra CPU, memory, and I/O overhead because instructions
must pass through the hypervisor. This reduces performance compared to bare-metal
systems.
• 2. Resource Contention
• Multiple VMs compete for CPU, memory, and disk resources. If not managed
properly, one VM can slow down others.
• 3. Single Point of Failure (SPoF)
• If the physical host crashes, all VMs on it also go down, causing multiple services to
fail simultaneously.
• 4. Security Risks
• A vulnerability in the hypervisor can compromise all VMs. Multi-tenant
environments increase risk of attacks like side-channel and VM escape.
• 5. Complexity of Management
• Managing many VMs, virtual networks, and storage layers increases administrative
complexity. Misconfiguration can cause failures.
• 6. Licensing Issues
• Some software licenses are not virtualization-friendly. Extra fees or restrictions may
apply for running applications inside VMs.
• 7. VM Sprawl
• VMs can be created very easily, often leading to uncontrolled growth. This causes
resource waste, security gaps, and management overhead.
• 8. Backup and Recovery Challenges
• Backing up VMs requires specialized tools and more storage. Large VMs make
replication and migration slower.
1. Definition of VMM (Virtual Machine Monitor)
 A Virtual Machine Monitor (VMM), also called a Hypervisor, is the software layer
that creates, runs, and manages Virtual Machines (VMs).
 It allocates CPU, memory, storage, and I/O resources to each VM while ensuring
isolation between them.

2. Requirements of VMM (Very Important Short Question)

Write these 5 points (2 lines each if needed):
✔ 1. Strong Isolation
VMM must keep all VMs completely isolated so one VM cannot affect or crash
another.
✔ 2. Efficient Resource Allocation
Must distribute CPU, memory, disk, I/O fairly and efficiently among VMs.
✔ 3. Performance with Low Overhead
Must run VMs with near-native performance with minimal resource overhead.
✔ 4. Control & Monitoring
Must monitor VM status, start/stop/migrate VMs, and track resource usage.
✔ 5. Security & Protection
Ensure secure access, protect VMs from unauthorized access, and manage virtualized
hardware safely.

3. Responsibilities of VMM (Write 5 points in exam)

✔ 1. VM Creation & Management
Creates VMs, boots guest OS, handles execution, suspends and resumes VMs.
✔ 2. Resource Scheduling
Schedules CPU, memory, network, and disk resources for each virtual machine.
✔ 3. Hardware Abstraction
 Provides a virtual hardware environment so each VM thinks it has its own CPU,
RAM, and devices.
✔ 4. Isolation & Protection
Enforces strong isolation between VMs and prevents malicious or faulty behavior.
✔ 5. Performance Optimization
Uses techniques like caching, shadow paging, ballooning, and para-virtual drivers to
improve performance.

4. Difference Between Host OS and Guest OS (Short Answer for 2–3 marks)
Host OS
A host operating system is a piece of software that runs on a computer and allows it to
communicate with its hardware. It has the ability to run a type 2 hypervisor. Type 2
hypervisors, in other words, run on the host operating system.
Container-based virtualization may also be used by the host OS. The logical
partitioning of server programs is aided by the use of containers. As a result,
containers can be used without requiring each application to have its own operating
system. It enables apps to share the operating system kernel while accessing distinct
hardware resources. This form of the shared operating system is also known as a host
operating system.
Features of Host Operating System
 Hardware Abstraction: Host OS enables communication between software and
hardware using a common language.
 Resource Management: Host OS efficiently manages CPU, memory, and disk space
allocation among running programs.
 File System Management: Host OS organizes and maintains files and folders for
easy access and structured data storage.
 Security: Host OS implements locks, firewalls, and safeguards to protect against
unauthorized access and malware.

Guest Operating System

Hypervisors of type 2 can produce several Virtual Machines.
Each computer has its own operating system, which is referred
to as the guest OS. In other words, a guest OS is a piece of
software that runs inside a virtual machine. As a result, the
guest operating system is run by a virtual machine.
In virtualization, the guest operating system differs from the
host operating system in numerous respects, and it can be
used as a portioned system component or a virtual machine
part. It's primarily used for apps that run on a different
operating system.

Features of Guest Operating System

 Application Support: Guest OS runs applications in the virtual environment.

 Hardware Abstraction: Guest OS mediates between applications and hardware

using standardized interfaces.

 Resource Management: Guest OS efficiently manages system resources in the

virtual environment.

 Device Driver Support: Guest OS includes drivers for communication with virtual
hardware.

 Virtualization Support: Guest OS is designed for virtualized environments and

manages virtual machines.

 1. What is OS Extension? (2–3 Lines)

 OS Extension means adding extra modules or drivers inside the
existing host operating system so that it can support
virtualization features (like VM management, para-virtualization
calls, or improved hardware access).
It modifies the host OS to allow better interaction between
VMs and hardware.


 ⭐ Advantages of OS Extension (Any 3)

 Better performance: VMs run faster because the OS directly
helps manage virtualization tasks.
 Low overhead: No need to emulate everything — system calls
become faster.
 Good integration: Hardware and OS communicate smoothly,
making virtualization efficient.


 ⭐ Disadvantages of OS Extension (Any 4)

 Less isolation: Because the host OS is modified, security
boundaries between VM and host become weaker.
 Compatibility issues: Modified OS may not support all guest OS
types.
 Maintenance difficulty: Updating or patching the OS becomes
more complex.
 Single point of failure: If the host OS crashes, all VMs stop
immediately

 1. KVM (Kernel-based Virtual Machine)
✅ Definition
KVM is an open-source hypervisor that turns the Linux kernel
into a Type-1 (bare-metal) virtual machine monitor using
hardware virtualization extensions like Intel VT-x or AMD-V.
It allows Linux to run multiple isolated virtual machines, each
with its own OS.

⭐ Advantages of KVM (5 Points)

1. High Performance: Uses hardware virtualization (VT-x/AMD-V),
giving near-native speed.
2. Strong Security: Inherits Linux kernel security (SELinux,
cgroups, namespaces).
3. Scalable: Supports large-scale cloud environments (OpenStack
uses KVM).
4. Open Source & Free: No licensing cost, easy customization.
5. Full Hardware Support: Supports live migration, snapshots,
CPU pinning, NUMA, and advanced networking.

⭐ Disadvantages of KVM (5 Points)

1. Complex Setup: Configuration requires Linux expertise.
2. Host OS Dependency: Performance depends heavily on Linux
kernel stability.
3. Higher Resource Use: Needs a powerful CPU/RAM for multiple
VMs.
4. Steep Learning Curve: Difficult for beginners compared to
VMware.
5. Limited GUI Tools: Fewer graphical management tools
compared to paid hypervisors.

🟩 2. Xen Hypervisor
✅ Definition
Xen is an open-source Type-1 hypervisor that runs directly on
hardware and supports both full virtualization and para-
virtualization. It provides strong isolation and is widely used in
cloud platforms like AWS (old generation).

⭐ Advantages of Xen (5 Points)

1. High Isolation & Security: Separation between Dom0 (control
domain) and DomU (guest VMs) ensures strong isolation.
2. Supports Full & Para Virtualization: Works even on systems
without hardware virtualization.
3. Stable & Mature: Used in enterprise clouds like AWS,
Rackspace, Citrix.
4. Efficient Resource Usage: Para-virtualized VMs reduce
overhead.
5. Live Migration Support: Enables continuous service during VM
relocation.

⭐ Disadvantages of Xen (5 Points)

1. Complex Architecture: Dom0/DomU structure makes
configuration difficult.
2. Performance Overhead in Full Virtualization: Software
emulation slows down VM performance.
3. Limited Windows Support: Para-virtualization cannot run
unmodified Windows OS.
4. Less Community Adoption: KVM and VMware dominate
modern deployments.
5. Harder Troubleshooting: Debugging Dom0 and DomU issues
can be complicated.

Unit-5
Security Issues in Cloud Computing :
There is no doubt that Cloud Computing provides various Advantages
but there are also some security issues in cloud computing. Below are
some following Security Issues in Cloud Computing as follows.
1. Data Loss -
Data Loss is one of the issues faced in Cloud Computing. This is also
known as Data Leakage. As we know that our sensitive data is in the
 hands of Somebody else, and we don't have full control over our
database. So, if the security of cloud service is to break by hackers then it
may be possible that hackers will get access to our sensitive data or
personal files.

2. Interference of Hackers and Insecure API's -

As we know, if we are talking about the cloud and its services it means
we are talking about the Internet. Also, we know that the easiest way to
communicate with Cloud is using API. So it is important to protect the
Interface's and API's which are used by an external user. But also in cloud
computing, few services are available in the public domain which are the
vulnerable part of Cloud Computing because it may be possible that
these services are accessed by some third parties. So, it may be possible
that with the help of these services hackers can easily hack or harm our
data.

3. User Account Hijacking -

Account Hijacking is the most serious security issue in Cloud Computing.
If somehow the Account of User or an Organization is hijacked by a
hacker then the hacker has full authority to perform Unauthorized
Activities.

4. Changing Service Provider -

Vendor lock-In is also an important Security issue in Cloud Computing.
Many organizations will face different problems while shifting from one
vendor to another. For example, An Organization wants to shift
from AWS Cloud to Google Cloud Services then they face various
problems like shifting of all data, also both cloud services have different
techniques and functions, so they also face problems regarding that.
Also, it may be possible that the charges of AWS are different from
Google Cloud, etc.

5. Lack of Skill -
While working, shifting to another service provider, need an extra
 feature, how to use a feature, etc. are the main problems caused in IT
Companies who doesn't have skilled Employees. So it requires a skilled
person to work with Cloud Computing.

6. Denial of Service (DoS) attack -

This type of attack occurs when the system receives too much traffic.
Mostly DoS attacks occur in large organizations such as the banking
sector, government sector, etc. When a DoS attack occurs, data is lost.
So, in order to recover data, it requires a great amount of money as well
as time to handle it.
7. Shared Resources: Cloud computing relies on a shared infrastructure. If
one customer's data or applications are compromised, it may potentially
affect other customers sharing the same resources, leading to a breach
of confidentiality or integrity.
8. Compliance and Legal Issues: Different industries and regions have
specific regulatory requirements for data handling and storage. Ensuring
compliance with these regulations can be challenging when data is
stored in a cloud environment that may span multiple jurisdictions.
9. Data Encryption: While data in transit is often encrypted, data at rest
can be susceptible to breaches. It's crucial to ensure that data stored in
the cloud is properly encrypted to prevent unauthorized access.
[Link] Threats: Employees or service providers with access to cloud
systems may misuse their privileges, intentionally or unintentionally
causing data breaches. Proper access controls and monitoring are
essential to mitigate these threats.

AWS Identity and Access Management (IAM) is a security service that

enables you to securely control access to AWS services and resources.
IAM allows you to define who is authenticated (signs in) and who is
authorized (has permissions) to use specific AWS resources. It forms the
backbone of security in any AWS environment.
 When you create an AWS account, AWS provides a root user, which has
unrestricted access to all services. IAM enables you to move away from
using the root user by creating individual IAM users, groups, and roles,
each with specific permissions.
Key Features of IAM
✔ 1. Centralized Access Control
You can manage all users, groups, roles, and permissions from a single,
centralized console.
✔ 2. Granular (Fine-Grained) Permissions
IAM policies allow you to define highly specific permissions, such as:
 Which actions (e.g., ec2:StartInstances)
 On which resources (e.g., a specific EC2 instance)
 Under what conditions
✔ 3. Global Service
IAM is not region-specific. IAM identities (users, groups, roles) are
created at a global level and apply across all AWS regions.
✔ 4. Free to Use
IAM is provided at no additional cost. You only pay for the AWS
resources accessed through IAM.
What is Secure Software Development Life Cycle (SSDLC )?
Last Updated : 9 Aug, 2025


Secure Software Development Life Cycle (SSDLC) ensures that computer

programs are built with security in mind right from the beginning.
 It involves planning, designing, coding, testing, deploying, and
maintaining software while consistently addressing security concerns at
each step.
 Crucial to identify and fix security issues early, reducing the risk of cyber
threats. By integrating security measures throughout the development
process,
Phases of Secure SDLC:
 Planning: In the planning stage, the main focus is on figuring out the
security requirements for the software. This includes identifying possible
risks and creating a plan for how to make the software secure from the
beginning.
 Design: During the design phase, the plan for security is put into action.
This involves making decisions about how to build security features into
the software. The goal is to ensure that the design can handle potential
security problems.
 Implementation: In the implementation phase, developers start building
the software using secure coding practices. This means writing code in a
way that reduces the chances of security problems. Code reviews are
done to catch and fix any security issues.
 Testing: Testing is all about checking how secure the software is.
Different tests are done, like trying to break into the software to find
vulnerabilities, scanning the code for potential problems, and making
sure the software can handle different security threats.
 Deployment: Deployment is when the software is released. Here, the
focus is on making sure the release process is secure, taking precautions
to avoid any security issues during this stage.
 Maintenance: Maintenance is an ongoing process where the software is
continuously looked after. This involves keeping an eye on security and
regularly updating the software to deal with new threats, making sure it
stays secure over time.
 SOFTWARE AS A SERVICE SECURITY
• SaaS security focuses on protecting data, applications, and user identities
in the cloud.
• It is a shared responsibility: the SaaS provider secures the application's
infrastructure, while the customer is responsible for configuring the
application's security settings and managing user access.
• SaaS security aims to reduce risks like unauthorized access and data
exposure while enhancing the security of SaaS applications.
• Organizations are increasingly moving to cloud-based solutions. So SaaS
security became very crucial.
• SaaS security is essential for several reasons:

• Protecting Sensitive Data

• Compliance Requirements

• Preventing Cyber Threats

• Building Trust

Pillars of saas security

Foundational or core pillars(CIA triads)
• Confidentiality: Ensures that sensitive information is only accessible to
authorized individuals, preventing data leaks and unauthorized viewing.
• Integrity: Guarantees that data remains accurate and unchanged,
protecting against unauthorized modifications.
• Availability: Ensures that systems and data are accessible to users when
needed, minimizing downtime and service disruptions.
Operational pillars
• Identity and Access Management (IAM): Controls who can access cloud
resources, using methods like role-based access controls and multi-factor
 authentication to ensure only authorized users have the necessary
permissions.
• Data Protection: Implements measures to secure data, such as
encryption for data in transit and at rest, and regular backups.
• Network Security: Protects the network infrastructure through firewalls,
intrusion detection and prevention systems, and secure configurations.
• Compliance and Governance: Ensures adherence to relevant industry
regulations and legal frameworks (e.g., GDPR, SOC 2) through
monitoring, logging, and automated controls.
• Threat Detection and Response: Includes monitoring for unusual
activities using tools like SIEM or XDR, and having a clear incident
response plan to handle and recover from security incidents.
• Configuration and Posture Management: Focuses on securing the cloud
environment itself through tools that enforce rules, fix
misconfigurations, and manage security settings to prevent
vulnerabilities
6. Explain the Application Security in Detail
(10-marks | Based entirely on PPT)
Application security in cloud computing deals with protecting SaaS
applications, web services, and APIs from attacks, unauthorized access,
and data breaches. The PPT focuses on cloud application security layers,
identity frameworks, and security standards that ensure safe
communication between users and cloud applications.

1. Identity and Authentication Standards

Cloud applications depend on strong identity control. The PPT highlights
the following:
✔ SAML (Security Assertion Markup Language)
 XML-based framework for authentication and authorization.
 Allows identity information to be shared across different applications
securely.
✔ OAuth
 Open standard for secure token-based authorization.
 Allows secure access to APIs without sharing passwords.
✔ OpenID
 Supports Single Sign-On (SSO).
 Users authenticate once and access multiple cloud applications.

2. Transport Security Standards

✔ SSL / TLS
 Provide secure communication between client and server.
 Protects applications from eavesdropping and man-in-the-middle
attacks.

3. Messaging and Communication Standards

Cloud apps rely on secure messaging protocols (given in PPT):
 SMTP, POP, IMAP – secure email communication
 RSS, XMPP – for data feeds and messaging
 These ensure application-to-application and user-to-application secure
communication.

4. Access Control & IAM Integration

 PPT shows IAM as an essential pillar for SaaS application protection.
 Enables role-based access control (RBAC), MFA, and policy-based access.
 5. Application Configuration Security
 Hardening SaaS configurations
 Restricting default permissions
 Enforcing encryption policies
These reduce security vulnerabilities mentioned in the PPT.

6. Protection from Cloud Threats

Application security ensures protection from:
 Malware
 Cross-site scripting (XSS)
 SQL injection
 Session hijacking
 Data theft
Cloud apps implement continuous monitoring, logging, and anomaly
detection (explained under security controls in PPT).

Conclusion
Application security ensures that cloud applications remain safe,
available, and trusted by using:
 Identity frameworks
 Transport security
 Messaging standards
 Access control
 Monitoring and governance
This completes the application security explanation exactly as in PPT.
 ✅ 7. Explain Data Security and Virtual Machine Security in Detail
(10-marks | From PPT only)

🔷 A. Data Security
Data security ensures confidentiality, integrity, and availability of
information stored in the cloud.

1. Data Protection Techniques (From PPT)

 Encryption (at rest & in transit)
 Access control through IAM
 Secure messaging standards (SSL/TLS, SAML, OAuth)
 Data governance, retention policies, and compliance enforcement

2. Secure Communication
 PPT stresses the use of SSL/TLS, SAML, OAuth, OpenID to protect data
during transmission.
 Prevents unauthorized access and protects data paths.

3. Data Storage Security

 Use of secure cloud storage with access restrictions
 Enforcement of backups and version control
 Data integrity checks to prevent tampering

4. Policies & Compliance

 Governance standards from PPT ensure
o proper handling
 o auditing
o monitoring
o policy enforcement

🔷 B. Virtual Machine (VM) Security

Virtual Machine security protects the virtualized infrastructure that runs
cloud services.

1. VM Security Goals (From PPT)

 Prevent unauthorized access
 Ensure isolation between VMs
 Protect against malware
 Monitor VM network activity

2. VM Lifecycle Protection
The PPT mentions VMAN (Virtualization Management Initiative), which
helps:
 Manage VM configurations
 Secure VM deployment
 Standardize VM movement across platforms

3. OVF (Open Virtualization Format)

 PPT highlights OVF as a secure method for distributing VMs.
 Ensures VM integrity, portability, and tamper protection.

4. Hypervisor-Level Security
 VM security relies on:
 Hardening hypervisor
 Applying security patches
 Monitoring privileged operations
 Ensuring no VM can access another VM’s memory or data
(derived from PPT’s virtualization security points)

5. IAM Integration for VM Access

IAM restricts:
 Who can create VMs
 Who can start/stop instances
 Who can modify virtual resources
This reduces privilege-based attacks. Google File System (GFS) –
Features
GFS is a distributed file system developed by Google to store and
process huge data sets across thousands of commodity servers.
1. Designed for Large Distributed Applications
Created to handle web-scale data such as search indexes, logs, and large
multimedia files.
2. Master–Chunkserver Architecture
A single Master Node manages metadata, while Chunkservers store
actual data blocks (called chunks).
3. Very Large File Support
Optimized for files GBs to TBs in size, unlike traditional file systems.
4. Chunk-Based Storage (64 MB chunks)
Files are divided into large, fixed-size chunks stored across multiple
chunkservers, improving throughput.
 5. Replication for Fault Tolerance
Each chunk is usually stored 3 times on different machines, ensuring high
reliability.
6. High Availability & Automatic Recovery
When a chunkserver fails, GFS automatically re-replicates chunks to
maintain availability.
7. Sequential Write Optimization
Optimized for append operations and sequential writes, common in log
processing and big-data workloads.

🔷 Hadoop Distributed File System (HDFS) – Features

HDFS is the open-source implementation inspired by GFS and used in the
Apache Hadoop ecosystem.
1. Master–Slave Architecture
 NameNode → Maintains metadata (file system namespace).
 DataNodes → Store actual data blocks.
2. Fault-Tolerant and Reliable
Blocks are replicated (default 3 copies) across DataNodes to prevent data
loss.
3. Stores Large Files Efficiently
Designed for storing and processing very large datasets across clusters of
commodity hardware.
4. Data Locality Optimization
Computation moves to the location of the data (MapReduce), reducing
data transfer and improving performance.
5. Streaming Data Access Model
HDFS prefers write-once, read-many workload patterns, ideal for big-
data analytics.
 6. Automatic Failure Handling
If a DataNode fails, the NameNode assigns block replication tasks to
healthy nodes.
7. Scalability
HDFS can scale to thousands of nodes and petabytes of data without
performance degradation.
Cloud Data Security Challenges (Data-Specific)
(Use these 10 points)
1. Data Breach – unauthorized access to sensitive data.
2. Data Loss (Backup Failure) – data deleted without recovery due to weak
backup policies.
3. Data Privacy Issues – unauthorized third-party access, especially in
multi-tenant environments.
4. Weak Encryption Practices – unencrypted data becomes easy to steal.
5. Data Integrity Attacks – data is modified or tampered during
transmission or storage.
6. Insecure Data Transmission – lack of TLS/SSL leads to sniffing and man-
in-the-middle attacks.
7. Data Location Uncertainty – data stored across regions raises legal and
control issues.
8. Inadequate Access Control – lack of IAM causes unauthorized data
exposure.
9. Backup & Recovery Challenges – cloud failures create risk of permanent
data loss.
[Link] Data Theft – staff accessing sensitive customer informatio
Hadoop architecture----gfg