Methods and systems for establishing connections associated with virtual machine migrations

• US 10,664,301 B2
• Filed: 03/26/2018
• Issued: 05/26/2020
• Est. Priority Date: 02/24/2015
• Status: Active Grant

• Current Assignee: Red Hat Israel Ltd. (International Business Machines Corporation)
• Original Assignee: Red Hat Israel Ltd. (International Business Machines Corporation)
• Inventors: Tsirkin, Michael
• Primary Examiner(s): Truong, Camquy
• Application Number:
  US15/936,077
• Publication Number:
  US 20180217861A1
• Time in Patent Office: 792 Days
• CPC Class Codes: G06F 2009/4557 Distribution of virtual machine instances; Migration and load balancing
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects

Abstract

An example method of establishing one or more connections between a target host machine and a remote endpoint connected to a virtual machine (VM) running on a source host machine includes receiving, by a target hypervisor executable on a target host machine, a list of one or more remote endpoints to which a VM executable on a source host machine is connected. The source and target host machines are coupled to a network. The method further includes initiating, by a host communication manager executable on the target host machine, a connection to one or more of the remote endpoints specified in the list before the VM has completed migration from the source host machine to the target host machine.

Claims

1. A system comprising:

a target hypervisor that receives a first list of one or more remote endpoints to which a first VM executable on a first source host machine is connected and receives a second list of one or more remote endpoints to which a second VM executable on a second source host machine is connected, wherein the first list is received before the first VM has competed migration to a target host machine from the first source host machine, and the second list is received before the second VM has competed migration to the target host machine from the second source host machine; and

a host communication manager that establishes a first network connection to a first remote endpoint included in the first list before the first VM has completed migration from the first source host machine to the target host machine and that establishes a second network connection to a second remote endpoint included in the second list before the second VM has completed migration from the second source host machine to the target host machine.

2. The system of claim 1, wherein the first source host machine and the target host machine are coupled to an InfiniBand network.

3. The system of claim 2, wherein the target host machine is an InfiniBand node including one or more Host Channel Adaptors (HCA), each HCA includes one or more ports and one or more queue pairs, and the target host machine connects to an InfiniBand fabric via an HCA.

4. The system of claim 3, wherein a port on an HCA supports a set of services, and each service is identified by a service identifier (ID).

5. The system of claim 4, wherein the host communication manager establishes the first network connection to the first remote node by using the service ID, and the host communication manager associates an incoming connection request with an entity providing the service identified by the service ID.

6. The system of claim 3, wherein a queue pair includes a receive queue, and the target hypervisor receives data packets from the first remote endpoint via the receive queue for the first VM.

7. The system of claim 6, wherein the queue pair further includes a send queue, and the target hypervisor sends data packets to the first remote endpoint via the send queue for the first VM.

8. The system of claim 1, wherein the first remote endpoint is a VM.

9. The system of claim 1, wherein the first remote endpoint is different from a VM.

10. The system of claim 1, comprising:

a source hypervisor executable on the first source host machine, wherein the source hypervisor tracks one or more network connections to which the first VM is connected.

11. The system of claim 10, wherein the source hypervisor detects a new connection between the first VM and a new remote endpoint and adds information based on the new connection to the first list.

12. The system of claim 11, wherein the source hypervisor adds a service ID and a port ID associated with the new connection to the first list.

13. The system of claim 11, wherein the source hypervisor adds an Internet Protocol (IP) address of the new remote node and a port ID associated with the new connection to the first list.

14. The system of claim 13, wherein the port ID is an HCA port ID.

19. The system of claim 1, wherein the first source host machine is different from or the same as the second source host machine.

15. A method comprising:

receiving, by a target hypervisor executable on a target host machine, a first list of one or more remote endpoints to which a first virtual machine (VM) executable on a first source host machine is connected, wherein the first list is received before the first VM has competed migration to the target host machine from the first source host machine;

receiving, by the target hypervisor, a second list of one or more remote endpoints to which a second VM executable on a second source host machine is connected, wherein the second list is received before the second VM has competed migration to the target host machine from the second source host machine;

establishing, by a host communication manager executable on the target host machine, a first network connection to one or more of the remote endpoints included in the first list before the first VM has completed migration from the first source host machine to the target host machine; and

establishing, by the host communication manager, a second network connection to one or more of the remote endpoints included in the second list before the second VM has completed migration from the second source host machine to the target host machine.

16. The method of claim 15, wherein the first source host machine and the target host machine are coupled to an InfiniBand network.

17. The method of claim 15, wherein the first list is specific to the first VM and the second list is specific to the second VM.

20. The method of claim 15, wherein the first source host machine is different from or the same as the second source host machine.

18. A machine-readable medium comprising a plurality of machine-readable instructions that when executed by one or more processors is adapted to cause the one or more processors to perform a method comprising:

receiving, by a target hypervisor executable on a target host machine, a first list of one or more remote endpoints to which a first virtual machine (VM) executable on a first source host machine is connected, wherein the first list is received before the first VM has competed migration to the target host machine from the first source host machine;

receiving, by the target hypervisor, a second list of one or more remote endpoints to which a second VM executable on a second source host machine is connected, wherein the second list is received before the second VM has competed migration to the target host machine from the second source host machine; and

establishing, by a host communication manager executable on the target host machine, a first network connection to one or more of the remote endpoints included in the first list before the first VM has completed migration from the first source host machine to the target host machine; and

establishing, by the host communication manager, a second network connection to one or more of the remote endpoints included in the second list before the second VM has completed migration from the second source host machine to the target host machine.