CN107678831A - It is a kind of to realize the V2V methods migrated between virtual platform - Google Patents

Abstract

The invention discloses a kind of V2V methods realized and migrated between virtual platform, belong to cloud computing administrative skill field, the technical problem to be solved in the present invention is unable to flexible conversion and does not support mutually to migrate between the virtual machine of each manufacturer for the virtual machine of each manufacturer, the technical scheme used for：This method is by V2V Tool integrations in unified management node, and multinomial selection is provided when user, which clicks on, to be migrated, and calls different V2V instruments by the selection of user, realizes the migration operation of virtual machine between kinds of platform；Comprise the following steps that：（1）, build environment, dispose management node and calculate node；（2）, qemu img programs are installed in calculate node, in management node deployment call qemu img programs；（3）, deployment storage and network, create virtual machine in different calculate nodes；（4）, complete using cold migrating the virtual machines or thermophoresis virtual machine the migration of virtual machine between platform.

Description

A V2V method for migrating across virtualization platforms

technical field

The invention relates to the technical field of cloud computing management, in particular to a V2V method for realizing migration between virtualization platforms.

Background technique

V2v migrates systems and data between virtual machines and handles host differences and virtual hardware. The source virtual machine system and destination virtual machine system type in v2v can be the same or different, such as migration between VMware and KVM or within each. V2v migration methods include offline migration, online migration and memory migration. Before offline migration, the virtual machine needs to be suspended, and the virtual machine image and status are copied to the destination host at the same time. Offline migration has a certain period of service unavailability, but it is simple and easy to implement, and is suitable for occasions that do not require high service availability. Offline migration is an effective way to solve the migration between different types of virtual machines. For example, the open source migration tool virt-v2v uses this method to migrate VMware and KVM and other types of virtual machines to the KVM platform and load the KVM driver to run successfully. Online migration can ensure the normal operation of the virtual machine during the migration process. The source host provides services at the initial stage of migration. When the destination host has the necessary resources to run the system, it takes over the services. The switching process is extremely short, and the migration process is transparent to users. It is suitable for service Occasions with high availability requirements. Memory migration can use the pre-copy strategy to send the memory data of the source host virtual machine to the destination host virtual machine through a cycle. The pre-copy strategy sends the memory data of the source host virtual machine to the destination host virtual machine through a cycle. In the downtime copy phase, the source host hangs up and no longer updates the memory. The pre-copy mechanism greatly reduces the amount of memory transfer during the downtime period, and the downtime is greatly reduced.

The virt-v2v tool developed by Red Hat. It is a script written in perl language, which can automatically copy virtual machines created on Xen, KVM and VMware ESX to virt-v2v hosts, and automatically change the configuration so that they can be managed by libvirt. Currently, virt-v2v supports static migration of the following virtual machines: RHEL4, RHEL5, RHEL6, Windows XP, Windows Vista, Windows 7, Windows Server 2003 and Windows Server 2008.

The Virt-v2v tool is deployed on a KVM host and uses to create a local directory to store the migrated virtual machine image. In addition, in order to realize the automatic migration of the virtual machine, first set the virt-v2v.conf file in advance and set some virt-v2v Migration rules, including the mapping of the network interface after migration, migration method, storage location, output format, etc. These rules can also be entered as command line parameters, such as - - network, -o, -os, -of, etc. Create a .netrc file for automatic login to the VMware ESX server. And set the 0600 permission, the file content is in the format of machinesx.example.com login root password xxxxxx.

Then use the virt-v2v command to migrate.

Migrate from Xen to KVM: virt-v2v-ic xen+ssh://root@xen0.demo.com -os pool -bbrnamevm-name.

Migrating from VMware to KVM: virt-v2v-ic esx://esx.demo.com/ -os pool --bridegebramevm-name.

The disadvantages of the existing technology are: (1) the virtual machines of various manufacturers cannot be flexibly converted; (2) the mutual migration between virtual machines of various manufacturers is not supported.

