Linux operating system-copying a copy of Linux after importing VMware eth0 NIC fails to boot (or clone a Linux virtual machine)

2. When you do the experiment, you may need more than one virtual host, if you have to install from scratch is certainly unreasonable. There are two ways to do this: the first is to copy a virtual host directly into the folder and then import it into VMware.

   650) this.width=650; "Src=" Http://s2.51cto.com/wyfs02/M00/84/53/wKiom1eNgtbzFlrUAAAlyeF2czk359.png-wh_500x0-wm_3 -wmp_4-s_1982224013.png "title=" () 3@w]7nwjvgdo3c]980~h0.png "alt=" Wkiom1engtbzflruaaalyef2czk359.png-wh_50 "/>

4. Clone a virtual host directly in VMware

However, if the first way to operate, it will certainly cause the Eth0 network card can not start, because the virtual Host network card has become a eth1. We need to make some changes and change it back to eth0.

Workaround:

1. Edit the/etc/udev/rules.d/70-persistent-net.rules file

2, the Name= "eth0" the line configuration commented out or deleted, the name= "eth1" Changes to Name= "eth0"

3, Note: Network card configuration file,/etc/sysconfig/network-scripts/ifcfg-eth0, parameter hwaddr value I was commented out. If you want to use the corresponding new value (ATTR (address) that needs to be modified to the/etc/udev/rules.d/70-persistent-net.rules file.

4, restart the virtual host, restart the service, restart the network card

This article is from the "one Gourd soy sauce" blog, please be sure to keep this source http://zhushenghang.blog.51cto.com/11105203/1827625

Linux operating system-copying a copy of Linux after importing VMware eth0 NIC fails to boot (or clone a Linux virtual machine)