Troubleshooting a network adapter that cannot be started after cloning CentOS in a VMware virtual machine

0. Previous words: A long-troubled question

Before often such problems, but because there is no solution, can only bite the bullet himself to install a new operating system, although it is a waste of time, but also reluctantly solved it.

But there is a problem not to solve the overall bad, and then after a variety of search and ask netizens, find out the following this very good solution, tested, this method can be a perfect solution to this problem.

1. Problem arises: After cloning CentOS, there is a situation where the NIC cannot be configured

In the experimental environment is often used in multiple Linux operating systems, in order to avoid the installation of waiting time, we generally take the cloning operation system, but this will be a problem, that is, the cloned operating system can not start the network card, the situation is as follows:

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/71/3F/wKiom1XJmD_CmJcZAAGT3zGtjFs101.jpg "title=" Clone.png "alt=" Wkiom1xjmd_cmjczaagt3zgtjfs101.jpg "/> Nic can not start, network connectivity becomes a problem, and no network connection of the Linux operating system, for operation and maintenance testing, that is a very troublesome thing." What to do?

2. Problem Analysis: Why the network card could not be started

The problem is/etc/udev/rules.d/70-. Persistent-net.rules this file, because this file is bound to the network card and MAC address, that is, we cloned the operating system, this file with the original operating system is the same, but the cloned operating system, because the network card has changed, the MAC address of the network card has changed, so that, our operating system's network card and MAC address is not the same as the binding in the/etc/udev/rules.d/70-persistent-net.rules , so the network card can not boot up the situation.

3. Problem Resolution: Remove the NIC binding file

Since the above-mentioned file is bound to the previous network card and MAC address, so that the current network card and MAC address does not correspond to the network card can not be started, then we could take the file to delete the method:

[Email protected] ~]# Rm/etc/udev/rules.d/70-persistent-net.rules

After the deletion, restart the system, the system will help us automatically generate a new binding the current network card and MAC address of the configuration file, so that our network card can be started.

Of course, in addition to the use of deleting this seems to be a bit of an extreme approach, you can manually modify the above file, but, compared to the method of deletion, it is much more troublesome!

This article is from the "fragrant fluttering leaves" blog, please make sure to keep this source http://xpleaf.blog.51cto.com/9315560/1683646

Troubleshooting a network adapter that cannot be started after cloning CentOS in a VMware virtual machine