Patent No. CN 106406979A discloses a method for migrating a XenServer platform virtual machine to a KVM virtualization platform. The method of the present invention comprises the following steps: enter the host computer where the XenServer virtual machine is located; search for the corresponding vdi file of the virtual machine by a script command, export the vdi file to a local file by the DD command; copy the local file to the host computer where the KVM platform is located; The command converts the exported file into a qcow2 file, and creates a KVM platform virtual machine through the qcow2 file. However, this technical solution cannot solve the problems that the virtual machines of various vendors cannot be flexibly converted and the mutual migration between virtual machines of various vendors is not supported.

Contents of the invention

The technical task of the present invention is to provide a V2V method for realizing cross-virtualization platform migration, so as to solve the problems that virtual machines of various manufacturers cannot be flexibly converted and do not support mutual migration between virtual machines of various manufacturers.

The technical task of the present invention is realized in the following manner, a V2V method for realizing cross-virtualization platform migration, the method is to integrate V2V tools on a unified management node, and give multiple choices when the user clicks migration, Different V2V tools are invoked through the user's selection to realize the migration operation of virtual machines between various platforms; the specific steps are as follows:

(1) Set up the environment and deploy management nodes and computing nodes: the management nodes run services, and the computing nodes run virtual machines;

(2) Install the qemu-img program on the computing node to facilitate the conversion of the virtual machine on the computing node, deploy and call the qemu-img program on the management node;

(3) Deploy storage and network, create virtual machines on different computing nodes, choose RAW format or QCOW2 for disk, and choose thin provisioning for VMware;

(4) Use cold migration virtual machine or hot migration virtual machine to complete the migration of virtual machines between platforms.

Preferably, the multiple choices given by the user when clicking migration include migrating to VMware platform or migrating to KVM platform or migrating to Xen platform.

Preferably, the computing nodes in the step (1) are installed with ESXi of VMware or XenServer of Xen or Hans of Inspur based on KVM.

As preferably, the steps of the cold migration in the step (4) are as follows:

①. Shut down the virtual machine;

②. Click Migrate to select the computing node;

③. The management node invokes the qemu-img program to convert it into ova format for export;

④. Import the exported qemu-img program in ova format to the destination host.

Preferably, the steps of thermal migration in the step (4) are as follows:

①. Issue the migration command and shut down the virtual machine;

②. Convert the qemu-img program to the ova file format;

③. Import the exported qemu-img program in ova format to the destination host;

④. After the migration is successful, call the self-start command to start the virtual machine automatically.

Compared with the prior art, the V2V method for realizing cross-virtualization platform migration of the present invention has the following advantages:

(1), the present invention selects a V2V tool that is easy to use, stable and compatible, and integrates it on a unified management node. When the user clicks on migration, multiple choices are given, such as VMware's virtual machine migration, which pops up and is available The options are: migrate to the VMware platform; migrate to the KVM platform; migrate to the Xen platform, and call different v2v tools through the user's choice to realize the migration of virtual machines between various platforms;

(2) Unify V2V tools to realize cross-platform migration of virtual machines;

(3) Simplify system management and save management, maintenance and upgrade costs for users;

(4) Improve system load balance;

(5) Help users successfully complete the switching of virtualization platforms.

detailed description

A V2V method for realizing cross-virtualization platform migration of the present invention will be described in detail below with reference to specific embodiments.

Example:

The V2V method of the present invention realizes the migration between virtualization platforms. The method is to integrate the V2V tool on a unified management node. The KVM platform may be migrated to the Xen platform; different V2V tools are invoked through the user's choice to realize the migration operation of virtual machines between various platforms; the specific steps are as follows:

(1) Build the environment, deploy management nodes and computing nodes: management nodes run services, computing nodes run virtual machines; computing nodes install VMware’s ESXi or Xen’s XenServer or Inspur’s KVM-based Hans.

(2) Install the qemu-img program on the computing node to facilitate the conversion of the virtual machine on the computing node, deploy and call the qemu-img program on the management node;

(3) Deploy storage and network, create virtual machines on different computing nodes, choose RAW format or QCOW2 for disk, and choose thin provisioning for VMware;

(4) Use cold migration virtual machine or hot migration virtual machine to complete the migration of virtual machines between platforms.

The steps for cold migration are as follows:

①. Shut down the virtual machine;

