Device eth0 does not seem to be present" on cloned CentOS VM
2013-07-12 18:33
519 查看
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.
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
Update the network configuration.
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
# start_udev
Update the network configuration.
# service network restart
相关文章推荐
- Vmware Workstation8.0克隆CentOS6.3出现"device eth0 does not seem to be present, delaying initialization"
- [centos] Linux下"Device eth0 does not seem to be present,delaying initialization."问题解决方法.
- 从vware里克隆出的CentOS Linux,ifconfig 没有ip地址 和重启 Device eth0 does not seem to be present
- CentOS Linux解决Device eth0 does not seem to be present
- centos网卡错误Device eth0 does not seem to be present
- CentOS Linux解决Device eth0 does not seem to be present
- 【转】CentOS Linux解决Device eth0 does not seem to be present(linux)
- CentOS Linux解决Device eth0 does not seem to be present
- centos系统 解决Device eth0 does not seem to be present
- CentOS Linux解决Device eth0 does not seem to be present
- vm 克隆一台新机器启动网卡报错:device eth0 does not seem to be present, delaying initialization
- CentOS Linux解决Device eth0 does not seem to be present
- CentOS 解决Device eth0 does not seem to be present和ifconfig有其他网卡IP
- " Device eth0 does not seem to be present, delaying initialization"
- CentOS Linux解决Device eth0 does not seem to be present
- CentOS: Device eth0 does not seem to be present
- vmware复制centos虚拟机碰到Device eth0 does not seem to be present的问题
- Vmware克隆centos:device eth0 does not seem to be present,delaying initialization
- 解决Linux出现"Device eth0 does not seem to be present"问题
- 解决centos网卡启动device eth0 does not seem to be present, delaying initialization.