Cloud Computing

20S215
Cloud Computing
III B.E-CSE &
III M.TECH
-CSE

2024-2025

B.MATHIVANAN

VI SEM Asso. Prof. / CSE

SREC
 20CS215 – CLOUD COMPUTING
COURSE OUTCOMES:
On successful completion of the course, students will be able to
CO1: Show the progression of cloud computing from virtualization
to containerization. PO6, PO7, PO12
CO2: Understand cloud computing architecture, virtualization and
cloud security. PO6, PO7, PO12
CO3: Construct SLA compliance for cloud computing PO6, PO7,
PO12
CO4: Compare docker and kubernetes for cloud containerization
and workload management. PO6, PO7, PO12
VIRTUAL MACHINES AND VIRTUALIZATION 9

Implementation Levels of Virtualization - Virtualization Structures/Tools and

Mechanisms - Virtualization of CPU, Memory, and I/O Devices - Virtual
Clusters and Resource Management - Virtualization for Data-Center
Automation. Case Study - AWS

4
Virtualization
is the creation of a virtual (rather than actual) version of
something, such as a hardware platform, operating system, a
storage device or network resources

Virtualization is a technique, which allows to share a single

physical instance of a resource or an application among multiple
customers and organizations.

It does by assigning a logical name to a physical storage and

providing a pointer to that physical resource when demanded.

* 5
Virtualization
Virtualization is used to improve IT throughput by using physical
resources as a pool from which virtual resources can be
allocated.

With the help of Virtualization, multiple operating systems and

applications can run on same machine and its same hardware at the
same time, increasing the utilization and flexibility of hardware.

* 6
Virtualization
Concept is not new. Multi Programming – Each Process thinks it
has complete control on all of the resources.
Virtual Memory CPU Sharing
Similarities and Differences
with Multiprogramming
Multi Programming
CPU is shared among processes
Memory is shared using Page Tables.

Process knows it is being managed- uses system calls.

Virtualization
CPU is shared among OSs.
* 7
 The Virtual Server
•A virtual server, also known as a virtual machine (VM), is a
partitioned space inside a real server and is transparent to
users, replicating the functionality of a dedicated physical
server.

* 8
 The Virtual Server Concept
• Virtual servers seek to encapsulate the server software away from
the hardware
• This includes the OS, the applications, and the storage for that server.

• Servers end up as mere files stored on a physical box, or in

enterprise storage.

• One host typically house many virtual servers (virtual machines or

VMs).

• A virtual server can be serviced by one or more hosts e.g. storage,

services, etc

* 9
The Virtual Server Concept

Hypervisor layer between Guest OS and hardware

* 10
The Virtual Server Concept

• Virtual servers can still be referred to by their function i.e.

email server, database server, etc.

• If the environment is built correctly, virtual servers will not be

affected by the loss of a host.

• Hosts may be removed and introduced almost at will to

accommodate maintenance.

* 11
 The Virtual Server Concept
• Virtual servers can be scaled out easily.
• If the administrators find that the resources supporting a virtual server
are being taxed too much, they can adjust the amount of resources
allocated to that virtual server

• Server templates can be created in a virtual environment to be

used to create multiple, identical virtual servers

• Virtual servers themselves can be migrated from host to host

almost at will.

* 12
 The Virtual Server Concept

• Pros • Cons
• Resource pooling • Slightly harder to conceptualize
• Highly redundant • Slightly more costly (must buy
• Highly available hardware, OS, Apps, and now the
• Rapidly deploy new servers abstraction layer)
• Easy to deploy
• Reconfigurable while services
are running
• Optimizes physical resources
by doing more with less

* 13
 Virtualization Architecture
•A Virtual machine (VM) is an isolated runtime
environment (guest OS and applications)
•Multiple virtual systems (VMs) can run on a single
physical system

* 14
Hypervisors and Virtual Machines

Server Server
1 2 Clustering
Guest Guest
OS OS Service
Console
Hypervisor

