Although there are many online solutions on this issue, but I decided to write about myself again repeat this solution to the problem, focusing on updating knowledge and understanding of VMware 15 new features workstation.
When workstation cloning CentOS7.X series system virtual machine, whether it is a linked clone or a full clone using VMware, is very likely to occur following the card can not start the problem:
Note: The current pro-test VMware workstation 15 does not have this problem, later in this article I'll explain why I'm not writing this article and purpose.
1 ifup ens33 2 3 Error:Connection activation failed: No suitable device found for this connection
The reason for this problem is: the same MAC address, resulting in conflict
Clone a virtual machine, the default of its MAC address remains the MAC machine before the template, so the MAC address will conflict, when the system uses NetworkManager to manage network card
NetworkManager does not allow the same MAC address, NIC has led directly to get up, but CentOS6.X will not, because it uses to manage the network.
solution:
1, if you do not intend to use NetworkManager, NetworkManager can then direct close
1 systemctl STOP # Stop NetworkManager NetworkManager 2 systemctl mask # Disable NetworkManager NetworkManager, Windows-like disabled
3 systemctl disable NetworkManager # boot does not start
2, change the MAC address
1) through VMware workstation virtual machine management interface, just delete the previous card, re-add, or click Advanced, and modify the MAC address is not the same template machine, as shown below:
2) Then start the system, modify the network card configuration file / etc / sysconfig / network-scripts / ifcfg-XXX
Parameters HWADDR = new network card MAC
3) If there are 70-persistent-net.rules /etc/udev/rules.d/ the file directory, then there will be a MAC address to the new network card MAC
Why /etc/udev/rules.d/ directory if there is 70-persistent-net.rules this file below it?
Because if installed CentOS7 system when it is enabled in the kernel net.ifnames biosdevname = 0 = 0 , it means that the card CentOS7 without naming conventions, and traditional
eth0 ... ethn card rules, then the default in the system do not have this file, otherwise the installation of the system, despite changes in the future is to install the card again for the traditional naming convention, this file is still there.
Important : The above is VMware workstation 15 to appear before the problems in VMware workstation 15, this problem has not occurred
Because VMware workstation 15 in cloning a virtual machine, whether it is a linked clone or a full clone will automatically generate and replace the card's MAC address, then the above problem does not appear.
As VMware workstation 15 when the previous version which supports cloning automatically change the card MAC, there is no pro-test, but VMware workstation 15 I pro-test is no problem.
I write this purpose: mainly online update many older solutions article (although many), maybe a little to advertise the suspect VMware workstation 15,
But the focus is so that knowledge can update the look.