What if the problem cannot be found in the configuration of the centos7 virtual machine Nic cloned by VMware?

Editor to share with you the use of VMware cloning of the centos7 virtual machine network card configuration can not find a problem, I hope you will learn something after reading this article, let's discuss it together!

Background

The newly cloned virtual machine ifconfig shows the configuration of the Nic as follows:

You can see that the name of the network card is ens33. Enter the network card configuration file directory. There is no ens33 network card configuration, only the default eno16777736 of centos7.

Take a look at the configuration.

Solution.

Note that the configuration name of the network card has been changed to eth0 to perform the following operations. There are three changes altogether. The first place is the network card name: / etc/sysconfig/network-scripts/ifcfg-eth0, the second place is in the configuration file: NAME=eth0, and the third place is also in the configuration file: DEVICE=eth0

At first, I used dhcp to dynamically allocate ip. In order to prevent changes to ip, I modified and added the following configuration

The value of HWADDR must always be the same as that of eth0, otherwise the startup of the network card will fail.

Modify / etc/sysconfig/grub to add net.ifnames=0 biosdevname=0

Restart the system reboot and it will take effect.

After reading this article, I believe you have a certain understanding of "what to do if you can't find a problem with the configuration of the centos7 virtual machine network card cloned by VMware". If you want to know more about it, you are welcome to follow the industry information channel, thank you for reading!