x86 Architecture
Intercepts
hardware
requests

* 15
•A hypervisor or virtual machine monitor (VMM) is computer
software, firmware or hardware that creates and runs virtual
machines.

•A hypervisor is a piece of computer software, firmware or

hardware that creates and runs virtual machines.

•A computer on which a hypervisor runs one or more virtual

machines is called a host machine, and each virtual machine is
called a guest machine.

16
16
Hypervisor
• Each guest operating system appears to have the host's processor,
memory, and other resources all to itself.

• hypervisor is actually controlling the host processor and resources,

allocating what is needed to each operating system in turn and making
sure that the guest operating systems (called virtual machines) cannot
disrupt each other.

* 17
 Hypervisor:

there are two types of hypervisors.

Type 1 hypervisors, called “bare metal,” run directly on the
host’s hardware.
Type 2 hypervisors, called “hosted,” run as a software layer on an
operating system, like other computer programs.
18
19
20
 Types of Virtualization

•Hardware Virtualization.
•Operating system Virtualization.
•Server Virtualization.
•Storage Virtualization.

* 21
 Hardware Virtualization
•When the virtual machine software or virtual machine
manager (VMM) is directly installed on the hardware system is
known as hardware virtualization.

•The main job of hypervisor is to control and monitoring the

processor, memory and other hardware resources.

•After virtualization of hardware system we can install different

operating system on it and run different applications on those OS.

Usage:
•mainly done for the server platforms, because controlling virtual
machines is much easier than controlling a physical server.

* 22
 Operating System Virtualization
•When the virtual machine software or virtual machine
manager (VMM) is installed on the Host operating system instead of
directly on the hardware system is known as operating system
virtualization.

Usage:
•Operating System Virtualization is mainly used for testing the
applications on different platforms of OS.

* 23
 Server Virtualization
•When the virtual machine software or virtual machine
manager (VMM) is directly installed on the Server system is known
as server virtualization.

Usage:
•Server virtualization is done because a single physical server can be
divided into multiple servers on the demand basis and for balancing
the load.

* 24
 Storage Virtualization
•Storage virtualization is the process of grouping the physical storage
from multiple network storage devices so that it looks like a single
storage device.
•Storage virtualization is also implemented by using software
applications.

Usage:
•Storage virtualization is mainly done for back-up and recovery
purposes.

* 25
 Benefits of Virtualization
• Sharing of resources helps cost reduction
• Isolation: Virtual machines are isolated from each other as if they are
physically separated
• Encapsulation: Virtual machines encapsulate a complete computing
environment
• Hardware Independence: Virtual machines run independently of
underlying hardware
• Portability: Virtual machines can be migrated between different hosts.

* 26
Implementation levels of virtualization

* 27
 ISA
An Instruction Set Architecture (ISA) is part of the abstract model
of a computer that defines how the CPU is controlled by the
software.

The ISA acts as an interface between the hardware and the

software, specifying both what the processor is capable of doing as
well as how it gets done.

* 28
 Implementation levels of virtualization
1) Instruction Set Architecture Level (ISA):

•ISA virtualization can work through ISA emulation.

•At the ISA level, virtualization is performed by emulating a given ISA by

the ISA of the host machine.

•For example, MIPS binary code can run on an x86-based host machine
with the help of ISA emulation.

•With this approach, it is possible to run a large amount of legacy binary

code written for various processors on any given new hardware host
machine. Instruction set emulation leads to virtual ISAs created on any
hardware machine.

* 29
 Implementation levels of virtualization
• A virtual instruction set architecture (V-ISA) thus requires adding a
processor-specific software translation layer to the compiler.

With the help of an emulator, a host

system can run software, programs,
which are designed for the guest
system.

* 30
 Implementation levels of virtualization
2) Hardware Abstraction Level (HAL):

•Hardware-level virtualization is performed right on top of the bare

hardware.

•On the one hand, this approach generates a virtual hardware

environment for a VM.

