Problem phenomenon:
Sometimes, you can use the cloning capabilities of VMware virtual machines to quickly replicate installed Linux systems.
But after cloning, you will find that there is no eth0 network card.
Workaround:
1. Edit the/etc/udev/rules.d/70-persistent-net.rules file
As you can see, eth0 is the network card of the pre-clone machine, and Eth1 is the NIC generated by the cloned machine.
So
The name= "eth0" line configuration commented out or deleted, the name= "eth1" modified to Name= "Eth0", modified as follows:
2. Change the NIC configuration file,/etc/sysconfig/network-scripts/ifcfg-eth0
Modify the value of HWADDR to the new value in the/etc/udev/rules.d/70-persistent-net.rules file, as follows:
3, restart the system, reboot.
welcome everyone, join my public number: Big Data lie over the pit ai lie in the pit
At the same time, you can follow my personal blog :
http://www.cnblogs.com/zlslch/ and http://www.cnblogs.com/lchzls/ Http://www.cnblogs.com/sunn ydream/
For details, see: http://www.cnblogs.com/zlslch/p/7473861.html
Life is short, I would like to share. This public number will uphold the old learning to learn the endless exchange of open source spirit, gathered in the Internet and personal learning work of the essence of dry knowledge, everything to the Internet, feedback back to the Internet.
Current research areas: Big data, machine learning, deep learning, artificial intelligence, data mining, data analysis. Languages include: Java, Scala, Python, Shell, Linux, and more. It also covers the usual use of mobile phones, computers and the Internet using tips, problems and practical software. As long as you focus and stay in the group, every day must have a harvest
corresponding to the platform discussion and answer QQ group: Big Data and artificial intelligence lying in the pit (total group) (161156071)
Problem with eth0 Nic not found after VMware virtual machine cloning Linux (CentOS) system (detailed text)