VMWare ESXi 5.0 Fast copy virtual machines

The free version of VMware ESXi is very powerful, but unfortunately its client vsphere clients do not provide the ability to clone virtual machines. In fact, its command-line tools already support cloning, and we can do this manually.

First, copy the virtual machine configuration file : Go to vsphere Client: On the Right tab on the left select host , select Summary --click on the memory entry and run Browse the data store create a folder for the new virtual machine in the Datastore browser and copy the . VMX file from the virtual machine folder you want to clone (can be renamed to a new name)

then, execute the clone with the command line: go to command line interface: can use putty and so on SSH remote, the premise is the host has the function of open ssh. To create a clone virtual machine disk file by using the command:

Vmkfstools-i/VMFS/VOLUMES/DATASTORE/BASEVM/BASEVM.VMDK/VMFS/VOLUMES/DATASTORE/NEWVM/NEWVM.VMDK This command will show the progress, If the file is large, the time will be longer.

This command is supported for cloning snapshots. If you are cloning a snapshot (Snapshot), the above BASEVM.VMDK will be replaced with the Snapshot file to be cloned, such as Basevm-000008.vmdk,vmkfstools will be the most dynamic generation of the merged new files.

reconfigure the new virtual machine in the Admin interface: go back to the Datastore browser interface, right click on the. vmx file, select Add to List , and join the new virtual machine to the management interface. Modify the configuration of the new virtual machine in vsphere: Delete the original hard disk because it is a disk file that points to the old virtual machine, then add a new hard disk and choose to use the existing disk file and select the one that you just created with the command line. Start a new virtual machine, complete.

At this point, you get an identical virtual machine. Note that this new virtual machine is exactly the same as the original virtual machine, including the contents of the hard disk, configuration, etc., so if you open an account at the same time there may be problems, such as IP, host name conflict.

The above content is reproduced from http://shao-fan.com/blog/vmware-esxi-clone.html

I found the following issues when cloning CentOS 5.7 (there is no problem with SQL SERVER 2008):

Open the cloned virtual machine and discover that there are two NICs eth0 and Eth0.bak. Ways to remove Eth0.bak:

/etc/sysconfig/networking/devices, remove Ifcfg-eth0.bak
/etc/sysconfig/networking/profiles/default, remove Ifcfg-eth0.bak
/etc/sysconfig/network-scripts/, remove Ifcfg-eth0.bak

Reconfigure the eth0, and modify the host name.

Original address: http://blog.csdn.net/tswisdom/article/details/7546896