CN108255570B - Method, device and system for virtual machine migration between heterogeneous virtual machine monitor platforms - Google Patents

Abstract

Embodiments of the present invention provide a method, device and system for virtual machine migration between heterogeneous virtual machine monitor platforms, and relate to the field of virtualization. The method includes: an original hypervisor platform obtains original description information of a running virtual machine VM ;The original hypervisor platform sends the original description information to the target hypervisor platform; the target hypervisor platform receives the original description information sent by the original hypervisor platform; the target hypervisor platform obtains the target format information; the target hypervisor platform modifies the original description information according to the target format information, and obtains the VM on the target Target description information in the hypervisor platform; the target hypervisor platform rebuilds the VM according to the target description information. The problem in the prior art that the VM needs to be offline, that is, the business needs to be interrupted, is solved when the VM is migrated between heterogeneous hypervisor platforms in the prior art, and the effect of keeping the VM online during the VM migration process to avoid business interruption is achieved.

Description

Method, device and system for virtual machine migration between heterogeneous virtual machine monitor platforms

technical field

Embodiments of the present invention relate to the field of virtualization technologies, and in particular, to a method, device and system for virtual machine migration between heterogeneous virtual machine monitor platforms.

Background technique

With the development of virtualization technology, heterogeneous Hypervisor (virtual machine monitor) platforms have appeared in the market. In order to ensure that the services deployed on the original hypervisor platform are not affected when the new hypervisor platform is used, it is necessary to migrate the VM (Virtual Machine, virtual machine) on the original hypervisor platform. The formats of the representation information used to represent the VMs in the heterogeneous hypervisor platforms are different.

An existing method for migrating VMs between heterogeneous hypervisor platforms includes: the original hypervisor platform shuts down the running VM, and obtains an image (image) file and an XML (Extensible Markup Language, extensible markup language) file corresponding to the VM; The file is converted into an image file corresponding to the target hypervisor platform according to the format requirements of the target hypervisor platform for the image file, uninstalls the VM driver of the original hypervisor platform in the converted image file, and implants the VM driver of the VM in the target hypervisor platform; Convert the XML file into the XML file corresponding to the target Hypervisor platform according to the format requirements of the target Hypervisor platform for the XML file; send the obtained image file and XML file to the target Hypervisor platform; the target Hypervisor platform rebuilds the VM according to the received image file and XML .

In the process of implementing the present invention, the inventor found that the above process at least has the following problems: when migrating a VM, the original platform needs to shut down the VM, and only after the migration is completed, the VM can be created in the target hypervisor platform. In the prior art, the VM is in a shutdown state during the migration process, that is, services are interrupted.

SUMMARY OF THE INVENTION

In order to solve the problem in the prior art that the VM will be shut down and services will be interrupted during the VM migration process, the embodiments of the present invention provide a VM migration method, device and system between heterogeneous hypervisor platforms, and the technical solutions are as follows:

In a first aspect, a VM migration method between heterogeneous hypervisor platforms is provided, and the method includes:

The original hypervisor platform obtains the original description information of the VM in the original hypervisor platform, and sends the original description information to the target hypervisor platform; wherein the original description information includes the original representation information used to represent the VM in the memory of the original hypervisor platform. The target hypervisor platform and the original hypervisor platform are heterogeneous platforms, that is, the target format used to represent the representation information of the VM in the memory of the target hypervisor platform and the original format used to represent the representation information of the VM in the memory of the original hypervisor platform The format is different.

Correspondingly, the target hypervisor platform receives the original description information sent by the original hypervisor platform, modifies the original description information according to the pre-obtained target format information, and obtains the target description information; rebuilds the VM according to the target description information. The target format information includes the target format.

By acquiring the original description information of the original hypervisor platform during the running of the VM in the original hypervisor platform, the original description information includes the original representation information of the VM in the memory of the original hypervisor platform; sending the original description information to the target hypervisor platform, The target hypervisor platform is made to modify the received original description information according to the target format information, obtain the target description information, and reconstruct the VM according to the target description information; wherein, the target format information includes the target format of the VM in the memory of the target hypervisor platform; In the prior art, when a VM is migrated between heterogeneous hypervisor platforms, the VM needs to be offline, that is, the service needs to be interrupted; the VM is kept online during the VM migration process to avoid service interruption, and the effect of smooth evolution between different platforms can be achieved. .

