Device eth0 does not seem to be present" on cloned CentOS VM

本文介绍了解决在克隆CentOS虚拟机后遇到的eth0设备未找到错误的步骤。通过修改udev配置文件，确保新设备正确识别为eth0，从而解决网络连接问题。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

http://linuxtoolkit.blogspot.tw/2012/03/device-eth0-does-not-seem-to-be-present.html

After cloning the a CentOS 6 Virtual Machine from a VMware VM Template. On powering, I encountered the error "Device eth0 does not seem to be present".

Basically, in a nutshell, the OS remembers the old NIC of the template and new NIC provided after the clone are assigns as though they were new NICs. To solve the problem, remove the "SUBSYSTEM" entry that contains the old entry and change the eth1 to eth0 accordingly.

# vim /etc/udev/rules.d/70-persistent-net.rules

# PCI device 0x15ad:0x07b0 (vmxnet3)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="00:50:56:ae:00:1a", 
ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x15ad:0x07b0 (vmxnet3)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="00:50:56:ae:00:1b", 
ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x15ad:0x07b0 (vmxnet3)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="00:50:56:ae:00:1b", 
ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

Remember to modify the /etc/sysconfig/network-scripts/ifcfg-eth0 to reflect the correct changes.

After modifying and updating the udev configuration as seen in the 2 blog entries. You can reload the new udev configuration in the memory. Use the command start_udev