•On the other hand, the process manages the underlying hardware
through virtualization.

•The idea is to virtualize a computer’s resources, such as its processors,

memory, and I/O devices. The intention is to upgrade the hardware
utilization rate by multiple users concurrently.
* 31
 Implementation levels of virtualization
3) Operating System Level

•At the level of the OS, the virtualization model is capable of creating a
layer that is abstract between the OS and the application.

•This is an isolated container on the OS and the physical server, which uses
the software and hardware. Each of these then functions in the form of a
server.

•When there are several users & no one wants to share the hardware, then
this is where the virtualization level is used. Every user will get his virtual
environment using a dedicated virtual hardware resource. In this way,
there is no question of any conflict

* 32
 Implementation levels of virtualization
4) Library Level:

•The operating system is cumbersome, and this is when the applications

use the API from the libraries at a user level.

•These APIs are documented well, and this is why the library virtualization
level is preferred in these scenarios.

•API hooks make it possible as it controls the link of communication from

the application to the system.

* 33
 Implementation levels of virtualization
5) Application Level:

•The application-level virtualization is used when there is a desire to

virtualize only one application and is the last of the implementation levels
of virtualization in Cloud Computing.

•One does not need to virtualize the entire environment of the platform.

•This is generally used when you run virtual machines that use high-level
languages. The application will sit above the virtualization layer, which in
turn sits on the application program.

•It lets the high-level language programs compiled to be used at the

application level of the virtual machine run seamless
* 34
 VIRTUALIZATION STRUCTURES / TOOLS AND
MECHANISMS
• Depending on the position of the virtualization layer, there are several classes of
VM architectures, namely the hypervisor architecture, para-virtualization, and
host-based virtualization.

• Hypervisor Architecture

• The hypervisor supports hardware-level virtualization on bare metal devices like

CPU, memory, disk and network interfaces.

• The hypervisor software sits directly between the physical hardware and its OS.
This virtualization layer is referred to as either the VMM or the hypervisor.

• The hypervisor provides hyper calls for the guest OSes and applications.

* 35
 VIRTUALIZATION STRUCTURES / TOOLS AND
MECHANISMS
• Depending on the functionality, a hypervisor can assume a micro-kernel
architecture like the Microsoft Hyper-V. Or it can assume a monolithic hypervisor
architecture like the VMware ESX for server virtualization.

• A micro-kernel hypervisor includes only the basic and unchanging functions

(such as physical memory management and processor scheduling). The device
drivers and other changeable components are outside the hypervisor.

• A monolithic hypervisor implements all the aforementioned functions, including

those of the device drivers. Therefore, the size of the hypervisor code of a
micro-kernel hypervisor is smaller than that of a monolithic hypervisor.

* 36
 VIRTUALIZATION STRUCTURES / TOOLS AND
MECHANISMS
• Depending on the functionality, a hypervisor can assume a micro-kernel
architecture like the Microsoft Hyper-V. Or it can assume a monolithic hypervisor
architecture like the VMware ESX for server virtualization.

• A micro-kernel hypervisor includes only the basic and unchanging functions

(such as physical memory management and processor scheduling). The device
drivers and other changeable components are outside the hypervisor.

• A monolithic hypervisor implements all the aforementioned functions, including

those of the device drivers. Therefore, the size of the hypervisor code of a
micro-kernel hypervisor is smaller than that of a monolithic hypervisor.

* 37
 Xen
• Xen is a type-1 hypervisor is a type-1 hypervisor, providing services that
allow multiple computer operating systems is a type-1 hypervisor, providing
services that allow multiple computer operating systems to execute on the
same computer hardware concurrently.

• It was originally developed by the University of Cambridge Computer

LaboratoryIt was originally developed by the University of Cambridge
Computer Laboratory and is now being developed by the Linux
FoundationIt was originally developed by the University of Cambridge
Computer Laboratory and is now being developed by the Linux
Foundation with support from Intel.
* C-C-S-S 38
Xen - overview
• Xen Project creates a Virtual Machine Monitor (VMM) also known as a
hypervisor: a software system that allows the execution of multiple virtual
guest operating systems simultaneously on a single physical machine.

