Scribd
Upload
87 views10 pages

Virtual Machine Migration

Virtual machine migration can be either non-live or live. Live migration refers to moving a running virtual machine between physical hosts with minimal disruption. There are two techniques for live migration - pre-copy migration and post-copy migration. Pre-copy migration copies memory pages from the source host to the destination host while the VM is running, then stops and transfers remaining pages. Post-copy migration first transfers VM state and then memory pages on-demand, redirecting any faults to the source host. Common virtual machine platforms support live migration through these pre-copy and post-copy techniques.

Uploaded by

nitin goswami
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
87 views10 pages

Virtual Machine Migration

Virtual machine migration can be either non-live or live. Live migration refers to moving a running virtual machine between physical hosts with minimal disruption. There are two techniques for live migration - pre-copy migration and post-copy migration. Pre-copy migration copies memory pages from the source host to the destination host while the VM is running, then stops and transfers remaining pages. Post-copy migration first transfers VM state and then memory pages on-demand, redirecting any faults to the source host. Common virtual machine platforms support live migration through these pre-copy and post-copy techniques.

Uploaded by

nitin goswami
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 10

VIRTUAL MACHINE(VM)

MIGRATION
AMBRISH GANGAL
VM migration - TYPES
• Virtual machine migration is the migration of virtual machine
from one physical host to another without disrupting the users.
It is categorized as:
• (a) Non-live or Off-line Virtual Machine Migration: In it, Virtual
machine at the source host is paused and then transfer all
states of source host to the target or destination host and then
finally resume the working of virtual machine at the target host.
The major drawback of it is that it results in larger down time.
• (b) Live Virtual Machine Migration: In it, Virtual machine is
transferred from one host to another with minimum possible
disruption of services.
Live migration
• Live migration refers to the process of moving
a running virtual machine or application
between different physical machines without
disconnecting the client or application.
Memory, storage, and network connectivity of
the virtual machine are transferred from the
original guest machine to the destination.
Virtual Machine migration Techniques

• Pre-copy memory migration


• Post-copy memory migration
Pre-copy memory migration
Warm-up phase
• In pre-copy memory migration, the Hypervisor typically copies all the memory
pages from source to destination while the VM is still running on the source. If
some memory pages change (become 'dirty') during this process, they will be
re-copied until the rate of re-copied pages is not less than page dirtying rate.
Stop-and-copy phase
• After the warm-up phase, the VM will be stopped on the original host, the
remaining dirty pages will be copied to the destination, and the VM will be
resumed on the destination host. The time between stopping the VM on the
original host and resuming it on destination is called "down-time", and ranges
from a few milliseconds to seconds according to the size of memory and
applications running on the VM. There are some techniques to reduce live
migration down-time, such as using probability density function of memory
change.
Post-copy VM migration
• Post-copy VM migration is initiated by suspending the VM at the source.
• With the VM suspended, a minimal subset of the execution state of the
VM (CPU state, registers and, optionally, non-pageable memory) is
transferred to the target. The VM is then resumed at the target.
• Concurrently, the source actively pushes the remaining memory pages of
the VM to the target - an activity known as pre-paging. At the target, if the
VM tries to access a page that has not yet been transferred, it generates a
page-fault.
• These faults, known as network faults, are trapped at the target and
redirected to the source, which responds with the faulted page. Too many
network faults can degrade performance of applications running inside
the VM. Hence pre-paging can dynamically adapt the page transmission
order to network faults by actively pushing pages in the vicinity of the last
fault.
Post-copy VM migration (CONT..)
• An ideal pre-paging scheme would mask large majority of
network faults, although its performance depends upon the
memory access pattern of the VM's workload. Post-copy
sends each page exactly once over the network.
• In contrast, pre-copy can transfer the same page multiple
times if the page is dirtied repeatedly at the source during
migration. On the other hand, pre-copy retains an up-to-date
state of the VM at the source during migration, whereas with
post-copy, the VM's state is distributed over both source and
destination. If the destination fails during migration, pre-
copy can recover the VM, whereas post-copy cannot.
Post-copy VM migration
VM managers with live migration support
• Virtuozzo
• Xen since May 18, 2007
• OpenVZ
• Parallels Cloud Server
• Workload Partitions
• Integrity Virtual Machines
• KVM
• Oracle VM Server for x86
• Oracle VM Server for SPARC
• POWER Hypervisor (PHYP)
• VMware ESX
• IBM Live Partition Mobility, since 2007
• Hyper-V Server 2008 R2
• VirtualBox
• Proxmox Virtual Environment

You might also like