Optionally, the steps of modifying the original description information by the target hypervisor platform to obtain the target description information can be implemented as follows:

The target hypervisor platform converts the original representation information according to the target format, and obtains the target representation information. The target description information and target representation information together form the target description information.

Optionally, in a second possible implementation manner, the target hypervisor platform converts the original representation information, and the step of obtaining the target representation information may include:

The target hypervisor platform generates the target data structure according to the target format;

The target hypervisor platform writes the original representation information into the target data structure according to the difference between the original format and the target format, and obtains the target representation information.

Optionally, in a third possible implementation manner, in the process of converting the original representation information by the target hypervisor platform, if the original format of the original representation information includes the target field, the target field is changed in the process of modifying the original representation information. When set to invalid, the target field is a field that is included in the original format of the original presentation information but not included in the target format of the target presentation information.

Optionally, in a fourth possible implementation manner, the original hypervisor platform obtains original description information of the running virtual machine VM, including:

The original hypervisor platform obtains the original format of the VM in the memory of the original hypervisor platform;

The original Hypervisor platform performs binary analysis on the VM information in memory according to the original format and virtual machine communication support VMCS technology, and obtains the analysis results;

The raw hypervisor platform uses the analysis results as raw representation information.

In a fifth possible implementation manner, the original hypervisor platform obtains the original description information of the running virtual machine VM, and also includes:

The original hypervisor platform obtains the original extensible markup language XML file and the original image image file of the VM in the original hypervisor platform. At this time, the original description information also includes the original XML file and the original image file.

In a sixth possible implementation manner, when the original description information also includes the original XML file and original image file of the VM in the original Hypervisor platform;

The target hypervisor platform modifies the original description information according to the target format information to obtain the target description information of the VM in the target hypervisor platform, and further includes:

The target hypervisor platform obtains the target XML file corresponding to the target hypervisor platform according to the file format of the XML file and the original XML file in the target format information;

The target hypervisor platform obtains the target image file corresponding to the target hypervisor platform according to the file format of the image file and the original image file in the target format information; the target description information also includes the target XML file and the target image file.

A second aspect provides a VM migration method between heterogeneous hypervisor platforms, the method is used in the original hypervisor platform, and the method includes the steps on the original hypervisor platform side in the method of the first aspect.

In a third aspect, a method for migrating VMs between heterogeneous hypervisor platforms is provided. The method is used in a target hypervisor platform, and the method includes the steps on the target hypervisor platform side in the method of the first aspect.

In a fourth aspect, a VM migration device between heterogeneous hypervisor platforms is provided, and the device is used in the original hypervisor platform to implement the functions described in the second aspect. The functions can be implemented by hardware, or can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

A fifth aspect provides a VM migration device between heterogeneous hypervisor platforms, where the device is used in the original hypervisor platform to implement the functions described in the third aspect. The functions can be implemented by hardware, or can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

In a sixth aspect, a VM migration system between heterogeneous hypervisor platforms is provided, and the system includes an original hypervisor platform and a target hypervisor platform. Wherein, the original hypervisor platform includes the device described in the fourth aspect, and the target hypervisor platform includes the device described in the fifth aspect.

These and other aspects of the invention will be more clearly understood from the description of the following embodiments.

Description of drawings

FIG. 1 is a schematic diagram of an implementation environment involved in various embodiments of the present invention.

FIG. 2 is a method flowchart of a method for VM migration between heterogeneous hypervisor platforms provided by an embodiment of the present invention.

FIG. 3 is a schematic diagram of generating original representation information by an original Agent provided by an embodiment of the present invention.

FIG. 4 is a schematic structural diagram of a VM migration apparatus between heterogeneous hypervisor platforms according to an embodiment of the present invention.

FIG. 5 is a schematic structural diagram of a VM migration apparatus between heterogeneous hypervisor platforms according to an embodiment of the present invention.

Detailed ways

In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be described clearly and completely below with reference to the accompanying drawings in the embodiments of the present invention.

Please refer to FIG. 1 , which shows a schematic diagram of an implementation environment provided by various embodiments of the present invention. As shown in FIG. 1 , the implementation environment 100 includes an original hypervisor platform 110 , a target hypervisor platform 120 , and a VM 130 running on the original hypervisor platform 110 that needs to be migrated to the target hypervisor platform 120 .

