Virtualization

What is virtualization?
 Virtualization is a technology that allows you to create multiple
simulated environments or dedicated resources from a single
physical hardware system.
 Types of Virtualization
1. Server Virtualization: Consolidates multiple physical servers into virtual servers on a single
physical server, improving resource utilization and reducing costs ..
2. CPU virtualization:CPU virtualization focuses on creating virtual CPUs (vCPUs) that allow
multiple virtual machines (VMs) to share the physical CPU resources of a host machine. The
hypervisor allocates time slots on the physical CPU cores to the vCPUs. This allows multiple
VMs to run concurrently on a single physical CPU by sharing its processing power.
3. Storage Virtualization: Pools physical storage from multiple devices into a single virtual
storage unit, simplifying management and improving efficiency ..
4. Network Virtualization
: Combines network resources to create a single, software-based network, enhancing flexibility
and scalability
.
5. Desktop Virtualization
: Allows users to run desktop environments on a central server, providi
ng remote access and centralized managemen
 Virtualization describes a technology in which an application, guest operating system
or data storage is abstracted away from the true underlying hardware or software.
Comparison: Emulation vs Simulation vs Virtualization
Feature Emulation Simulation Virtualization

Definition Mimics hardware/software behavior Models the behavior of a system to Creates virtual versions of physical
of one system on another. study its performance. resources.

Purpose To run software designed for one To analyze or predict system To optimize and manage computing
platform on another. behavior. resources.

Accuracy High fidelity to original system. May simplify or approximate real Operates close to real hardware
behavior. performance.

Performance Often slower due to full system Depends on model complexity. Near-native performance.
replication.

Use Cases Running legacy software, game Testing network protocols, training Cloud computing, server
consoles. AI models. consolidation.

Hardware Dependency Independent of original hardware. Not tied to hardware; abstract model. Requires physical hardware but
abstracts it.

Examples QEMU, DOSBox NS2, MATLAB Simulink VMware, VirtualBox, Hyper-V

Compute Virtualization
 It is a technique of masking / abstracting the physical compute
hardware
 Enables multiple operating systems to run concurrently on a
single or clustered physical machine(s)
 Enables creation of multiple virtual machines, each running an
OS and application.
 VM is a logical entity that looks and behaves like physical machine

 Virtualization layer resides between hardware and VMs

 Also known as hypervisor/Virtual Machine Monitor
Need for Compute Virtualization

 Before Virtualization
 Runs single operating system per machine at a time
 Couples s/w and h/w tightly
 May create conflicts when multiple applications run on the same machine
 Underutilizes resources
 Inflexible and expensive
Need for Compute Virtualization

 After Virtualization
 Runs multiple operating systems per machine concurrently
 Makes operating system and application h/w independent
 Isolates VM from each other, hence no conflict
 Improves resource utilization
 Offers flexible infrastructure at low cost
Virtual Machine
 A virtual machine (VM) is a separate and independent software instance
that includes a full copy of an operating system and application software.

 A physical server prepared with a server virtualization hypervisor such

as Microsoft Hyper-V, VMware vSphere or Citrix XenServer can host
multiple VMs while maintaining logical isolation between each machine.

 Each instance can then share the server's computing resources --

dramatically increasing physical server hardware usage.
 Hypervisor
 A hypervisor, also called a Virtual Machine Monitor, is a program that
allows multiple operating systems to share a single hardware host.

 A tool that exposes hardware resources to support the operation of

multiple Virtual Machines (VMs), which are operating system instances
that are designed to share resources such as CPU cores, RAM, network
interface cards (NICs) and storage.
 Two key components:
 Kernel: provide same functionality as other OS like process creation, file s/m
mgmt., process scheduling etc.
 VMM
Hypervisor

 Virtual Machine Monitor (VMM) - is responsible for actually executing

commands on the CPUs and performing Binary Translation (BT)

 A VMM abstracts hardware to appear as a physical machine with its own

CPU, memory and I/O devices

 Each virtual machine is assigned a VMM that has a share of the CPU,
memory and I/O devices to successfully run the virtual machine

 When a virtual machine starts running, the control is transferred to the

VMM, which subsequently begins executing instructions from the virtual
machine
Types of Hypervisor

Type 1 (bare-metal) Type 2 (hosted)

VM1 VM2 Guest

Guest VM1 VM2 App Hypervisor

