homemade clone machine

Cloning virtual machines on VMware ESXiTranslate from http://www.dedoimedo.com/computers/vmware-esxi-clone-machine.html, omit before and after explanation.Cloning virtual machines in VMware ESXiThis demonstration was done using the VMware Infrastructure Client on Windows, so the Linux users were invited, but the idea was the same.Step 1: Start the VMware Infrastructure ClientIf you use ESXi, you will find that it is different from the server version b

.jpg "/>Click " Create " start cloning a virtual machine650) this.width=650; "title=" 10.png "style=" Float:none; "src=" http://s3.51cto.com/wyfs02/M00/6B/5B/ Wkiol1uryg-jxnoxaagrt4f4o6a074.jpg "alt=" Wkiol1uryg-jxnoxaagrt4f4o6a074.jpg "/>View Job Status650) this.width=650; "title=" 11.png "style=" Float:none; "src=" http://s3.51cto.com/wyfs02/M00/6B/5F/ Wkiom1urymcg8oddaaj8kuf7xqu609.jpg "alt=" Wkiom1urymcg8oddaaj8kuf7xqu609.jpg "/>Cloning complete650) this.width=650; "title=" 12.png "style=" F

-eth0 configuration file, Remove or modify the previous line of MAC addresses in the Ifcfg-eth0 configuration file. In addition, the cloned server's IP setting is static IP, either modified to a different IP address or set to dynamic IP, restart the network card service 2. Find/etc/udev/rules.d/70-persistent-net.rules Delete, Modify Ifcfg-eth0 Delete or note the configuration of MAC address, restart the machine, the system will automatically generat

After cloning, the VMware virtual machine discovers that the original eth0 of the cloned host will be gone, instead there will be a new Mac Nic Eth1. This article solves how to reasonably change the NIC to eth0. Ifconfig eth1 determine the MAC address of the new network card.Nmcli con determine the UUID of the new NIC 2Vim/etc/udev/rules.d/70-persistent-net.rulesDelete the relevant information of the original eth0 and change the name of Eth1 to

After the virtual machine clone is started using Ifconfig, no IP address is found, only the loopback address is 127.0.0.1,The MAC address and host name are the same as the source host (the source host is manually configured IP).Any execution of the following commands is useless anyway:/etc/init.d/network restartIfup eth0Workaround:1. Edit the eth0 configuration file: Vi/etc/sysconfig/network-scripts/ifcfg-e

Hyper-v vm differential disk clone System 1. First remove the template Sid value. Here we use 2003 as an example to copy the two files to the desktop or C drive on the 2003 installation disk. 650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M01/46/CE/wKiom1P0r-bR9pw0AAI1hxImM1s875.jpg "Title =" 1.png" alt = "wKiom1P0r-bR9pw0AAI1hxImM1s875.jpg"/> 2. Execute the sysprep.exe file, 650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M00/4

Two steps: First step export xml:[[emailprotected] ~]# virsh dumpxml centos02 >12c.xml Second Step disk file [[emailprotected] virhost]# CP Centos02.img 12c.img Look at the differences between the two files: [[emailprotected] ~]# diff/etc/libvirt/qemu/centos02.xml ~/12c.xml 1,10c1,3[[email protected] ~]# Virsh define 12c.xml Domain 12c defined from 12c.xml[email protected] ~]# Virsh start 12cDomain 12c Started[[email protected] ~]# virsh list Id Name State ----------

=192.168.1.0 Network address of the NICOnboot=yes If this network interface is set when the system starts, when set to Yes , the device is activated when the system starts. The default setting is YesAs for the back Type and UUID This will not be the tube, the types of the network cardEth0 nic file modified:# Cat/etc/sysconfig/network-scripts/ifcfg-eth0# Vim/etc/sysconfig/network-scripts/ifcfg-eth0Device=eth0Type=ethernetOnboot=yesNm_controlled=yesBootproto=noneipaddr=192.168.44.131netmask=255.25

