VMware cloning Centos6.9 virtual machine NIC does not start problem

VMware cloning Centos6.9 virtual machine NIC does not start problem

The general approach is to change the cloned virtual machine IP, then Setup to change the NIC device name and restart the Network Service to resolve the issue.

However, I found in the cloning of conventional methods can not be resolved, so turned a lot of posts, found that the cause of the problem is the clone and before cloning the NIC MAC address is the same, so long as the cloned MAC address can solve the problem.

First say the solution: from the dmesg|grep eth inside get to the device Mac, and then manually change to the network card configuration file inside,reboot. Perfect solution.

Now that it's used, here's a dmesg command.

DMESG is used to display the kernel ring buffer (kernel-ring buffer) content, and the kernel stores various messages here. At system boot time, the kernel fills in this buffer with information related to hardware and module initialization. Messages in the kernel ring buffer are often useful for diagnosing system problems. When you run DMESG, it displays a lot of information. It is common to use the pipe to view the output of DMESG through less or grep , which makes it easier to find unknown origin information. For example, if you find that your hard disk is performing poorly, you can use DMESG to check that they are running in DMA mode:

$DMESG | grep DMA
...
IDe0:bm-dma at 0xf000-0xf007, BIOS setTings:hda:DMA, HDB:DMA
IDE1:BM-DMA at 0xf008-0xf00f, BIOS Settings:hdc:DMA, Hdd:D ma
...

The above lines indicate what mode each IDE device is running in. If there is a problem with the Ethernet connection, you can search for the ETH in the DMESG log:

$DMESG | grep ETH
Forcedeth.c:reverse Engineered NForce
Ethernet driver. Version 0.49.
ETH0:FORCEDETH.C: subsystem:0147b:1c00
Bound to 0000:00:04.0
Eth0:no IPV6 Routers present

If everything is OK, then DMESG displays the hardware configuration information for each NIC. If a system service fails to be properly configured, the DMESG log quickly fills up with error messages, which is a good starting point for diagnosing failures.

It can also be used to detect the loading of system kernel modules, such as to detect ACPI loading, using DMESG | grep acpI

DMESG | egrep -i "(APM|ACPI)"

Kernel command line:vga=274 quiet Console=ttys3,9600acpi=no-idleoot=/dev/hda3

Acpi:core Subsystem version [20010208]

Acpi:subsystem EnableD

Acpi:system firmWare SUPPORTS:C2

Acpi:plvl2lat=99 plvl3lat=1001

ACPI:C2 enter=1417 C2 exit=354

ACPI:C3 enter=-1 C3 Exit=-1

Acpi:not using ACPI Idle

Acpi:system firmware supports:s0 S1 S4 S

This article is derived from blog http://xiangji.blog.51cto.com, be sure to keep this source.

This article is from the "Communication" blog, please be sure to keep this source http://xiangji.blog.51cto.com/12944296/1934352

VMware cloning Centos6.9 virtual machine NIC does not start problem