• In particular, the project creates a Type 1 or “bare-metal” hypervisor,

meaning that it runs directly on top of the physical machine.

• Guest virtual machines running on a Xen Project Hypervisor are known as

“domains”.

• A special domain known as domain0 (or dom0) is responsible for controlling

the hypervisor and starting other guest operating systems.

* C-C-S-S 39
Xen - overview
• other guest operating systems are called domUs. This is because these
domains are “unprivileged” in the sense they cannot control the hypervisor or
start/stop other domains.

• hypervisor supports two primary types of virtualization: para-virtualization

(PV) and hardware virtualized machine (HVM) also known as “full
virtualization”.

• Para-virtualization uses modified guest operating systems that we refer to as

"enlightened" guests.

• they make special calls to the hypervisor that allow them to access CPUs,
storage and network resources.

* C-C-S-S 40
Xen - overview
• In contrast, HVM guests need not be modified, as the hypervisor will create a
fully virtual set of hardware devices for the machine resembling a physical
x86 computer.

• This emulation requires more overhead than the para-virtualization approach

but allows unmodified guest operating systems like Microsoft Windows to run
on top of the hypervisor.

• HVMs are supported through virtualization extensions in the CPU.

* C-C-S-S 41
Xen - overview
• The technology is now prevalent; all recent servers, many desktops and
some mobile systems should be equipped with at least some extensions.

• Xen virtualization is now seen as on a spectrum, with PV at one end and

HVM at the other.

• In between are various enhancements to improve performance:

• HVM with PV drivers, PVHVM or “Para-virtualization on HVM”, and most

recently PVH.

• Each strives to provide the best of both worlds by reducing expensive

emulation.

* C-C-S-S 42
Xen - Basic Components
• basic components of a Xen-based virtualization environment are the Xen
hypervisor, the Domain0, any number of other VM Guests, and the
tools, commands, and configuration files that let you manage
virtualization.

• Collectively, the physical computer running all these components is referred

to as a VM Host Server because together these components form a platform
for hosting virtual machines.

• The Xen Hypervisor: sometimes referred to a virtual machine monitor, is

an open-source software program that coordinates the low-level interaction
between virtual machines and physical hardware.
* C-C-S-S 43
Xen - Basic Components
• The Domain0: The virtual machine host environment, also referred to
as Domain0 or controlling domain, is comprised of several components, such
as:

• The SUSE Linux operating system, which gives the administrator a

graphical and command line environment to manage the virtual machine host
components and its virtual machines.

• The Xend daemon (xend), which stores configuration information about each
virtual machine and controls how virtual machines are created and managed.

* C-C-S-S 44
Xen - Basic Components
• A modified version of QEMU, which is an open-source software program that
emulates a full computer system, including a processor and various
peripherals.

• It provides the ability to host operating systems in full virtualization mode.

QEMU is primarily a Type-2 hypervisor.

It runs on top of a host operating system and provides
virtualization capabilities for various guest operating systems and
architectures.
However, it can also be used in combination with KVM
(Kernel-based Virtual Machine) to function as a Type-1
hypervisor.
* C-C-S-S 45
Xen - Basic Components
• Xen-Based Virtual Machines: also referred to as a VM
Guest or DomU consists of the following components:

• At least one virtual disk that contains a bootable operating system. The
virtual disk can be based on a file, partition, volume, or other type of block
device.

• Virtual machine configuration information, which can be modified by

exporting a text-based configuration file from Xend or through VMM.

• A number of network devices, connected to the virtual network provided by

the controlling domain.

* C-C-S-S 46
Xen - Basic Components
• Management Tools, Commands, and Configuration Files:

• There is a combination of GUI tools, commands, and configuration files to

help you manage and customize your virtualization environment.

* C-C-S-S 47
Xen - architecture