A hypervisor platform is a computer system running on a host to provide a running environment and running resources for a VM. The host refers to a computer that hosts each virtual machine in physical existence, and the running resources provided by the hypervisor platform for the VM include instances and memory. Usually, the original hypervisor platform 110 and the target hypervisor platform 120 run in different hosts, which is not limited.

In the following embodiments, the original hypervisor platform 110 refers to the platform where the VM 130 is located before the migration, the target hypervisor platform 120 refers to the platform where the VM 130 is migrated, and the original hypervisor platform 110 can communicate with the target hypervisor platform 120 . In actual implementation, both the original hypervisor platform 110 and the target hypervisor platform 120 may run multiple VMs, and the figure only shows the VM 130 that needs to be migrated as an example, and other VMs are not shown.

In the following embodiments, the original hypervisor platform 110 and the target hypervisor platform 120 are heterogeneous platforms, that is, the original format of the VM 130 in the memory of the original hypervisor platform 110 and the original format of the information in the memory of the target hypervisor platform 120 The target formats for representing information in are often different. In addition, the format of the XML file of the VM 130 in the original hypervisor platform 110 and the format of the XML file in the target hypervisor platform 120 may be the same or different. Similarly, the format of the image file in the original hypervisor platform 110 is the same as that in the target hypervisor platform. The format of the image files in can be the same or different.

For example, the original hypervisor platform 110 may be a platform in a XEN (Open Source Virtual Machine Monitor) virtualization environment, and the target hypervisor platform 120 may be a KVM (Kernel-based Virtual Machine, open source system virtualization module) virtualization environment. platform. For another example, the original hypervisor platform 110 may be a platform in a KVM virtualization environment, and the target hypervisor platform 120 may be a platform in a Vmware (virtual machine software) virtualization environment. This embodiment does not limit the specific implementation of the original hypervisor platform 110 and the target hypervisor platform 120 .

In the following embodiments, as shown in FIG. 1 , an original Agent 111 (agent) may be deployed in the original hypervisor platform 110 , and a target Agent 121 may be deployed in the target hypervisor platform 120 . The original Hypervisor platform 110 uses the original Agent 111 to perform information acquisition and sends the acquired information to the target Agent 121. Similarly, the target Hypervisor platform 120 receives the information sent by the original Agent 111 through the target Agent 121 and performs operations such as VM reconstruction, and does not do this. limited.

In actual implementation, the original Agent 111 and the target Agent 121 may be program codes deployed in the hypervisor platform, which is not limited.

The VM 130 refers to the VM that runs on the original hypervisor platform 110 and needs to be migrated to the target hypervisor platform 120 . Services can be carried in the VM 130 .

Please refer to FIG. 2 , which shows a method flowchart of a method for VM migration between heterogeneous hypervisor platforms provided by an embodiment of the present invention. In this embodiment, the VM migration method is used in the implementation environment shown in FIG. 1 as an example. illustrate. As shown in Figure 2, the VM migration method includes:

Step 201, the original hypervisor platform obtains the original description information of the running VM.

The original hypervisor platform can run multiple VMs, and the original hypervisor platform can obtain the original description information of the VM to be migrated through the original agent in the original hypervisor platform. The original description information includes original representation information of the VM in the memory of the original hypervisor platform.

Optionally, this step may include the following steps:

First, the original hypervisor platform obtains the raw format of the VM in the memory of the original hypervisor platform.

Optionally, the original hypervisor platform can obtain the original format of the VM in the memory of the original hypervisor platform through the original agent.

The original format may include definitions of data structures of VM-related information presented in the original hypervisor platform. Optionally, the original format may include the fields contained in the data structure and the position corresponding to each field. For example, the original format includes VMCS, which includes Guest_cr (register) 0, Guest_cr3, Guest_cr4, Guest_es_base (Extra Segment, additional segment register), Guest_cs_base (Code Segment, code segment register), Guest_ss_base (Stack Segment, stack segment register) and The Guest_ds_base (Data Segment, data segment register) field is taken as an example, and the positions corresponding to each field are position 1, position 2, position 3, position 4, position 5, position 6, and position 7, respectively.

Second, the original Hypervisor platform performs binary analysis on the information of the VM in the memory according to the original format and the VMCS (Virtual Machine Communication Support, virtual machine communication support) technology, and obtains the analysis result.

After the original Agent obtains the original format, the original Agent can analyze the VM-related information in the memory according to the original format and in combination with the definition of VMCS in VT (Virtualization Technology), and obtain the analysis result. .

