Browse Prior Art Database

Method of coalescing pages of source System and Seprating them in Target System in Concurrent Live Virtual Machine Movement. Disclosure Number: IPCOM000245198D
Publication Date: 2016-Feb-18
Document File: 4 page(s) / 75K

Publishing Venue

The Prior Art Database


Disclosed is a method for improved concurrent Live Virtual Machine Movement across multiple systems. In an embodiment where multiple VMs share set of pages among themselves and needs to be migrated live to a one or more systems, this article prvoide a method to transfer the duplicated pages from the source system to the destination system. it also describes the grouping of moving virtual machines per destination.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 40% of the total text.

Page 01 of 4

Method of coalescing pages of source System and Seprating them in Target System in Concurrent Live Virtual Machine Movement .

Concurrent Live Virtual Machine Movement is a feature of Servers,on capable VM systems, the ability to support migrating up to 32 VMs concurrently from a managed system to one or multiple managed systems.

To achieve Concurrent Live Virtual Machine Movement, the source Managed System should have at least two Virtual input/output servers configured as Moving Service Partition . Each Moving Service Partition should be capable of handling several concurrent VM migrations. If more number of client VMs are to be migrated to another single Managed System, then the destination managed system should also have at least two Moving Service Partition to be configured on it, and each one can handles half of the total concurrent partition migrations.

The main goal of this feature is to provide our customer an easy and quick way to evacuate all the partitions or Virtual Machine to concurrently from one managed system.

Problem to be solved in Concurrent Live Virtual Machine Movement :

Most of the time, all partitions in the source virtual machine may have same level of OS and same applications running and operating on same set of data. This article list below factors that need to be considered during Concurrent Virtual machine migration operation.

1. Duplicate pages of the VM 's Participating in Concurrent Virtual machine migration operation to a specified destination system :

The Concurrent Live Virtual Machine Movement usually migrate multiple Virtual machines (up to 32 Virtual machines) to a single destination Virtual machine though two MSPs . Since each MSP handles

up to 16 Virtual machines and Hypervisor need to pump the data of 16 Virtual machines via each MSP by maintaining two sets of page lists . So there is a scope for identifying duplicate pages from these lists.

Futher to add If both MSPs are transferring the pages to same destination Virtual machine then duplication of pages can be even identified across the MSPs which transfer the data.

So there is scope for identifying duplicate pages in each list containing pages belonging to 16 Virtual machines or 32 Virtual machines and de-duplicate pages

in the Source System side and sending single copy to destination. This will considerably reduce convergence time of Concurrent Live Virtual Machine Movement by

reducing the amount of memory to be migrated

2. Group the Virtual machines Participating in Concurrent Live Virtual Machine Movement to a specified Destination :

The concurrent partition migration function migrate up to 32 Virtual machines to single or multiple destination system. If the source system operates with multiple destination system to move total N number of Virtual machines, we need a system of identifying

the Virtual machines of similar characteristics (same operating system level, use of shared resources, application's similarities) in same group .