Network startup error occurred when copying fedora16 from vmware

A network startup error occurred when copying fedora16 from vmware. Today, we made an experiment to copy the fedora16 system installed in vmware. As a result, the system started the replication and found that the ora16 operating system could not be connected to the Internet, the system before replication can access the Internet. Then I used the ifconfig command to check my Nic information, I found that the address of my p3p1 Nic is different from the static ip I configured in the/etc/sysconfig/network-scripts/ifcfg-p3p1 configuration file, I thought the network was not started, use systemctl restart network. service Command to start the network, but did not expect to say that the startup error, then I use ifup p3p1 to start the network card, actually reported error: No suitable device found: no device found for connection 'System p3p1' in vmware, and then google is used to search for this error. Many people found that/etc/udev/rules is deleted. the 70-persistent-net.rules file under the d directory, but when I enter this directory, I find that this file does not exist at all, and then I find a saying to put/etc/sysconfig/network- NM_CONTROLLED = "yes" in the scripts/ifcfg-p3p1 configuration file is set to NM_CONTROLLED = "no ". Then I restarted the network and found that it still failed to start. After ifup p3p1, the system prompts that the physical address of the NIC does not match, and it also fails. Then use google to search for udev to dynamically manage device files and see what udev is. Many Linux distribution uses udev to dynamically manage device files and name them based on device information. Udev identifies the network adapter during system boot and records the mac address and network adapter name in the udev rule script 70-persistent-net.rules. I can find that this file does not exist in my own system. That is to say, my system does not use the rule script to specify the mac ing between my Nic name and mac address, how does the system identify my physical address mismatch? Suddenly thought of is not I configured in the ifcfg-p3p1 configuration file mac address, so quickly open the ifcfg-p3p1 configuration file to see, the results are really like this, the HWADDR set mac address to delete, restart the system and you will be able to access the Internet. Cause of error: When the wmware system is replicated, a NIC is assigned to the replication system, so the physical address of the NIC is changed. This is also the cause of an error, because I wrote the physical address of the NIC IN THE ifcfg-p3p1 configuration file, and this physical address is still the physical address of the NIC of my original system, when the network is started, the physical address configured in the configuration file does not match the physical address detected by the actual system. Therefore, when ifup p3p1 is enabled, the physical address of the NIC does not match. To sum up today's problems, I did not understand the real role of each item in the previous static IP configuration. I searched the internet and copied and pasted it, as a result, it takes a long time to identify a problem.