Optionally, the original Agent can simulate and generate the original VCPU (Virtual Central Processing Unit, virtualized central processing unit) data structure, the original EPT (Extended Page Tables, extended page table) data structure, and the original VMCS data structure. The information related to the VM is written in the above data structure in the original format. Optionally, the original Agent can implement the clarification of the definitions of the above data structure fields in combination with VT hardware-assisted standardization. For example, taking ES in VMCS as an example, GUEST_ES_SELECTOR=0x00000800.

For example, referring to FIG. 3 , the original Agent abstracts the hardware 31 presented by the original Hypervisor platform to the VM into the content shown in the data structure 32 . Fig. 3 only takes the presented part of the hardware as an example. In actual implementation, the original hypervisor platform can also present more or less hardware, which is not limited; The shown content is taken as an example. In actual implementation, more or less content may be included, which is not limited.

Third, the original hypervisor platform uses the analysis results as raw representation information.

After that, the original Agent can use the original XML file, the original image file and the original representation information as the original description information of the VM in the original Hypervisor platform.

In actual implementation, the original hypervisor platform can also obtain the original XML file and original image file of the VM in the original hypervisor platform, and the original XML file and original image file are also used as original description information, which is not limited. The XML file is a configuration file for configuring the VM, and the image file is a template for creating a VM.

Step 202, the original hypervisor platform sends the original description information to the target hypervisor platform.

The original hypervisor platform can send the original description information to the target agent in the target hypervisor platform through the original agent.

Step 203, the target hypervisor platform receives the original description information sent by the original hypervisor platform.

Correspondingly, the target agent receives the original description information sent by the original agent.

In step 204, the target hypervisor platform obtains target format information, where the target format information includes the file format of the XML file, the file format of the image file, and the target format corresponding to the target hypervisor platform.

This step is similar to step 201, the difference is that in this step, the target agent acquires the target format. The target format is the format of the VM in the memory of the target hypervisor platform. The target format includes the fields in the data structure and the corresponding position of each field.

Optionally, the target format information may further include the file format of the XML file of the VM and the file format of the image file when the VM is created in the target hypervisor platform.

Step 205, the target hypervisor platform acquires the target XML file corresponding to the target hypervisor platform according to the file format of the XML file and the original XML file in the target format information.

Optionally, the target hypervisor platform can detect whether the file format of the XML file in the target format information is consistent with the file format of the XML file in the original description information; if they are consistent, directly determine the original XML file in the original description information as the target. The target XML file corresponding to the hypervisor platform; if the detection result is inconsistent, convert the original XML file into a file supported by the file format of the XML file in the target format information, and use the conversion result as the target XML corresponding to the target hypervisor platform. document.

For example, if the original hypervisor platform is a platform under the XEN virtualization environment, and the target hypervisor platform is a platform under the KVM virtualization environment, the target hypervisor platform can use the target agent to convert the XML in the VHD (Virtual Hard Disk, virtual disk) format in XEN The file is converted into an XML file in the format of QCOW2 (QEMU Copy-On-Write, virtual operating system simulator) on KVM, which is not limited.

Step 206, the target hypervisor platform acquires the target image file corresponding to the target hypervisor platform according to the file format of the image file and the original image file in the target format information.

Optionally, the target hypervisor platform can detect whether the file format of the image file in the target format information is consistent with the file format of the image file in the original description information; if they are consistent, directly determine the original image file in the original description information as the target. The target image file corresponding to the hypervisor platform; if the detection result is inconsistent, convert the original image file to a file supported by the file format of the image file in the target format information, and use the conversion result as the target image corresponding to the target hypervisor platform. document.

Optionally, when the original description information does not include the original XML file and the original image file, the method may also not include steps 205 and 206, which will not be repeated here.

Step 207, the target hypervisor platform converts the original representation information according to the target format, and obtains the target representation information.

Optionally, this step may include the following steps:

First, the target hypervisor platform generates the target data structure according to the target format.

The target agent in the target hypervisor platform can simulate the VCPU data structure, EPT data structure and VMCS data structure corresponding to the VM according to the target format.

In this embodiment, only the target data structure includes the above-mentioned types for illustration. Optionally, the target data structure may also include other data structures, which is not limited in this embodiment.

