Linux operating system, after using VMware clone function, leading to an error card, network connections are not encountered such a problem how to deal with? Xiao Bian gave you about the latter Linux virtual machine cloning errors card solutions, learning together under the bar.
Description of the problem
VMware clone virtual machine is a regular thing for the client is a virtual machine for direct cloning Winows can be used. For client will not start a network problem after Linux virtual machine cloning.
Use the command service network start will be given as follows:
device eth0 does not seem to be present
Vmware use of cloning feature, the original virtual machine configured with a MAC address different network cards for the newly created virtual machine. For such a CentOS Linux systems, run-time network card MAC address will be entered /etc/udev/rules.d/70-persistent-net.rules file. Such a good clone new system also saved the record.
When the new system starts, since vmware have to configure different MAC address, the system will start scanning hardware to the new network card MAC address as is eth1, and increases recorded in the aforementioned documents. At a time when the configuration file is / etc / sysconfig / network-scripts / ifcfg-eth0 in the record or the original MAC address, the MAC address of the new system does not exist, it can not be started.
In the new system, the rules of the old MAC record file corresponding to the eth0 line deleted, then the corresponding new MAC eth1 name to eth0. Then ifcfg-eth0 file to the value of HDADDR the new MAC address.
Such rules and ifcfg-eth0 to correspond to each other (the corresponding rules in the eth0 ifcfg-eth0 file names, rules in the mac correspond ifcfg-eth0 file for HDADDR) good. At this point you need to restart the system everything OK.
The above is, after the Linux virtual machine cloning errors card solution introduced, because the cloned MAC address does not exist, re-setting the MAC address will be able to solve this problem.