Eth0 cannot initialize after VMware clones CentOS6.4

With VMware cloning CentOS6.4 virtual machine, modified the IP equivalent of ifcfg-eth0, restart the network, error.

(eth0 not found, will be deferred initialization)

and then use

#ifconfig

Only the local loopback port is visible,

and then use

#ifconfig-A

View all available network cards and discover that eth1 is displayed instead of eth0.

Found on the internet, "VMware cloning Ubuntu" No such device eth0 "error (http://www.linuxidc.com/Linux/2010-01/23991.htm)" There are related issues,

Guess

Clone, the original virtual machine network card configuration and so on all clone,

In VMware, however, clone actually re-creates a server,

The MAC address will also be re-created,

But because the configuration of the original server is copied, the newly created network card is no longer eth0, but is saved as eth1.

Workaround:

Modify The configuration file for/etc/udev/rules.d/70-persistent-net.rules//Save network card MAC address and other information

First look inside there are:

# PCI Device 0x8086:0x100f (e1000)
subsystem== "NET", action== "Add", drivers== "? *", attr{address}== "eth0-mac", attr{type}== "1", kernel== "eth*" , name= "eth0"

# PCI Device 0x8086:0x100f (e1000)
subsystem== "NET", action== "Add", drivers== "? *", attr{address}== "eth1-mac", attr{type}== "1", kernel== "eth*" , name= "eth1"

Remove the information from the above eth0 and eth1 the Eth1-〉eth0

# PCI Device 0x8086:0x100f (e1000)
subsystem== "NET", action== "Add", drivers== "? *", attr{address}== "eth1-mac", attr{type}== "1", kernel== "eth*" , name= "eth0"

then vim /etc/sysconfig/network-scripts/ifcfg-eth0. Configure IP and other information,

Restart the server and you're ready.

And then again with Ifconfig to see, what appears is the configuration information of eth0.

This article is from the "Wave Plume Breeze" blog, please be sure to keep this source http://1145004.blog.51cto.com/1135004/1569884

Eth0 cannot initialize after VMware clones CentOS6.4