M5
M5
CONTENT SOURCE
• “Live Migration of Virtual Machines”, Christopher Clark, Keir Fraser, Steven Hand,
Jacob Gorm Hansen, Eric Jul, Christian Limpach, Ian Pratt, Andrew Warfield
• “Post-Copy Based Live Virtual Machine Migration Using Adaptive Pre-Paging and
Dynamic Self-Ballooning”, Michael R. Hines and Kartik Gopalan
Source Contents Credit to:
VM
Source Target
Review: Virtual Machines
A virtual machine provides interface identical to underlying bare hardware
▫ i.e., all devices, interrupts, memory, page tables etc.
Ø Virtualization provides facility to migrate virtual machine from one host (source)to
another physical host (destination).
Ø Virtual Machine Migration is a useful tool foradministrator of data center andclusters.
Review: Virtual Machines in Cloud
q Benefits of Virtual Machines
Virtualization helps in making efficient use of hardware resources
Facilitates a greater degree of abstraction
Easily move from one piece of hardware to another
Replicate them at will
Create more scalable and flexible infrastructure
High Availability and Fault tolerance (How?)
q Cloud computing has taken that degree of efficiency and agility realized from
virtualization
Pooled resources
Geographic diversity
Universal connectivity
7
Motivation
• Consider a data center consisting of “n” physical machines (PM) hosting “m” VMs
implementing one customer application each
• Resources(CPU, Network, Memory, I/O) are allocated to each VM to handle the
workload and operate at certain performance level (SLA)
• Each VM sees workload fluctuation (WHY?) from time to time =>
resource requirement changes Network Bandwidth = 10 Gbps
PM Memory = 16 GB
# of user visit
Capacity CPU = 8 cores
increases
VM1 VM2
VM1 VM2
cricinfo mail server Resource N = 5Gbps
N = 5Gbps
Allocation M = 8GB
Virtualization Layer M = 8GB
C = 4 cores C = 4 cores
Hardware
Motivation
q Main Issues:
What if PM does not have (enough or no) idle resources to satisfy VM's
requirement?
• Performance of the application degrades
• SLA violation occurs
q Key Ideas
• Replication VMs
• Migrating VMs
Virtual Machine Migration
• To Maintain/Upgrade
• To Optimize the Performance
• To Protect SLA
• To Improve QoE
When we need to migrate? [NSDI’ 07]
• Hotspot Detection
▫ Black-box Monitoring
CPU
Network
Memory
▫ Gray-box Monitoring
Gather OS level statistics and application logs
• A hotspot is flagged only if thresholds or SLAs are exceeded for a sustained time
When we need to migrate? [FGCS’ 12]
Ø Fault tolerance allows theVMs to continue its jobeven any part of system fails.
Ø This technique migrates theVM from one physical serverto another physical server
based upon the prediction of the failure occurred.
Ø Fault tolerant migration technique is to improve the availability of physical server
and avoids performance degradation of applications.
Load Balancing Migration Techniques
Ø The Load balancing migration technique aims to distribute load across the physical
servers to improve the scalability of physical servers in cloud environment.
Ø The Load balancing improves the
Ø resource consumption
Ø implementation offailover
Ø enhancing scalability
Energy Efficient Migration Techniques
Ø The power consumption of Data center is mainly based on the utilization of the
servers and theircooling systems.
Ø The servers typically need up to 70 percentage of their maximum power
consumption even at theirlow utilization level.
Ø Therefore, there is a need for migration techniques that conserves the energy of servers
by optimum resourceutilization.
V M Migration Methods
§ The status of the VM loses and user can notice the service interruption in cold
migration. First, VM is suspended, then its state is transferred, and lastly, VM is
resumed at destination host.
“Live Migration of Virtual Machines”, Christopher Clark, Keir Fraser, Steven Hand, Jacob Gorm Hansen, Eric Jul, Christian Limpach, Ian Pratt, Andrew Warfield
“Post-Copy Based Live Virtual Machine Migration Using Adaptive Pre-Paging and Dynamic Self-Ballooning”, Michael R. Hines and Kartik Gopalan
Live Migration
What ismigrated?
Source Destination
25
Steps to migrate aVM
• Broad steps in any migration technique: Suppose we are migrating a
VM from host A to host B
1. Setup target host B, reserve resources for the VM
2. Push phase: push some memory of VM from A to B
3. Stop-and-copy: stop the VM at A, copy CPU context, and some memory
4. Pull phase: Start VM at host B, pull any further memory required from A
5. Clean up state from host A, migration complete
• Total migration time: time for steps 2,3,4
• Service downtime: time for step 3
• Other metrics: impact on application performance, network
bandwidth consumed, total pages transferred
26
Flavors of migrationtechniques
Source Host
Destination Host
.BI
.VS
.X
.VH
V
DML
N
Storage
Design-memory migration
Implementation details(Xen)
What aboutfailures?