Second, the target hypervisor platform writes the original representation information into the target data structure according to the difference between the original format and the target format, and obtains the target representation information.

After that, the target hypervisor platform can write the original representation information into the target data structure through the target agent according to the difference between the original format and the target format, and use the target data structure after writing the data as the target content information.

Differences between the original format and the target format include differences in where the same fields correspond and differences in the fields that are included.

When the difference between the original format and the target format includes the difference in the position corresponding to the same field, this step may include: the target Agent may write the content in the original VCPU into the target VCPU according to the position of each field in the VCPU in the target format Similarly, the content in the original EPT is written into the target EPT according to the position of each field in the EPT in the target format, and the content in the original VMCS is written into the target VMCS according to the position of each field in the target format.

For example, taking Guest_es_base in VMCS as an example, Guest_es_base is located at position 4 in the original VMCS and at position 44 in the target VMCS. Therefore, the target Agent can write the content of Guest_es_base in the original VMCS to the position of the target VMCS. 44 places. Optionally, please refer to the following table, the target hypervisor platform can copy the content of each information to the corresponding location of the information in the target hypervisor platform.

However, the difference between the original format and the target format includes the difference in the included fields, and if the target field is included in the original format of the original representation information, the target field is set to be invalid in the process of modifying the original representation information. The target field is a field included in the original format of the original representation information but not included in the target format of the target representation information.

For example, if the original VMCS contains the Guest_cs_base field, but the target VMCS field does not contain the Guest_cs_base, the target Agent can set the content of the Guest_cs_base field in the original VMCS to be invalid during the modification process, which is not limited.

Step 208, the target hypervisor platform rebuilds the VM according to the target description information.

After that, the target agent can rebuild the VM in the target hypervisor platform according to the target description information. Optionally, the target agent can start the VM on the target hypervisor platform, and load the target description information for the running access of the VM.

Optionally, after the target hypervisor platform successfully rebuilds the VM, the target hypervisor platform may send migration success information to the original hypervisor platform. Optionally, the target hypervisor platform may send the migration success information to the original agent in the original hypervisor platform through the target agent.

To sum up, the VM migration method between heterogeneous hypervisor platforms provided by this embodiment obtains the original description information of the original hypervisor platform during the process of running the VM in the original hypervisor platform, and the original description information includes the VM in the original hypervisor platform. The original representation information in the memory of the original hypervisor platform; send the original description information to the target hypervisor platform, so that the target hypervisor platform modifies the received original description information according to the target format information, obtains the target description information, and reconstructs the VM according to the target description information; wherein , the target format information includes the target format of the VM in the memory of the target hypervisor platform; it solves the problem that the VM needs to be offline, that is, the business needs to be interrupted when the VM is migrated between heterogeneous hypervisor platforms in the prior art; The VM can be kept online to avoid service interruption, and thus can achieve smooth evolution between different platforms.

At the same time, the online migration of VMs between heterogeneous platforms avoids the need to overthrow the existing virtualization platforms when introducing a new virtualization platform due to the different formats of VM representation information in different platforms in the prior art. Design and rebuild issues in the ability to build new platforms.

The steps on the original hypervisor platform side in the above embodiment can be implemented independently as the VM migration method on the original hypervisor platform side, and the steps on the target hypervisor platform side can be implemented independently as the VM migration method on the target hypervisor platform side, which will not be repeated here.

Please refer to FIG. 4 , which shows a schematic structural diagram of a VM migration apparatus between heterogeneous hypervisor platforms provided by an embodiment of the present invention. In this embodiment, the apparatus is used in an original hypervisor platform as an example. As shown in FIG. 4 , the VM migration apparatus between heterogeneous hypervisor platforms may include: an obtaining unit 410 and a sending unit 420 .

The obtaining unit 410 is configured to perform the above step 201 .

The sending unit 420 is configured to perform the above step 202.

To sum up, the apparatus for migrating VMs between heterogeneous hypervisor platforms provided in this embodiment obtains the original description information of the original hypervisor platform during the process of running the VM in the original hypervisor platform, and the original description information includes the VM in the original hypervisor platform. The original representation information in the memory of the original hypervisor platform; send the original description information to the target hypervisor platform, so that the target hypervisor platform modifies the received original description information according to the target format information, obtains the target description information, and reconstructs the VM according to the target description information; wherein , the target format information includes the target format of the VM in the memory of the target hypervisor platform; it solves the problem that the VM needs to be offline, that is, the business needs to be interrupted when the VM is migrated between heterogeneous hypervisor platforms in the prior art; The VM can be kept online to avoid service interruption, and thus can achieve smooth evolution between different platforms.

