Nic cannot be enabled after cloning a VM after centos and redhat6.0

After centos and redhat6.0, Nic cannot be enabled after virtual machine cloning in versions later than redhat and centos6.0. if we want to clone a virtual machine after installing a system on a virtual machine, we will find that the clone VM Nic cannot start and report the Error: Nosui...
After centos and redhat6.0, Nic cannot be enabled after virtual machine cloning in versions later than redhat and centos6.0. if we want to clone a virtual machine after installing a system on a virtual machine, we will find that the clone VM Nic cannot start and report the Error: No suitable device found: no device found for connection 'system eth0 '. or Bringing up interface eth0: Device eth0 does not seem to be present, delaying initialization. www.2cto.com at the same time when we execute the ifconfig command, we will find that the eth1 Nic configuration file is/etc/sysconfig/network-scripts/ifcfg-eth0. Solution: centos-> delete this/etc/udev/rules. d/70-persistent-net.rules, restart the file and change eth1 of NAME = "eth1" to eth0, you also need to modify the mac address in ATTR {address} to be consistent with the mac address in the/etc/sysconfig/network-scripts/ifcfg-eth0 file. Www.2cto.com redhat-> redhat is a little tricky, redhat needs to rename the/etc/sysconfig/network-scripts/ifcfg-eth0 file to/etc/sysconfig/network-scripts/ifcfg-eth1, modify DEVICE = eth0 in the file to DEVICE = eth1, and then set/etc/udev/rules. delete the NAME = "eth0" in the d/70-persistent-net.rules file and restart the network server normally, except that eth0 is unavailable, instead, it is eth1. if you want to change it to eth0, you need to restart the system and modify all the above three locations before restarting.