Browse Prior Art Database

Method for identifying the necessity of devices for Virtual Machine migration . Disclosure Number: IPCOM000247759D
Publication Date: 2016-Oct-06
Document File: 3 page(s) / 24K

Publishing Venue

The Prior Art Database


The art of determining if a Virtual Machine could be migrated without a major impact to it's working or applications is a very daunting and complicated task. Automating this task (maybe, with minimal manual intervention) would be advantageous for businesses. This paper describes the method for identifying and categorizing devices of a Virtual Machine based on the necessity of device(s) and determining the do-ability of Virtual Machine migration.

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

Page 01 of 3

Method for identifying the necessity of devices for Virtual Machine migration .

Problem background and description :

Virtual Machine(VM) Migration is a widely acknowledged feature of most top-selling virtualization solutions; helping businesses tackle the hardware maintenance and server consolidation challenges without the need to affect solution availability. To reap the advantages of this flexibility, businesses have to plan their server networking and storage infrastructure, which includes cabling layout, well in advance. Providing the same/similar set of devices across servers is a daunting task and often proves to be a bottleneck for the ability to migrate a VM, to a not planned destination server. The objective of this paper is to

The validation process for a successful Virtual Machine(VM) migration typically requires access to the same/similar set of devices on the destination server. But in many cases, not all the virtual devices(disks, network adapter, virtual CD etc.) assigned to a migrating VM needs to be accessible/copied on destination machine for the following reasons :
1. VM may not be using all of the devices assigned to it. Some of them might have just been assigned to the client for future scalability.

2. There could be some devices(e.g. disks) used by some non-critical applications; and user might not worry too much about that particular application going down/fail.

3. For non-shared storage migration, storage of the VM needs to be replicated on the destination storage; and the destination storage might not have enough free storage to host all the VM's disk. For this scenario, there could still be enough storage space on destination for the critical disks of the migrating VM.

If VM migration(validation) process does not find all the devices assigned to the VM on the destination server then VM is not migrated. Today there is no known intelligent way to identify the unused devices of a VM. If we are able to do that then it is very much possible that the VM still could have been migrated without impacting the workloads, or with acceptable and known impact to select_applications/network/storage.

In some critical junctures (e.g. hardware failures) and in short-notice there might be a requirement to migrate a VM to a destination server with acceptable problems/risks.

Solution :

This article proposes an idea to device an efficient methodology to identify and classify the various devices used by VM to different categories. This classification would be based on multiple parameters. Use the intelligently computed(optionally, manually interfered) information for determining the success of VM migration with critical application not being impacted.Categorize and classify devices of VM as "critical or noncritical" based on one or multiple of these methods :


Page 02 of 3

1. All the virtual device traffic(e.g. IO) for the VM happens with the knowledge of the Hosting partition/Hypervisor. The hosting partition (with a new prop...