VMware Workstation Cloning virtual machine cannot be solved online

Description of the phenomenon:

Recently installed the virtual machine system is CentOS 6.8, for later use to facilitate the cloning or replication of the virtual machine. When using a cloned virtual machine, it was found that the NIC in the base system eth0 to the new system.

System Version Information

650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M00/8C/09/wKioL1hgj5yCxbtDAAAM0hO5ZpY287.png "title=" System version " alt= "Wkiol1hgj5ycxbtdaaam0ho5zpy287.png"/>

Using ifconfig-a will find only lo and eth1.

650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M01/8C/09/wKioL1hgh7LQBKeJAAAi8SDDA3U901.png "title=" Boot ifconfig-a.png "alt=" Wkiol1hgh7lqbkejaaai8sdda3u901.png "/>

Because the basic system network-related configuration is based on eth0, eth1 No network-related configuration, at this time to normal the network in the virtual machine, only add eth1 network configuration, so every time to modify the network card configuration in the long Linux system testing is not convenient. Further, if you continue to clone or replicate a new virtual machine based on this cloned virtual machine, the network card's identity is automatically added 1 each time (the second clone becomes eth2), and DMESG shows that the kernel only recognizes the NIC Eth0.

Cause Analysis:

Many Linux distribution use Udev to dynamically manage device files and name them based on the device's information. For example, in Debian Etch, Udev identifies the network card during system boot and records the MAC address and network card name in Udev's rules script. VMware automatically generates the MAC address of the virtual machine. In this way, because the virtual machine of the basic system has recorded that the virtual machine's network card MAC address corresponds to the NIC Eth0, in the cloned virtual machine due to the MAC address changes, Udev will automatically correspond to the Mac to the NIC Eth1. And so on, Udev will record all identified Mac and network card name relationship, so each clone network card name will automatically add 1, but in fact, kernel only to recognize a network card, the network configuration associated with the NIC name has not changed any.

Solution:

1. empty or delete the 70-persistent-net.rules file under the/ETC/UDEV/RULES.D path under the system

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/8C/0D/wKiom1hgiIzwvrqaAAAsaVk0T6M900.png "title=" Workaround the first step "alt=" Wkiom1hgiizwvrqaaaasavk0t6m900.png "/>

2. Remove the UUID and HWADDR address from the Ifcfg-eth0 (eth0 network profile) under the/etc/sysconfig/network-scripts path under System

before modification

650) this.width=650; "src=" Http://s5.51cto.com/wyfs02/M00/8C/09/wKioL1hgjmKgRjKFAAAR-Qf5xGY943.png "title=" The second step _ Modify before "alt=" Wkiol1hgjmkgrjkfaaar-qf5xgy943.png "/>

after modifying

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/8C/09/wKioL1hgjnjzyVSeAAALvfAAvxw525.png "title=" The second step _ Modified "alt=" Wkiol1hgjnjzyvseaaalvfaavxw525.png "/>

3. System restart (the following three commands to select any one of them)

1. Reboot

2. Shutdown-r Now

3. Init 6

4. After the reboot is complete, we can check the network card posture through IFCONFIG-A.

650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M01/8C/09/wKioL1hgj7XBOjgLAAAuCQu8JyY548.png "title=" after reboot " alt= "Wkiol1hgj7xbojglaaaucqu8jyy548.png"/>

At this point we find that the eth0 Nic has started normally.

To demand-driven technology, the technology itself does not have a better point, only the division of business.

This article is from the "Sea" blog, be sure to keep this source http://lisea.blog.51cto.com/5491873/1886136

VMware Workstation Cloning virtual machine cannot be solved online