Hypervisor OS Host

Host
Hardware Hardware

VMware Workstation, Microsoft Virtual PC, Sun

VMware ESX, Microsoft Hyper-V, Xen
VirtualBox, QEMU, KVM
Hybrid
Bare Metal

 A bare-metal virtualization hypervisor does not require

admins to install a server operating system first.

 Bare-metal virtualization means the hypervisor has direct

access to hardware resources, which results in better
performance, scalability and stability.

 Bare-metal virtualization is well suited for enterprise data

centers, because it usually comes with advanced features for
resource management, high availability and security.
 The most popular bare-metal virtualization hypervisors are:
 VMware ESX and ESXi
 Microsoft Hyper-V
 Citrix Systems XenServer:- open source project
Hosted
 A hosted hypervisor requires you to first install an OS

 A hosted virtualization hypervisor does not have direct access to

hardware and must go through the OS, which increases resource
overhead and can degrade virtual machine (VM) performance

 Hosted hypervisors are common for desktops, because they allow

you to run multiple OSs

 These virtualization hypervisor types are also popular for

developers, to maintain application compatibility on modern OSs
 The most popular hosted virtualization hypervisors are:
 VMware Workstation, Server, Player and Fusion
 Oracle VM VirtualBox
 Microsoft Virtual PC
 Parallels Desktop
Benefits of Compute Virtualization

 Server consolidation:
 Server consolidation is the process of combining multiple underutilized servers into fewer,
more powerful ones. This is typically achieved through virtualization, which allows multiple
virtual machines (VMs) to run on a single physical server.
 Isolation
 Hardware independence
 Reduced cost
In a normal machine
Trap and emulate

 Whenever the guest operating system tries to perform one of

these privileged operations, the processor will "trap" the
instruction and hand over control to the host operating system or
hypervisor, so that it can do the required operation and then
return control back to the guest.
 But most real-world instruction sets, including x86,
were not designed with virtualization in mind. As a
result, there are privileged instructions that do not have
any corresponding trap facility. Such instructions are
called sensitive instructions or critical instructions.
 Example: Pagetable modifying instructions
X86 Architecture
Problems

 Sensitive or critical instructions presence and they were not subset of Privileged
instructions.(Popek Goldberg Theorem)
 Deprivileging OS: Os needs to be run in higher Ring number than 0
Privileged Instructions
Instructions that can only be executed in kernel mode (or supervisor mode).
They control critical system functions like memory management, I/O operations,
and interrupt handling.
•Examples:
• Modifying page tables
• Accessing hardware devices
• Changing processor modes
If executed in user mode, they trigger a trap or exception.

Sensitive Instructions
Instructions that reveal or affect the system state, especially related to resource [Link]
may not be privileged but can still impact virtualization or system integrity.
Examples:
• Reading the current processor mode
• Accessing system configuration registers
May or may not cause a trap in user mode, but are critical for virtualization because they can
expose the underlying hardware state.
 Full Virtualization using Binary Translation
 Translates kernel code to replace non-virtualizable instructions with
new sequences of instructions that have the intended effect on the
virtual hardware.

 User level code is directly executed on the processor for high

performance virtualization.

 The guest OS is not aware it is being

Virtualized and requires no
modification.
 Full virtualization offers the best
isolation,migratability,portability and security for virtual machines.
Binary Translation

 Intercepting Problematic Instructions:

 The virtual machine monitor (VMM), also called the hypervisor, scans the guest OS code for
instructions that cannot be safely executed directly on the hardware.
 Translating Instructions:
 These problematic instructions are replaced with safe, equivalent sequences that simulate the
intended behavior without compromising isolation or control.
 Caching Translated Code:
 The translated code is cached so that future executions are faster, avoiding repeated
translation.
OS Assisted Virtualization or Para-virtualization
 Modifying the OS kernel to replace non-virtualizable
instructions with hypercalls that communicate directly with the
virtualization layer.

 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.

 The performance advantage of para-virtualization over full

virtualization can vary greatly depending on the workload.
HyperCall

 How Hypercalls Work:

 The guest OS replaces certain privileged instructions (which would normally require
direct hardware access) with hypercalls.
 These hypercalls are like system calls, but instead of calling the kernel, they call
the hypervisor.
 The hypervisor then safely executes the requested operation on behalf of the guest.
