Solution that eth0 cannot find after VMWare clones or copies a Linux Virtual Machine

Symptom: the recent virtual machine system was installed as Fedora. For future convenience, the virtual machine was cloned or copied. When the cloned virtual machine is used, the eth0 Nic in the basic system is lost to the new system. If ifconfig-a is used, only eth1 is found. Because the network configuration of the basic system is based on eth0, and eth1 does not have network-related configuration, in this case, the network in the virtual machine must be normal, and only the network configuration of eth1 should be added, in this way, the NIC configuration needs to be modified each time when multiple Linux systems are tested.

Symptom description:

The virtual machine system has been installed with Fedora recently. For future convenience, the virtual machine can be cloned or copied. When the cloned virtual machine is used, the network card eth0 in the basic system is lost to the new system. If ifconfig-a is used, only eth1 is found. Because the network configuration of the basic system is based on eth0, and eth1 does not have network-related configuration, in this case, the network in the virtual machine must be normal, and only the network configuration of eth1 should be added, in this way, it is inconvenient to modify the NIC configuration every time you perform multiple Linux system tests. Furthermore, if the clone VM continues to clone or copy a new Vm, the nic id will be automatically added with 1 (the second clone will be changed to eth2 ), dmesg shows that the kernel only recognizes the network adapter eth0.

Cause analysis:

Many Linux distribution uses udev to dynamically manage device files and name them based on device information. For example, in Debian etch, udev identifies the NIC during system boot and records the mac address and nic name in the udev rule script. VMware automatically generates the mac address of the VM. In this way, because the VM of the basic system has recorded that the mac address of the NIC of the VM corresponds to eth0 of the NIC, the mac address of the cloned VM is changed, udev automatically maps the mac to the network adapter eth1. Similarly, udev records all the relationships between recognized mac addresses and network card names. Therefore, each clone Nic name is automatically added with 1, and its real-time kernel only recognizes one network card, the network configuration related to the NIC name has not changed.

Solution:

Network search finds that In Debian etch, udev stores the correspondence between mac and nic name in/etc/udev/rules. d/z25_persistent-net.rules, In the cloned virtual machine as long as you delete the line with NAME = "eth0" and restart the system. For example, delete the following two lines in Debian etch:
# PCI device 0x1022: 0x2000 (pcnet32) SUBSYSTEM = "net", DRIVERS = "? * ", ATTRS {address} =
"00: 0c: 29: 4c: 46: 01", NAME = "eth0 ″

Modify the 70-persistent-net.rules file under/etc/udev/rules. d under my Fedora.

Delete # Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] (rule written by anaconda)
SUBSYSTEM = "net", ACTION = "add", DRIVERS = "? * ", ATTR {address} =" 00: 0c: 29: ad: 06: 2a ",
ATTR {type} = "1", KERNEL = "eth *", NAME = "eth0 ″

Modify "eth1" of the corresponding line of eth1 to "eth0.

Another method is to delete all the contents and restart the system. The system also discovers the hardware of the NIC and generates the file again.

OK!