Management of virtual machine migration in an operating environment

Patent metadata

Field	Value
Publication number	US-2016239335-A1
Application number	US-201615136456-A
Country	US
Kind code	A1
Filing date	Apr 22, 2016
Priority date	Nov 19, 2013
Publication date	Aug 18, 2016
Grant date	—

Abstract

Embodiments directed toward a method, and a system. A method can be directed toward deciding whether to accept a virtual machine migration on a host. The method can include receiving a request to host a migrated virtual machine. The method can include determining if the host is overcommitted. The method can include selecting a low priority virtual machine in response to the host being overcommitted. The method can include determining if a resource for the low priority virtual machine can be reduced to accommodate the migrated virtual machine. The method can include reducing the resources for the low priority virtual machine in response to the resources being able to be reduced. The method can include accepting the request to host the migrated virtual machine in response to the reduction of the resources.

First claim

What is claimed is:

1 . A computer-implemented method for migrating a virtual machine among a plurality of hosts on a network, comprising:
a first host of the plurality of hosts monitoring the first host hosting a first plurality of virtual machines for a first virtual machine migration event; the first host determining whether the first virtual machine migration event causes the first host to be overcommitted; the first host identifying a first low priority virtual machine on the first host in response to the first host being overcommitted; the first host determining a first optimization path that includes migrating the first low priority virtual machine to a second host of the plurality of hosts; the first host implementing the first optimization path for the first low priority virtual machine on the first host without input from the second host; the second host automatically accepting the first low priority virtual machine;
the second host monitoring the second host hosting a second plurality of virtual machines for a second virtual machine migration event;
the second host determining whether the second virtual machine migration event causes the second host to be overcommitted; the second host identifying a second low priority virtual machine on the second host in response to the second host being overcommitted; and the second host implementing a second optimization path for the second low priority virtual machine on the second host.

2 . The method of claim 1 , wherein the second optimization path includes migrating the second low priority virtual machine to a third host of the plurality of hosts, further comprising:
determining whether the third host will be overcommitted beyond an overcommitment threshold; and the third host hosting the second low priority virtual machine in response to the third host being overcommitted within the overcommitment threshold.

3 . The method of claim 2 , further comprising receiving, from the second host, data metrics used to determine the overcommitment and identify the second low priority virtual machine.

4 . The method of claim 1 , further comprising:
determining whether a resource on the first low priority virtual machine can be reduced; and reducing the resource for the first low priority virtual machine in response to the low priority virtual machine being able to be reduced.

5 . The method of claim 4 , wherein reducing the resource comprises:
determining an optimal size of the first low priority virtual machine by examining a usage pattern for the low priority virtual machine, and reducing the resource so that the usage pattern is less than the optimal size of the first low priority virtual machine.

6 . The method of claim 1 , wherein determining whether the first virtual machine migration event causes the first host to be overcommitted comprises:
determining requirements from the first plurality of virtual machines on the first host and the first low priority virtual machine from the first virtual machine migration event; determining a resource of the first host; comparing the requirements to the resource; and identifying an overcommitment in response to the requirements being greater than the resource and within an overcommitment threshold

7 . A system for migrating a virtual machine, comprising:
one or more computer processors of a first host, configured to:
monitor, a first plurality of virtual machines hosted on the first host for a first virtual machine migration event;
determine, whether the first virtual machine migration event causes the first host to be overcommitted;
identify, a first low priority virtual machine on the first host in response to the first host being overcommitted;
determine a first optimization path that includes migrating the first low priority virtual machine to a second host; and
implement a first optimization path for the first low priority virtual machine on the first host without input from the second host;
one or more processor of a second host, configured to:
automatically accept the first low priority virtual machine;
monitor, a second plurality of virtual machines hosted on the second host for a second virtual machine migration event;
determine, whether the second virtual machine migration event causes the second host to be overcommitted;
identify, a second low priority virtual machine on the second host in response to the second host being overcommitted; and
implement a second optimization path for the second low priority virtual machine on the second host.

8 . The system of claim 7 , wherein the one or more computer processors are configured to implement the first optimization path by:
predicting whether a migration of the first low priority virtual machine to the second host causes the second host to be overcommitted; and migrating the low priority virtual machine to the second host in response to the second host not being overcommitted.

Assignees

• IBM

Inventors

• Anderson Jason L
• Bhatia Nimesh
• Boss Gregory J
• Singh Animesh

Classifications

• G06F9/45558 Primary

  Hypervisor-specific management and integration aspects · CPC title

• H04L67/16

  Electricity · mapped topic

• H04L67/1095

  Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes · CPC title

• G06F2009/4557

  Distribution of virtual machine instances; Migration and load balancing · CPC title

• G06F9/4875

  with migration policy, e.g. auction, contract negotiation · CPC title