=" F6f4ea2d8aea85118e2aa7a3c1c00a24.png-wh_ "/>Then, hit enter.650) this.width=650; "title=" 10.png "src=" https://s1.51cto.com/oss/201710/20/ Cc50afa72c79f18afe15ecffe21fc0e3.png-wh_500x0-wm_3-wmp_4-s_2412810302.png "alt=" Cc50afa72c79f18afe15ecffe21fc0e3.png-wh_ "/>Then, hit enter.650) this.width=650; "title=" 11.png "src=" https://s5.51cto.com/oss/201710/20/ 23a7ef44a1beeb283e6ecb59cde79ab0.png-wh_500x0-wm_3-wmp_4-s_1759960928.png "alt=" 23a7ef44a1beeb283e6ecb59cde79ab0.png-wh_ "/>I'm here, t

/usr/lib/systemd/system/runlevel5.target-Graphical.targetlrwxrwxrwx. 1 root root 2017/usr/lib/systemd/system/runlevel6.target-Reboot.targetDivided into 6 levels;When restarting, note:Loading the optical drive at startupRestart after rebooting into BIOS setupThere are 4 ways to choose,This is another change to the root password, using the form of a disc;If you change the wrong file, you can enter the rescue mode, the wrong file is changed correctly;1.15 Cloning a virtual machineCloning of VMSShut

When you do the experiment, you may need more than one virtual host, if you have to install from scratch is certainly unreasonable. There are two ways to do this: the first is to copy a virtual host directly into the folder and then import it into VMware.650) this.width=650; "Src=" Http://s2.51cto.com/wyfs02/M00/84/53/wKiom1eNgtbzFlrUAAAlyeF2czk359.png-wh_500x0-wm_3 -wmp_4-s_1982224013.png "title=" () 3@w]7nwjvgdo3c]980~h0.png "alt=" Wkiom1engtbzflruaaalyef2czk359.png-wh_50 "/>

Today, I installed the virtual machine to play, downloaded the Ubuntu server 14.04 image, and then made a template. After the template is deployed as a virtual machine, the network of the returned virtual machine is not available, here I choose the bridge mode, using ifconfig found no IP address, finally found a solution, and now recorded:Keep the last line, all

I. failure Phenomena:[Email protected] ~]# service network restart S Hutting down loopback insterface: [ ok] Bringing up loopback insterface: [OK]Bringing up interface Eth0:device eth0 does no seem to be present,delaying initialization. [FAILED]Workaround:[Email protected] ~]# Rm-rf/etc/udev/rules.d/70-persistent-net.rules[[email protected] ~] # Reboot .....------.[Email protected] ~]# service network restart S Hutting down loopback insterface: [ ok] B Ringing up loopback insterfac

First, the Linux virtual machine cloning, the boot system found that the network card could not start, and then ifup eth0 network card will prompt (Device eth0 does not seem to be present, delaying initialization.) failed.Second, the treatment method:Method One:1, [[email protected] ~]# Vim/etc/udev/rules.d/70-persistent-net.rules# This file is automatically generated by the/lib/udev/write_net_rules# program, run by the Persistent-net-generator.rules

The following three steps can be quickly resolvedFirst step: Modify or delete a file/etc/udev/rules.d/7 0-persistent-net.rules[Email protected] ~]# Mv/etc/udev/rules.d/70-persistent-net.rules/etc/udev/rules.d/70-persistent-net.rules.bakStep Two: Modify the NIC configuration file/etc/sysconfig/network-scripts/ifcfg-eth0Comment out the network card or Mac information.Device=eth0#HWADDR =00:50:56:aa:31:ecType=ethernet#UUID =8e8f1d18-f7fa-47a0-9430-07bfa8705120Onboot=yesNm_controlled=yesBootproto=s

After cloning is complete, there may be a conflict with the MAC address, go to KVM to remove the eth0 configuration in/etc/udev/rules.d/70-persistent-net.rules, then change eth1 to Eth0, and modify/etc/sysconfig/ Network-script/ifcfg-eth0 Mac, confirm that the MAC address in the two configuration files is the same.Reference:http://blog.51cto.com/freedyong/1361907Modify MAC address after KVM clone is complete under CentOS/vmware copy virtual