VMware cloning CentOS modifies Linux MAC address

Device eth0 does not seem to be present, delaying initialization

Failure background:
In VMware Workstation, a virtual machine that has completely cloned an existing CentOS is discovered and the NIC is not started after booting. Restart the Network service and find the error message "Device eth0 does not seem to be present, delaying initialization."

Causes of failure:
Because of the cloning of virtual machines, VMware just modified the name of the virtual machine and other information, and did not modify any information on the virtual hard disk, causing the network card after cloning the MAC address and the operating system recorded in the MAC address does not match, causing eth0 to start up. The operating system records the addition of a new network card, the name Eth1,mac address of the new network card is the new MAC address assigned by VMware

Workaround:
Modify the/etc/udev/rules.d/70-persistent-net.rules file
Delete the information about eth0. The name of the network card that modifies the second eth1 is eth0.
Modify the MAC address of the/etc/sysconfig/network-scripts/ifcfg-eth0 MAC address to/etc/udev/rules.d/70-persistent-net.rules modified eth0.
Restart the server.

VMware cloning CentOS modifies Linux MAC address