* C-C-S-S 48
 Xen - architecture
•graphic depicts a virtual machine host with four virtual machines.

•The Xen hypervisor is shown as running directly on the physical

hardware platform.

•Note, that the controlling domain is also just a virtual machine,

although it has several additional management tasks compared
to all other virtual machines.

* C-C-S-S 49
 Xen - architecture
•On the left, the virtual machine host’s Domain0 is shown running
the SUSE Linux operating system.

•The two virtual machines shown in the middle are running

paravirtualized operating systems.

•The virtual machine on the right shows a fully virtual machine

running an unmodified operating system, such as Windows
Server 2003 or Windows XP.

* C-C-S-S 50
* C-C-S-S 51
• A Xen based system is handled by Xen hypervisor, which is executed in the
most privileged mode and maintains the access of guest operating system to
the basic hardware.

• Guest operating system are run between domains, which represents virtual
machine instances

• In addition, particular control software, which has privileged access to the

host and handles all other guest OS, runs in a special domain called Domain
0.

• This the only one loaded once the virtual machine manager has fully booted,
and hosts an HTTP server that delivers requests for virtual machine creation,
configuration, and termination.

•* C-C-S-S 52
• This component establishes the primary version of a shared virtual machine
manager (VMM), which is a necessary part of Cloud computing system
delivering Infrastructure-as-a-Service (IaaS) solution.

• Various x86 implementation support four distinct security levels, termed as

rings, i.e., Ring 0, Ring 1, Ring 2, & Ring 3

• Ring 0 represents the level having most privilege and Ring 3 represents the
level having least privilege.

• Almost all the frequently used Operating system, except for OS/2, uses only
two levels i.e. Ring 0 for the Kernel code and Ring 3 for user application and
non-privilege OS program.

* C-C-S-S 53
•Due to the structure of x86 instruction set, some instructions allow
code execution in Ring 3 to switch to Ring 0 (Kernel mode).

•Such an operation is done at hardware level, and hence between a

virtualized environment, it will lead to a TRAP or a silent fault, thus
preventing the general operation of the guest OS as it is now running in
Ring 1.

* C-C-S-S 54
Pros:

• a) Xen server is developed over open-source Xen hypervisor and it uses a

combination of hardware-based virtualization and paravirtualization. This
tightly coupled collaboration between the operating system and virtualized
platform enables the system to develop lighter and flexible hypervisor that
delivers their functionalities in an optimized manner.

• b) Xen supports balancing of large workload efficiently that capture CPU,

Memory, disk input-output and network input-output of data. It offers two
modes to handle this workload: Performance enhancement, and For handling
data density.

* C-C-S-S 55
Pros:

• c) It also comes equipped with a special storage feature that we call Citrix
storage link. Which allows a system administrator to uses the features of
arrays from Giant companies- Hp, Netapp, Dell Equal logic etc.

• d) It also supports multiple processor, Iive migration one machine to another,

physical server to virtual machine or virtual server to virtual machine
conversion tools, centralized multiserver management, real time performance
monitoring over window and linux.

* C-C-S-S 56
Cons:

• a) Xen is more reliable over linux rather than on window.

• b) Xen relies on 3rd-party component to manage the resources like drivers,

storage, backup, recovery & fault tolerance.

• c) Xen deployment could be a burden some on your Linux kernal system as

time passes.

• d) Xen sometimes may cause increase in load on your resources by high

input-output rate and may cause starvation of other VMs.

* C-C-S-S 57
 Hyper – v
•Hyper-V is Microsoft software that virtualizes a single hardware server
into multiple virtual servers/machines.

•Hyper-V lets you share the underlying hardware resources (processor,

hard drive, memory, etc.) across virtual machines (VMs) by assigning
them virtual resources.

• Hyper-V consists of various parts that work together: Windows

hypervisor, Hyper-V Virtual Machine Management Service, the virtualization
Windows Management Instrumentation (WMI) provider, the virtual machine bus
(VMbus), virtualization service provider (VSP) and virtual infrastructure driver
(VID).