②. Click Migrate to select the computing node;

③. The management node invokes the qemu-img program to convert it into ova format for export;

④. Import the exported qemu-img program in ova format to the destination host.

The steps of thermal migration in step (4) are as follows:

①. Issue the migration command and shut down the virtual machine;

②. Convert the qemu-img program to the ova file format;

③. Import the exported qemu-img program in ova format to the destination host;

④. After the migration is successful, call the self-start command to start the virtual machine automatically.

Deploy and install a unified management node, then install KVM's Node host, VMware's EXSi, and Xen's XenServer host, and configure their respective storage and network, create several virtual machines on each host, and install the operating system for them and driver software. If the cross-platform migration of the virtual machine needs to be shut down, the next operation is to convert the image file format of the virtual machine, reload the network interface and other related operations. After the migration is completed, start the virtual machine to check whether it can run normally .

The present invention relates to the technical field of virtual machine migration on a virtualization platform. The virtual machine migration technology refers to the process of migrating a virtual machine from one host or storage location to another host or storage location, mainly divided into physical machine migration and virtual machine migration. machine (P2V), virtual machine to virtual machine (V2V) and virtual machine to physical machine (V2P). Currently popular virtualization tools such as VMware, Xen, and KVM provide their own migration components, such as VMware's Converter, Xen's Xen-converter, and KVM's virt-v2v, etc. Migrating to tools on its own platform, this patent intends to integrate these v2v tools into a management platform, manage virtual and hardware resources of multiple virtualization platforms in a unified manner, and realize the migration of virtual machines between different platforms. So as to achieve the purpose of simplifying system maintenance and management, improving system load balance, enhancing system fault tolerance and optimizing system power management, and can save management funds, maintenance costs and upgrade costs for users. Various other corresponding changes and modifications can be made according to the technical concept of the present invention, and all these changes and modifications should belong to the protection scope of the claims of the present invention.

Through the above specific implementation manners, those skilled in the technical field can easily realize the present invention. However, it should be understood that the present invention is not limited to the specific embodiments described above. On the basis of the disclosed embodiments, those skilled in the art can arbitrarily combine different technical features to achieve different technical solutions.

Except for the technical features described in the instructions, all are known technologies by those skilled in the art.

Claims (5)

1. A V2V method for migrating across virtualization platforms, characterized in that the method integrates V2V tools on a unified management node, and when the user clicks on migration, multiple choices are given, and the user's selection is used to call Different V2V tools realize the migration operation of virtual machines between various platforms; the specific steps are as follows: (1) Set up the environment and deploy management nodes and computing nodes: the management nodes run services, and the computing nodes run virtual machines; (2) Install the qemu-img program on the computing node to facilitate the conversion of the virtual machine on the computing node, deploy and call the qemu-img program on the management node; (3) Deploy storage and network, create virtual machines on different computing nodes, choose RAW format or QCOW2 for disk, and choose thin provisioning for VMware; (4) Use cold migration virtual machine or hot migration virtual machine to complete the migration of virtual machines between platforms. 2. The V2V method for realizing migration across virtualization platforms according to claim 1, wherein the multiple choices given when the user clicks migration include migrating to VMware platform or migrating to KVM platform or migrating to Xen platform. 3. The V2V method for realizing cross-virtualization platform migration according to claim 1, characterized in that the computing nodes in the step (1) are installed with ESXi of VMware or XenServer of Xen or Hans of Inspur based on KVM. 4. The V2V method for implementing cross-virtualization platform migration according to claim 1, characterized in that the cold migration in the step (4) is as follows: ①. Shut down the virtual machine; ②. Click Migrate to select the computing node; ③. The management node invokes the qemu-img program to convert it into ova format for export; ④. Import the exported qemu-img program in ova format to the destination host. 5. The V2V method for implementing cross-virtualization platform migration according to claim 1, characterized in that the steps of hot migration in the step (4) are as follows: ①. Issue the migration command and shut down the virtual machine; ②. Convert the qemu-img program to the ova file format; ③. Import the exported qemu-img program in ova format to the destination host; ④. After the migration is successful, call the self-start command to start the virtual machine automatically.