Hardware Assisted Virtualization

 Hardware vendors include Intel Virtualization Technology (VT-x) and AMD’s AMD-V
which both target privileged instructions with a new CPU execution mode feature that
allows the VMM to run in a new root mode below ring 0.
 As depicted in Figure 7, privileged and sensitive calls are set to automatically trap to
the hypervisor, removing the need for either binary translation or paravirtualization.
 guest state is stored in Virtual Machine Control Structures (VT-x) or Virtual Machine
Control Blocks (AMD-V).
Virtual Machine

 From a user’s perspective, a logical compute system

 Runs an OS and application like physical machine
 Contains virtual components such as CPU, RAM, disk and NIC

 From a hypervisor’s perspective

 VM is a discrete set of files such as configuration file, virtual disk files, virtual BIOS file,
VM swap file and log file
 VM operations
 Multiplexing
 Migration
 Suspension
 Provision
Resource Pool

 It is a logical abstraction of aggregation physical

resources that are managed centrally
 Created from a physical machine or cluster
 Administratorsmay create child resource pool or virtual
machine from the parent resource pool
 Reservation, Limit and Share are used to control the
resources consumed by resource pools or VMs
Resource Management
 A process of allocating resources from physical machine
or clustered physical machines to virtual machines to
optimize the utilization of resources.
 Resource management includes management of CPU,
memory, network and storage.
 Goals of resource management
 Controls utilization of resources
 Prevents VMs from monopolizing resources
 Allocates resources based on relative priority of VMs
 Resources must be pooled to manage them centrally
Share, Limit and Reservation

 Parameters that control the resources consumed by a

child resource pool or a VM are as follows
 Share – Amount of CPU or memory resources a VM or a child
resource pool can have with respect to its parent’s total
resources
 Limit – Maximum amount of CPU and memory a VM or a
child resource pool can consume (max)
 Reservation – Amount of CPU and memory reserved for a
VM or a child resource pool (min)
CPU virtualization

 CPU virtualization is a technique that allows a single physical CPU to be shared

among multiple virtual machines (VMs) by creating virtual CPUs (vCPUs). It is
managed by a software layer called a hypervisor.
Multicore Processors
 Advantage to Hypervisor that performs multitasking of
virtual machines
 Hypervisor running on a physical machine can have
single core, dual core or quad core CPUs
 Hypervisor scheduler optimizes the placement of CPUs
onto different sockets
Optimizing CPU Resource utilization

 Modern CPUs are equipped with multiple cores and

hyper-threading
 Multi-core processors have multiple processing units (cores) in
a single CPU
 Hyper-threading makes a physical CPU appear as two or more
logical CPUs
 Allocating a CPU resource efficiently and fairly is critical
 Hypervisor schedules virtual CPUs on the physical CPUs
CPU Optimization in Virtual Env
 Hypervisor support following features to optimize CPU resources:
 1. vCPU Scheduling
Maps virtual CPUs (vCPUs) to physical CPUs (pCPUs).
 Uses intelligent scheduling algorithms to balance load and reduce contention.
 2. CPU Overcommitment
 Allows more vCPUs than physical cores.
 Optimizes resource usage when VMs are not fully utilizing their assigned CPUs.
 3. CPU Affinity / Pinning
 Binds specific vCPUs to specific physical cores.
 Reduces context switching and improves cache performance.
 4. NUMA Awareness
 Optimizes memory access based on CPU socket locality.
 Ensures VMs are scheduled on cores closest to their memory.
5. Dynamic Resource Allocation
•Adjusts CPU resources based on workload demand.
•Supports features like hot-add vCPU and dynamic scaling.
6. CPU Throttling / Limits
•Restricts CPU usage for specific VMs to prevent resource hogging.
•Useful in multi-tenant environments.
7. CPU Reservations and Shares
•Reservations guarantee minimum CPU resources.
•Shares define relative priority when resources are contested.
8. Performance Monitoring and Feedback
•Tracks metrics like CPU usage, ready time, co-stop.
•Uses feedback to adjust scheduling and resource allocation.
9. Idle CPU Consolidation
•Powers down unused cores or consolidates workloads to save energy.
•A reservation guarantees a minimum amount of CPU (in MHz or GHz) to a VM.
•Even if the host is overloaded, the VM will get at least its reserved CPU.
Shares define the relative priority of a VM when CPU resources are contested.
They don’t guarantee CPU, but influence how much a VM gets compared to others.
VM1 has 2000 shares, VM2 has 1000 shares.
If both are competing for CPU, VM1 gets twice as much CPU time as VM2.
Calculating available Host CPU Resources
The number of physical cores (pCPU) available on a host is calculated as:

(# Processor Sockets) X (# Cores/Processor) = # Physical Processors (pCPU)

If the cores use hyperthreading, the number of logical cores is calculated as:

(# pCPU) X (2 threads/physical processor) = # Virtual Processors (vCPU)

For example, if you have 2 processors with 6 cores each:

(2 Processor Sockets) X (6 Cores/Processor) = 12 Physical Processors (pCPU)

(12 pCPU) X (2 threads/physical processor) = 24 Virtual Processors (vCPU)
Optimizing Memory Resource
 Hypervisor manages a machine’s physical memory
 Part of this memory is used by the hypervisor
 Rest is available for VMs
 VMs can be configured with more memory than physically
available, called ‘memory overcommitment’
 Memory optimization is done to allow overcommitment
In a virtualized environment, memory reclamation is
a set of techniques used by the hypervisor to recover
unused memory from virtual machines (VMs)
and redistribute it to others that need it. This is
essential for efficient memory utilization, especially
when memory overcommitment is used (i.e., allocating
more virtual memory than physically available).
Hypervisor supports 4 techniques to reclaim
memory:
1. Transparent page sharing
2. Memory ballooning
3. Memory compression
4. Memory swapping
[Link] page sharing

 Let's say, there are 30 copies of the same memory segment among different VMs with
the same OS. ESXi keeps just one and the rest are just pointers.
 It is the vmkernel who automatically identifies identical pages of virtual memory and
consolidates them to a single page in physical memory. As a result, the total virtual
machine host memory consumption is lowered and we can allocate more memory to
our VMs (to overcommit even more). TPS works in the background, from time to time.
1. Transparent Page Sharing

 Hypervisor detects identical memory pages of virtual machines and maps them to
same physical page
 Read-only when started
 For writes, hypervisor treats the shared pages as copy-on-write
 Attempts to write on shared page
 Generates minor page fault
 Creates private copy after write and remaps the memory
Memory ballooning

 Memory ballooning is a computer memory reclamation

technique used by a hypervisor to allow the physical
host system to retrieve unused memory from certain
guest virtual machines (VMs) and share it with others.
Memory Ballooning
 No memory shortage, balloon remains deflated

i)Memory shortage, balloon inflates

ii)Driver demands memory from guest OS
iii)Guest OS forces page out
iv)Hypervisor reclaims memory

i)Memory shortage resolved, deflates balloon

ii)Driver relinquishes memory
iii)Guest OS can use pages
iv)Hypervisor grants memory
Memory compression
 Memory compression moves memory pages to a separate
cache which is located in the host’s main memory. ESXi
determines if a page can be compressed by checking the
compression ratio for the page. Memory compression occurs
when the page’s compression ratio is greater than 50%.
Otherwise, memory compression has no added value and the
page is swapped out. Only pages that would otherwise be
swapped out to disk are chosen as candidates for memory
compression.
 Memory compression only occurs when there’s a host memory
shortage and ballooning has not achieved the desired effect.
ESXi will not proactively compress memory pages when host
memory is undercommitted.
 Memory compression is somewhat comparable to swapping
but instead of moving memory pages to disk, memory page
are moved to a reserved memory location. Because memory
access times are much faster than disk access times, memory
Memory compression
Memory Swapping
 When transparent page sharing, ballooning and memory
compression do not have the desired effect, ESXi uses it’s last
resort, hypervisor swapping. Hypervisor swapping moves the
a guest’s memory pages to a virtual machine based swap file
(.vswp), which frees host physical memory for other virtual
machines.
 Both page sharing and ballooning take time to reclaim
memory. The page-sharing speed depends on the page scan
rate and the sharing opportunity. Ballooning speed relies on
the guest operating system’s response time for memory
allocation. Hypervisor swapping is a guaranteed technique to
reclaim a specific amount of memory within a specific amount
of time. However, hypervisor swapping is used as a last resort
to reclaim memory from the virtual machine because it has a
huge performance impact.
 3. Memory Swapping

 Each powered-on VM needs its own swap file

 Created when the VM is powered-on
 Deleted when the VM is powered-off
 Swap file size is equal to the difference between the