• * C-C-S-S 58
 Hyper – v
Hyper-V can help you:

• Establish or expand a private cloud environment. Provide more flexible,

on-demand IT services by moving to or expanding your use of shared resources
and adjust utilization as demand changes.

• Use your hardware more effectively. Consolidate servers and workloads onto
fewer, more powerful physical computers to use less power and physical space.

• Improve business continuity. Minimize the impact of both scheduled and

unscheduled downtime of your workloads.

* C-C-S-S 59
 Hyper – v
Hyper-V can help you:

• Establish or expand a virtual desktop infrastructure (VDI). Use a centralized

desktop strategy with VDI can help you increase business agility and data
security, as well as simplify regulatory compliance and manage desktop
operating systems and applications. Deploy Hyper-V and Remote Desktop
Virtualization Host (RD Virtualization Host) on the same server to make
personal virtual desktops or virtual desktop pools available to your users.

• Make development and test more efficient. Reproduce different computing

environments without having to buy or maintain all the hardware you'd need if
you only used physical systems.

•
* C-C-S-S 60
Hyper – v

* C-C-S-S 61
• Hyper-V is a hypervisor-based virtualization technology for certain x64
versions of Windows. It is the processor-specific virtualization platform that
allows multiple isolated operating systems to share a single hardware
platform.

• Hyper-V supports isolation in terms of a partition. A partition is a logical unit of

isolation, supported by the hypervisor, in which operating systems execute.

• The Microsoft hypervisor must have at least one parent, or root, partition,
running Windows. The virtualization management stack runs in the parent
partition and has direct access to hardware devices.

* C-C-S-S 62
• The root partition then creates the child partitions which host the guest
operating systems. A root partition creates child partitions using the hypercall
application programming interface (API).

• Partitions do not have access to the physical processor, they have a virtual
view of the processor and run in a virtual memory address region that is
private to each guest partition.

• The hypervisor handles the interrupts to the processor, and redirects them to
the respective partition.

* C-C-S-S 63
• Hyper-V can also hardware accelerate the address translation between
various guest virtual address spaces by using an Input Output Memory
Management Unit (IOMMU) which operates independent of the memory
management hardware used by the CPU.

• An IOMMU is used to remap physical memory addresses to the addresses

that are used by the child partitions.

• Child partitions also do not have direct access to other hardware resources
and are presented a virtual view of the resources, as virtual devices (VDevs).

* C-C-S-S 64
• Requests to the virtual devices are redirected either via the VMBus or the
hypervisor to the devices in the parent partition, which handles the requests.

• The VMBus is a logical inter-partition communication channel. The parent

partition hosts Virtualization Service Providers (VSPs) which communicate
over the VMBus to handle device access requests from child partitions.

• Child partitions host Virtualization Service Consumers (VSCs) which redirect

device requests to VSPs in the parent partition via the VMBus.

• This entire process is transparent to the guest operating system.

* C-C-S-S 65
• Virtual Devices can also take advantage of a Windows Server Virtualization
feature, named Enlightened I/O, for storage, networking, graphics, and input
subsystems.

• Enlightened I/O is a specialized virtualization-aware implementation of high

level communication protocols (such as SCSI) that utilize the VMBus directly,
bypassing any device emulation layer.

• This makes the communication more efficient but requires an enlightened

guest that is hypervisor and VMBus aware. Hyper-V enlightened I/O and a
hypervisor aware kernel is provided via installation of Hyper-V integration
services..

* C-C-S-S 66
• Integration components, which include virtual server client (VSC) drivers, are
also available for other client operating systems.

• Hyper-V requires a processor that includes hardware assisted virtualization,

such as is provided with Intel VT or AMD Virtualization (AMD-V) technology.

* C-C-S-S 67
Hyper-V offers many features :

• Computing environment - A Hyper-V virtual machine includes the same

