VMware ESX Migration to KVM

Introduction to Migration:

As one of the pioneers and market leaders in system virtualization, VMware has a strong and easy-to-use virtualization product and is known and used by many people. However, the drawback is that their enterprise-class virtualization Products Esx/esxi Series license licensing fees are more expensive. Whether you're considering migrating from VMware to a KVM virtualization solution, from the point of view of KVM completely free or from a fully open source of KVM-based Linux kernels, this article may help.

Migrating from VMware to KVM, I chose to do this through the VIRT-V2V tool, and first we talk about what is VIRT-V2V?

The VIRT-V2V tool can be used to migrate a virtual client from some hypervisor (including KVM itself) to a KVM environment, requiring that the KVM in the destination host be managed by Libvirt or managed by Rhev. VIRT-V2V is a command-line tool developed by Redhat's engineer Matthew Booth, and it is also a fully open source project. In addition to Matthew himself, there are other developers who have contributed code to the project. The latest version of the VIRT-V2V development source code can be cloned through "Git clone git://git.fedorahosted.org/virt-v2v.git".

VIRT-V2V By default will use the semi-virtualized driver (Virtio) as far as possible by the converted virtual client. According to Redhat's official description of the VIRT-V2V tool, the VIRT-V2V tools in the RHEL 6.x system support migrating from KVM, Xen, VMware Esx to KVM (the latest version also supports VirtualBox conversions).

Migration of the VIRT-V2V tool is not a dynamic migration, it is necessary to shut down the client to be migrated on the host (Xen, VMware, etc.) before performing the migration, so it can actually be said that the VIRT-V2V implementation is always converted to the Xen, Virtual clients such as VMware are converted into KVM clients. In general, VIRT-V2V relies on libvirt, allowing Libvirt to provide a common adaptation layer for different virtual products, providing the necessary functionality for KVM conversions.

According to Redhat's official documentation, VIRT-V2V's executable program and its release in some Linux distributions. Can be installed directly using "Yum install VIRT-V2V".

The steps are as follows:

1. If VMware Tools is installed on the virtual machine, you must uninstall it first. Because KVM virtual machines do not support virtual drives inside VMware Tools.

2. Stop the VMS waiting to be migrated on VMware ESX because VIRT-V2V only supports static migrations.

3. Create a. netrc file for automatic login to the VMware ESX server. The VMware ESX server connection requires authorization, and the VIRT-V2V tool supports an authorized connection that uses a password when it connects to ESX, which reads the machine name, user name, password, and so on by default in the $home/.netrc file. This is similar to the FTP command. If the host system does not have this file, create it manually. and the. netrc file requires 600 permissions so that the VIRT-V2V tool can read it correctly. The format in this. netrc file is as follows:

Machine 192.168.1.114 Login Root password 123456

4. Use the VIRT-V2V command to migrate, such as the following command line

Virt-v2v-ic esx://192.168.1.114/?no_verify=1-os default--bridge br0 vm-nameesx://192.168.1.114 #表示连接到VMware esx server, will Command vm-name the client to migrate over. VMware ESX servers use HTTPS connectivity, and in the process of connecting to VMware ESX servers, you typically need to configure SSL certificates. Use the No_verify=1 to ignore SSL certificate checks. -os default #表示迁移过来后, the local storage pool where the image files are stored. --bridge bro #表示本地网桥的名称, used to establish a network connection to the client. Vm-name #表示在VMware的源宿主机中将要被迁移的客户机的名称.

5. After a successful migration, the virtual machine appears in the list of virtual machines managed by Virt-manager. Start the virtual machine with the Virt-manager tool.

6. Verify that the migrated virtual machine configuration and system are consistent with the previous migration.

note the details as follows

1. The machine to be migrated must be in the shutdown state.

2. The machine to be migrated cannot have a snapshot, the server state of the first snapshot when the servers are migrated by default.

3. The. netrc file must be 600 permissions.

4. How to view-os local storage pool?

Virt-manager--Edit-->connection details--> Storage Bar--left bottom corner "+" customizable location

650) this.width=650; "src=" Http://tshare365.com/ueditor/php/upload/image/20150329/1427617868710812.png "title=" Http://tshare365.com/archives/1190.html "alt=" http://tshare365.com/archives/1190.html "width=" 424 "height=" 205 " Border= "0" vspace= "0" style= "width:424px;height:205px;"/>

650) this.width=650; "src=" Http://tshare365.com/ueditor/php/upload/image/20150329/1427617675825661.png "title=" Http://tshare365.com/archives/1190.html "alt=" http://tshare365.com/archives/1190.html "width=" 424 "height=" 491 " Border= "0" vspace= "0" style= "width:424px;height:491px;"/>

5. How to check the local network card name?

Virt-manager---Edit-->connection details--> virtual network card bar (or network interface Bar)-->virbro (bro)

650) this.width=650; "src=" Http://tshare365.com/ueditor/php/upload/image/20150329/1427617868710812.png "title=" Http://tshare365.com/archives/1190.html "alt=" http://tshare365.com/archives/1190.html "width=" 424 "height=" 205 " Border= "0" vspace= "0" style= "width:424px;height:205px;"/>

650) this.width=650; "src=" Http://tshare365.com/ueditor/php/upload/image/20150329/1427617982447929.png "title=" Http://tshare365.com/archives/1190.html "alt=" http://tshare365.com/archives/1190.html "width=" 424 "height=" 479 " Border= "0" vspace= "0" style= "width:424px;height:479px;"/>

6. After the migration, the default virtual machine image format is raw, you can add-of qcow2 on migration and specify the virtual machine image format as Qcow2 on KVM.

description of issues encountered during migration

[Email protected] ~]# virt-v2v-ic esx://192.168.1.114/?no_verify=1-os default--bridge br0 pythonlibvirt error code:1, Message: Internal error Missing essential Config entry ' floppy0.filename '

The KVM virtual machine is not recognized due to the floppy disk being mounted on the server being migrated. Remove the floppy disk.

This article is from the "Start Dream" blog, please be sure to keep this source http://pangge.blog.51cto.com/6013757/1626190

VMware ESX Migration to KVM