Please refer to FIG. 5 , which shows a schematic structural diagram of a VM migration apparatus between heterogeneous hypervisor platforms provided by an embodiment of the present invention. In this embodiment, the apparatus is used in a target hypervisor platform as an example. As shown in FIG. 5 , the VM migration apparatus between heterogeneous hypervisor platforms may include: a receiving unit 510 , an acquiring unit 520 , a modifying unit 530 and a reconstructing unit 540 .

The receiving unit 510 is configured to perform the above step 203 .

The obtaining unit 520 is configured to perform the above step 204 .

The modification unit 530 is configured to perform the above steps 205 to 207 .

The reconstruction unit 540 is configured to perform the above step 208 .

In summary, the VM migration device between heterogeneous hypervisor platforms provided in this embodiment modifies the received original description information according to the target format information by receiving the original description information of the VM sent by the original hypervisor platform, and obtains the target description information , reconstruct the VM according to the target description information; wherein, the original description information includes the original representation information of the VM in the memory of the original hypervisor platform, and the target format information includes the target format of the VM in the memory of the target hypervisor platform; When migrating VMs between heterogeneous hypervisor platforms, the VM needs to be offline, that is, the business needs to be interrupted; the VM can be kept online to avoid business interruption during the VM migration process, and smooth evolution can be achieved between different platforms.

An embodiment of the present invention also provides a VM migration system between heterogeneous hypervisor platforms, where the system includes an original hypervisor platform and a target hypervisor platform. in,

The original hypervisor platform includes the VM migration device between heterogeneous hypervisor platforms shown in FIG. 4;

The target hypervisor platform includes the VM migration device between heterogeneous hypervisor platforms shown in FIG. 5 .

To sum up, the VM migration method between heterogeneous hypervisor platforms provided by this embodiment obtains the original description information of the original hypervisor platform during the process of running the VM in the original hypervisor platform, and the original description information includes the VM in the original hypervisor platform. The original representation information in the memory of the original hypervisor platform; send the original description information to the target hypervisor platform, so that the target hypervisor platform modifies the received original description information according to the target format information, obtains the target description information, and reconstructs the VM according to the target description information; wherein , the target format information includes the target format of the VM in the memory of the target hypervisor platform; it solves the problem that the VM needs to be offline, that is, the business needs to be interrupted when the VM is migrated between heterogeneous hypervisor platforms in the prior art; The VM can be kept online to avoid service interruption, and thus can achieve smooth evolution between different platforms.

At the same time, the online migration of VMs between heterogeneous platforms avoids the need to overthrow existing virtualization platforms when introducing a new virtualization platform due to the different formats of VM representation information in different platforms in the prior art. Design and rebuild issues in the ability to build new platforms.

It should be noted that, for the sake of simple description, the foregoing method embodiments are all expressed as a series of action combinations, but those skilled in the art should know that the present invention is not limited by the described action sequence. As in accordance with the present invention, certain steps may be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present invention.

While the invention has been described herein in conjunction with various embodiments, those skilled in the art will appreciate, from reviewing the drawings, the disclosure, and the appended claims, in practicing the claimed invention, and Other variations of the disclosed embodiments are implemented. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude a plurality. A single processor or other unit may fulfill the functions of several items recited in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that these measures cannot be combined to advantage.

As will be appreciated by those skilled in the art, embodiments of the present invention may be provided as a method, a server (apparatus), or a computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein. The computer program is stored/distributed in a suitable medium, provided with or as part of other hardware, or may take other forms of distribution, such as over the Internet or other wired or wireless telecommunication systems.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, servers (apparatus) and computer program products of embodiments of the invention. It will be understood that each process and/or block in the flowchart illustrations and/or block diagrams, and combinations of processes and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to the processor of a general purpose computer, special purpose computer, embedded processor or other programmable data processing device to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing device produce Means for implementing the functions specified in a flow or flow of a flowchart and/or a block or blocks of a block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory result in an article of manufacture comprising instruction means, the instructions The apparatus implements the functions specified in the flow or flow of the flowcharts and/or the block or blocks of the block diagrams.