basic parts as a physical computer, such as memory, processor, storage, and
networking. All these parts have features and options that you can configure
different ways to meet different needs. Storage and networking can each be
considered categories of their own, because of the many ways you can
configure them.

• Disaster recovery and backup - For disaster recovery, Hyper-V Replica

creates copies of virtual machines, intended to be stored in another physical
location, so you can restore the virtual machine from the copy.

* C-C-S-S 68
Hyper-V offers many features :

• For backup, Hyper-V offers two types. One uses saved states and the other
uses Volume Shadow Copy Service (VSS) so you can make
application-consistent backups for programs that support VSS.

• Optimization - Each supported guest operating system has a customized set

of services and drivers, called integration services, that make it easier to use
the operating system in a Hyper-V virtual machine.

• Portability - Features such as live migration, storage migration, and

import/export make it easier to move or distribute a virtual machine.

* C-C-S-S 69
Hyper-V offers many features :

• Remote connectivity - Hyper-V includes Virtual Machine Connection, a

remote connection tool for use with both Windows and Linux. Unlike Remote
Desktop, this tool gives you console access, so you can see what's
happening in the guest even when the operating system isn't booted yet.

• Security - Secure boot and shielded virtual machines help protect against
malware and other unauthorized access to a virtual machine and its data.

* C-C-S-S 70
High-level overview of the architecture of a
Hyper-V environment.

* C-C-S-S 71
 Host-Based / Full Virtualization with Binary Translation
• virtualization layer on top of the host OS. This host OS is still responsible for
managing the hardware.

• The guest OS are installed and run on top of the virtualization layer. Dedicated
applications may run on the VMs.

• Binary translation is one specific approach to implementing full

virtualization.

• It involves examining the executable code of the virtual guest for “unsafe”
instructions, translating these into “safe” equivalents, and then executing the
translated code.

• An unsafe instruction is one that for example tries to access or modify the
memory of another guest.
* C-C-S-S 72
Host-Based / Full Virtualization with Binary Translation

* C-C-S-S 73
 Host-Based / Full Virtualization with Binary Translation
• Trap & Emulate:

• Emulate : Executable code from the guest is allowed to execute directly on the
host CPU by the hypervisor

• A Trap is an exceptional condition that transfers control Binary translation back

to the hypervisor.

• Once the hypervisor has received a trap, it will inspect the offending instruction,
Emulate it in a safe way, and continue execution the instruction

• Direct Execution: With direct execution, most code is executed directly on the
CPU, and only the code that needs to be translated is actually translated.

* C-C-S-S 74
 Host-Based / Full Virtualization with Binary Translation
• Full Virtualization provides complete simulation of the underlying hardware

• Simulate all computing element such as instruction set, main memory, interrupts ,
exceptions, and device access.

• The result is a os stems in which all software including all OS’s capable of
execution on the raw hardware can be run in the virtual machine.

• The combination of binary translation and direct execution provides Full

Virtualization as the guest OS is fully abstracted (completely decoupled) from the
underlying hardware by the virtualization layer.

• The guest OS is not aware it is being and requires no modification.

* C-C-S-S 75
Host-Based / Full Virtualization with Binary Translation

* C-C-S-S 76
Host-Based / Full Virtualization with Binary Translation

* C-C-S-S 77
 Para Virtualization
• To overcome the problem of degraded performance, Guest OS kernel is
modified.

• Para-virtualization is assisted with intelligent compiler to replace non-virtualiable

instructions with hyper calls that communicate directly with the virtualization
layer or hypervisor .

• Para-virtualization is different from full virtualization where the unmodified OS

does not know it is virtualized and sensitive OS calls are trapped using binary
translation.

• Para-Virtualization is done at Compile time.

• Example: – KVM (Kernel-based Virtual Machine) and VMware ESX

* C-C-S-S 78
 Para Virtualization

* C-C-S-S 79
 Para Virtualization

* C-C-S-S 80
 Para Virtualization

* C-C-S-S 81
* 82
* 83
* 84