Workaround for clone machine NIC after cloning virtual machine in VMware cannot start

A good deal of a daily blog, it seems that they are not hard enough. Come on, boy!

Well today to share with you, because in daily use, install Linu new system too time, so cloning system became everyone's first choice, however this is not all smooth, you will find cloning, cloning machine Nic can not start the phenomenon. OK, let's get to the solution!

1. First, enter the following directory:

[Email protected] ~]# cd/etc/udev/rules.d/

2. Modify the configuration file as follows:

original : [[email protected] rules.d]# vim 70-persistent-net.rules

# This file is automatically generated by the/lib/udev/write_net_rules

# program, run by the Persistent-net-generator.rules rules file.

#

# can modify it, as long as you keep each rule to a single

# line, and change is only the value of the Name= key.

# PCI Device 0x8086:0x100f (e1000)

subsystem== "NET", action== "Add", drivers== "? *", attr{address}== "00:0c:29:11:05:1e", attr{type}== "1", kernel== "eth*" , name=

"eth0"

# PCI Device 0x8086:0x100f (e1000)

subsystem== "NET", action== "Add", drivers== "? *", attr{address}== "00:0C:29:AA:8B:BF", attr{type}== "1", kernel== "eth*" , name=

"eth1"

modified : [[email protected] rules.d]# vim 70-persistent-net.rules

# This file is automatically generated by the/lib/udev/write_net_rules

# program, run by the Persistent-net-generator.rules rules file.

#

# can modify it, as long as you keep each rule to a single

# line, and change is only the value of the Name= key.

# PCI Device 0x8086:0x100f (e1000)

# subsystem== "NET", action== "Add", drivers== "? *", attr{address}== "00:0c:29:11:05:1e", attr{type}== "1", kernel== "eth*" , NAME

= "Eth0"

# PCI Device 0x8086:0x100f (e1000)

subsystem== "NET", action== "Add", drivers== "? *", attr{address}== "00:0c:29:aa:8b:bf", attr{type}== "1", kernel== "eth*", name=

"eth0"

3, modify the network card parameters:

[Email protected] ~]# Vim/etc/sysconfig/network-scripts/ifcfg-eth0

Device=eth0

Hwaddr=00:0C:29:AA:8B:BF * modified to the top of the Red MAC address *

Type=ethernet

Uuid=d7849a85-3812-4026-ab92-b2fa58b28ecf

Onboot=yes

Nm_controlled=yes

Bootproto=none

Ipaddr=192.168.255.252 * Configuring a new IP address *

netmask=255.255.255.0

dns2=4.4.4.4

dns1=8.8.8.8

Ipv6init=no

Userctl=no

4. Restart the system to see if the network card is starting properly and the IP address is normal.

[[email protected] ~]# shutdown-r now * Reboot system *

[Email protected] ~]# ifconfig

Eth0 Link encap:ethernet HWaddr 00:0C:29:AA:8B:BF

inet addr:192.168.255.252 bcast:192.168.255.255 mask:255.255.255.0

Inet6 ADDR:FE80::20C:29FF:FEAA:8BBF/64 Scope:link

Up broadcast RUNNING multicast mtu:1500 metric:1

RX packets:900 errors:0 dropped:0 overruns:0 frame:0

TX packets:788 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:87807 (85.7 KiB) TX bytes:115265 (112.5 KiB)

Lo Link encap:local Loopback

inet addr:127.0.0.1 mask:255.0.0.0

Inet6 addr::: 1/128 scope:host

Up LOOPBACK RUNNING mtu:65536 metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:0  (0.0 b) TX bytes:0 (0.0 b)

Visible, the network card starts normally, the IP address is OK.

This article ends ***********************

20150806

This article is from "Effort!" Struggle! "Blog, be sure to keep this provenance http://026mingming.blog.51cto.com/8783374/1682112

Workaround for clone machine NIC after cloning virtual machine in VMware cannot start