These computer program instructions can also be loaded on a computer or other programmable data processing device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process such that The instructions provide steps for implementing the functions specified in the flow or blocks of the flowcharts and/or the block or blocks of the block diagrams.

Although the invention has been described in conjunction with specific features and embodiments thereof, it will be apparent that various modifications and combinations can be made therein without departing from the spirit and scope of the invention. Accordingly, this specification and drawings are merely illustrative of the invention as defined by the appended claims, and are deemed to cover any and all modifications, variations, combinations or equivalents within the scope of the invention. It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the spirit and scope of the invention. Thus, provided that these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include these modifications and variations.

Claims (18)

1. A virtual machine migration method between heterogeneous virtual machine monitor platforms, wherein the method comprises: The original hypervisor platform obtains the original description information of the running virtual machine VM, the original description information includes the original extensible markup language XML file of the VM in the original hypervisor platform, the original image image file, the original hypervisor platform The original representation information used to represent the VM in the memory; The original hypervisor platform sends the original description information to the target hypervisor platform, the target format used to represent the representation information of the VM in the memory of the target hypervisor platform and the representation information used to represent the VM in the memory of the original hypervisor platform the original format is different; The target hypervisor platform receives the original description information sent by the original hypervisor platform; The target hypervisor platform obtains target format information, and the target format information includes the file format of the XML file corresponding to the target hypervisor platform, the file format of the image file, and the target format; The target hypervisor platform modifies the original description information according to the target format information to obtain the target description information of the VM in the target hypervisor platform; The target hypervisor platform rebuilds the VM according to the target description information. 2. The method according to claim 1, wherein the target hypervisor platform modifies the original description information according to the target format information to obtain the target description information of the VM in the target hypervisor platform, comprising: : The target hypervisor platform converts the original representation information according to the target format, and obtains target representation information; the target description information includes the target representation information. 3. The method according to claim 2, wherein the target hypervisor platform converts the original representation information according to the target format, and obtains the target representation information, comprising: The target hypervisor platform generates a target data structure according to the target format; The target hypervisor platform writes the original representation information into the target data structure according to the difference between the original format and the target format to obtain the target representation information. 4. The method according to claim 2 or 3, characterized in that, If the original format of the original representation information includes a target field, the target field is set to be invalid in the process of modifying the original representation information, and the target field is included in the original format of the original representation information but The target represents fields not included in the target format of the information. 5. The method according to claim 1, wherein the original hypervisor platform obtains the original description information of the running virtual machine VM, comprising: The original hypervisor platform obtains the original format of the VM in the memory of the original hypervisor platform; The original Hypervisor platform performs binary analysis on the information of the VM in the memory according to the original format and the virtual machine communication support VMCS technology, and obtains an analysis result; The original hypervisor platform uses the analysis result as the original representation information. 6. The method according to claim 5, wherein the original hypervisor platform obtains the original description information of the running virtual machine VM, further comprising: The original hypervisor platform acquires the original extensible markup language XML file and the original image image file of the VM in the original hypervisor platform, and the original description information further includes the original XML file and the original image file. 7. The method according to claim 1, wherein the target hypervisor platform modifies the original description information according to the target format information to obtain the target description information of the VM in the target hypervisor platform, and further include: The target hypervisor platform obtains the target XML file corresponding to the target hypervisor platform according to the file format of the XML file in the target format information and the original XML file; The target hypervisor platform obtains the target image file corresponding to the target hypervisor platform according to the file format of the image file in the target format information and the original image file; the target description information also includes the target XML file and the target image file. 8. A virtual machine migration method between heterogeneous virtual machine monitor platforms, characterized in that, used in the original hypervisor platform, the method comprising: Obtain the original description information of the running virtual machine VM, where the original description information includes the original Extensible Markup Language XML file of the VM in the original Hypervisor platform, the original image image file, and the original Hypervisor of the VM in the original Hypervisor platform. raw representation information in the platform's memory; Send the original description information to the target hypervisor platform; the target hypervisor platform modifies the original description information according to the obtained target format information, and obtains the target description information of the VM in the target hypervisor platform, according to the target The description information reconstructs the VM; the target format information includes the file format of the XML file corresponding to the target hypervisor platform, the file format of the image file, and the target used to represent the representation information of the VM in the memory of the target hypervisor platform The target format is different from the original format used to represent the representation information of the VM in the memory of the original hypervisor platform. 9. A virtual machine migration method between heterogeneous virtual machine monitor platforms, characterized in that, used in a target hypervisor platform, the method comprising: Receive the original description information of the running virtual machine VM sent by the original hypervisor platform; the original description information includes the original extensible markup language XML file of the VM in the original hypervisor platform, the original image image file, the VM The original representation information in the memory of the original hypervisor platform; the target format used to represent the representation information of the VM in the memory of the target hypervisor platform is the same as the original representation information used to represent the representation information of the VM in the memory of the original hypervisor platform different formats; Obtain target format information, where the target format information includes the file format of the XML file corresponding to the target hypervisor platform, the file format of the image file, and the target format; Modify the original description information according to the target format information to obtain the target description information of the VM in the target hypervisor platform; Rebuild the VM according to the target description information. 10. The method according to claim 9, wherein the modifying the original description information according to the target format information to obtain the target description information of the VM in the target hypervisor platform, comprising: Convert the original representation information according to the target format to obtain target representation information; the target description information includes the target representation information. 11. The method according to claim 10, wherein the converting the original representation information according to the target format and obtaining the target representation information comprises: generating a target data structure according to the target format; The original representation information is written into the target data structure according to the difference between the original format and the target format to obtain the target representation information. 12. The method according to claim 10 or 11, characterized in that, If the original format of the original representation information includes a target field, the target field is set to be invalid in the process of modifying the original representation information, and the target field is included in the original format of the original representation information but The target represents fields not included in the target format of the information. 13. An apparatus for migrating virtual machines between heterogeneous hypervisor platforms, characterized in that it is used in an original hypervisor platform, and the apparatus comprises: The obtaining unit is used to obtain the original description information of the running virtual machine VM, the original description information includes the original extensible markup language XML file, the original image image file of the VM in the original Hypervisor platform, the original image file of the VM the original representation information in the memory of the original hypervisor platform; a sending unit, configured to send the original description information obtained by the obtaining unit to the target hypervisor platform; the target hypervisor platform modifies the original description information according to the obtained target format information, and obtains the VM in the target hypervisor platform The target description information in the hypervisor platform, and the VM is reconstructed according to the target description information; the target format information includes the file format of the XML file corresponding to the target hypervisor platform, the file format of the image file, and the target hypervisor platform. The target format used to represent the representation information of the VM in the memory of the original hypervisor platform is different from the original format used to represent the representation information of the VM in the memory of the original hypervisor platform. 14. An apparatus for migrating virtual machines between heterogeneous hypervisor platforms, characterized in that, for use in a target hypervisor platform, the apparatus comprises: a receiving unit, configured to receive the original description information of the running virtual machine VM sent by the original hypervisor platform; the original description information includes the original extensible markup language XML file, original image image of the VM in the original hypervisor platform file, the original representation information of the VM in the memory of the original Hypervisor platform; the target format used to represent the representation information of the VM in the memory of the target Hypervisor platform and the memory of the original Hypervisor platform used to represent the VM The original format of the representation information is different; an acquisition unit, configured to acquire target format information, where the target format information includes the file format of the XML file corresponding to the target hypervisor platform, the file format of the image file, and the target format; a modifying unit, configured to modify the original description information according to the target format information obtained by the obtaining unit to obtain target description information of the VM in the target hypervisor platform; A reconstruction unit, configured to reconstruct the VM according to the target description information modified by the modification unit. 15. The apparatus of claim 14, wherein The modification unit is further configured to convert the original representation information according to the target format, and obtain target representation information; the target description information includes the target representation information. 16. The apparatus according to claim 15, wherein the modifying unit is further configured to: generating a target data structure according to the target format; The original representation information is written into the target data structure according to the difference between the original format and the target format to obtain the target representation information. 17. The device according to claim 15 or 16, characterized in that, The modification unit is further configured to, when the original format of the original representation information includes a target field, set the target field to be invalid in the process of modifying the original representation information, and the target field is the original Fields included in the original format of the representation information but not included in the target format of the target representation information. 18. A virtual machine migration system between heterogeneous virtual machine monitor platforms, wherein the system comprises an original hypervisor platform and a target hypervisor platform; The original hypervisor platform comprises the virtual machine migration device between heterogeneous hypervisor platforms as claimed in claim 13; The target hypervisor platform includes the virtual machine migration device between heterogeneous hypervisor platforms according to any one of claims 14 to 17.

Images