memory limit and the VM memory reservation
 Hypervisor swaps out the VM’s memory content if
memory is scarce
 Swapping is the last option because it causes notable
performance impact
 Host free memory states
ESXi maintains four host free memory states: high,
soft, hard, and low, which are reflected by four
thresholds. The threshold values are calculated
based on host memory size. The ‘minfree‘ value
represents the threshold for the high state. By
default, ESXi enables page sharing since it
opportunistically reclaims host memory with little
overhead. When to use ballooning or swapping
(which activates memory compression) to reclaim
host memory is largely determined by the current
host free memory state.
 In the high state, the aggregate virtual machine guest memory usage
is smaller than the host memory size. Whether or not host memory is
overcommitted, the hypervisor will not reclaim memory through
ballooning or swapping unless the virtual machine memory limit is set.

If host free memory drops towards the soft threshold, the hypervisor
starts to reclaim memory using ballooning. Ballooning happens before
free memory actually reaches the soft threshold because it takes time
for the balloon driver to allocate and pin guest physical memory.
Usually, the balloon driver is able to reclaim memory in a timely
fashion so that the host free memory stays above the soft threshold.

If ballooning is not sufficient to reclaim memory or the host free
memory drops towards the hard threshold, the hypervisor starts to use
swapping in addition to using ballooning. During swapping, memory
compression is activated as well. With host swapping and memory
compression, the hypervisor should be able to quickly reclaim memory
and bring the host memory state back to the soft state.
 In a rare case where host free memory drops below the
low threshold, the hypervisor continues to reclaim
memory through swapping and memory compression,
and additionally blocks the execution of all virtual
machines that consume more memory than their target
memory allocations.
 In certain scenarios, host memory reclamation happens
regardless of the current host free memory state. For
example, even if host free memory is in the high state,
memory reclamation is still mandatory when a virtual
machine’s memory usage exceeds its specified memory
limit. If this happens, the hypervisor will employ
ballooning and, if necessary, swapping and memory
compression to reclaim memory from the virtual machine
until the virtual machine’s host memory usage falls back
to its specified limit.
Sliding Scale Calculation for [Link]

 VMware ESXi uses a sliding scale to determine the minimum amount of free memory
(minFree) that must be available before memory reclamation techniques (like
ballooning, compression, and swapping) are triggered. Host memory=128GB

Memory Range Percentage Calculation Example

0 – 4 GB 6% 6% of 4096 MB = 245.76
MB
4 – 12 GB (next 8 GB) 4% 4% of 8192 MB = 327.68
MB
12 – 28 GB (next 16 GB) 2% 2% of 16384 MB = 327.68
MB
Remaining (>28 GB) 1% 1% of (131072 - 28672 MB)
= 1024 MB
This is better understood with an example. Let us take an example of ESXi host
with 100 GB Memory to understand sliding scale calculation
of [Link].
•For the first 4 GB of memory we will set aside 6% of it which is equal to 245
MB.
•For next 8 GB from 4-12 GB range, we will set aside 4% of it which is equal
to 327 MB.
•For next 16 GB from range of 12-28 GB, we will set aside 2% of it which is equal
to 327 MB.
•For remaining 72 GB (100 GB memory – 28 GB), we will set aside 1% of it which
is 720 MB.
Now we just need to calculate sum of all these values.1619
 Physical to Virtual Machine (P2V)
Conversion
 What is P2V?
 Intuitively, P2V stands for “physical to virtual” and represents the process of
converting and migrating a physical computer image into a virtual machine (VM).
Unlike a migration where you take the applications and data from one computer and
copy them to an entirely new platform, with VMware Converter for P2V, you take an
exact image-level copy of the physical computer and transform it into a virtual
machine.
 The virtual machine then retains the same state as the physical computer, including the
operating system, applications, configuration, data, and even assigned resources.
However, after a P2V operation, the assigned resources, such as CPU and memory, can
easily be adjusted or changed.
Physical to Virtual Machine (P2V)
Conversion
 It is process through which physical machines are converted into
virtual machines (VMs)
 Clones data from physical machine’s disk to VM disk (Cloning is the
process of creating a cloned disk, where the cloned disk is a virtual
disk that is an exact copy of the source physical disk)
 Performs system configuration of the destination VM such as:
- change IP address and computer name
- install required device drivers to enable the VM to
boot
Benefits of P2V Converter

 Reduces time needed to setup new VM

 Enables migration of legacy machine to a new hardware without reinstalling OS or
application
 Performs migration across heterogeneous hardware
 Achieves objective of Server consolidation
 Supported Types of Migration
 You can use VMware converter to perform a physical to virtual conversion of a
powered on:
 a local machine where VMware Converter is running
 a remote Windows host
 a remote Linux host
 You can also convert machines that are powered off in the following environments:
 VMware Infrastructure virtual machine (vSphere)
 VMware Workstation or other VMware virtual machine
 Hyper-V Server
Components of P2V Converter
 There are three key components
 Converter server
 Is responsible for controlling conversion process
 Is used for hot conversion only
 Pushes and installs agent on the source machine
 Converter agent
 Is responsible for performing the conversion
 Is used in hot mode only
 Installed on physical machine to convert it to virtual machine
 Converter Boot CD
 Bootable CD contains its OS and converter application
 Converter application is used to perform cold conversion
Conversion Options
 Hot conversion
 Occurs while physical machine is running
 Performs synchronization
 Copies blocks that were changed during the initial cloning period
 Performs power off at source and power on at target VM
 Changes IP address and machine name of the selected machine, if both machines must
co-exist on the same network
 Cold conversion
 Occurs while physical machine is not running OS and application
 Boots the physical machine using converter boot CD
 Creates consistent copy of the physical machine
Hot Conversion Process
1. The conversion server prepares the source machine for the conversion by
installing the agent on the source physical machine
2. The agent takes a snapshot of the source volume
3. The converter server creates a virtual machine on the destination machine
4. The agent clones the physical disk of source machine (using snapshot) to the
virtual disk of the destination virtual machine
5. The agent synchronizes the data and installs the required drivers to allow the
operating system to boot from a VM and personalize the virtual machine
(changes the IP address and machine name, for eg)
6. The virtual machine is ready to run on the destination server.
1. The converter installs the agent on the source machine
2. The Agent takes a snapshot of the source volumes
3. Converter creates a new virtual machine on the destination machine
4. The Agent copies volumes from the source machine to the destination machine.
5. The Agent installs the required drivers to allow the operating system to boot in a virtual machine
6. The Agent personalizes the virtual machine (for example, changing the IP information).
7. Converter removes all traces from the source machine
Cold Conversion Process
1. Boot the source machine from the converter boot CD and use the converter
software to define conversion parameters and start the conversion
2. The converter application creates a new virtual machine on the destination
physical machine
3. The converter application copies volumes from the source machine to the
destination machine
4. The converter application installs the required drivers to allow the OS to boot
in a virtual machine and personalizes the virtual machine (for eg, changing
the IP address and machine name)
5. The virtual machine is ready to run on the destination sever
1. User boots the source machine from the Converter Boot CD and uses VMware Converter to define
and start the migration.
2. Converter copies the source volumes into a RAM disk.
3 Converter creates a new virtual machine on the destination machine.
4 Converter copies volumes from the source machine to the destination machine.
5 Converter installs the required drivers to allow the operating system to boot in a virtual
machine.
6 Converter personalizes the virtual machine (for example, changing the IP information).
7 User removes Boot CD and reboots the source physical machine to return it to its own
operating system. The virtual machine is ready to run on the destination machine
P2V Conversion: Considerations

 Some hardware-dependent drivers may not be preserved

 Source machine configuration remains unchanged such as: OS configuration
etc..
 Source and target machines will have the same identities
 Running them on the same network might result in conflicts
 Applications that depend on characteristics of the hardware may not work
Virtual Machine Affinity
 VM to VM affinity:
 Selected VMs should run on same hypervisor
- To improve performance, if VMs are communicating
with each other heavily
 Anti-affinity ensures that selected VMs are not together on a hypervisor
 VM to physical server affinity:
 Specify whether selected VM can be placed only on a particular hypervisor (eg. Licensing
issues)
 Anti-affinity is allowing VM to move on different hypervisors in a cluster
Topics to concentrate

 Comparison of types of VMM/hypervisor and explaining the specific type

 Comparison of Techniques of virtualization and explaining the specific technique
 Optimization of CPU and memory techniques
 P2V conversion process and benefits