Workarounds that eth0 cannot find after VMware clones a Linux virtual machine

Cause analysis: Many Linux uses udev to dynamically manage device files and to persist names based on device information, andVMware automatically generates Mac addresses for virtual machines. In this way, because the virtual machine of the base system has recorded the NIC mac address of the virtual machine corresponding to the NIC eth0, the mac address of the cloned virtual machine will be changed, andUdev will automatically The Mac corresponds to the NIC eth1. And so on,Udev will record all of the identified Mac and network card name relationship, so each clone network card name will automatically add 1, but in fact, kernel only to recognize a network card, The network configuration associated with the NIC name has not changed.

Solution:

1.udev Save the mac and Nic name in /etc/udev/rules.d/70-persistent-net.rules , in the cloned virtual machine as long as the deletion and name= " Eth0 " related row Delete, then the eth1 corresponding line of " eth1 " modified to " eth0 ", and restart the system. Another way is to remove the contents and restart the system.

2. # ifconfig eth0 up

#ifconfig

Now you can see the relevant information of Eth0 !

This article is from the "10917734" blog, please be sure to keep this source http://10927734.blog.51cto.com/10917734/1826825

Workarounds that eth0 cannot find after VMware clones a Linux virtual machine