Network configuration to be modified after Linux machine cloning

After cloning a Linux machine, you need to modify the network configuration. assume that the original machine is two NICs, eth0 and eth1. after cloning, the MAC address is also two. the MAC address is different from the original one, however, because some network configurations of the system are not updated, the network of the cloned machine cannot be started. for example, an exception occurs... after cloning a Linux machine, you need to modify the network configuration. assume that the original machine has two NICs, eth0 and eth1. after cloning, the MAC address is also two. the MAC address is different from the original one, however, because some network configurations of the system are not updated, the network of the cloned machine cannot be started. for example, an exception occurs: Bringing up interface eth0: pcnet32 device eth0 does not seepresent, delaying initialization. or the output shown in ifconfig-a is not consistent with the actual situation, for example, the eth0 does not exist, but eth2 and eth3 are added. The following are some repair items: 1. set/etc/sysconfig/n Etwork-scripts/ifcfg-eth3 change to xxx-eth0, modify the information inside 2. open etc/sysconfig/network-scripts/ficfg-eth0 (if this file does not exist, rename it from the xxx-eth3), make sure ONBOOT should be yes, 3. check the MAC of the ficfg-eth0 and the MAC of the ifconfig actual MAC and the MAC of the NIC corresponding to the VM information page, and modify the MAC of the ficfg-eth0. 4. change the hostname in/etc/sysconfig/network to the new hostname3. restart the service, service NetworkManager restart and service network restart. if not, delete or modify/etc/udev/rules. d/70-persistent-net.rules, reboot system, which defines the binding relationship between the NIC and MAC address. /Etc/udev/rules. d/70-persistent-net.rules