“Device eth0 does not seem to be present”解决办法

在KVM中克隆出新的CentOS虚拟机时，出现如下问题：
# service network restart
Shutting down loopback insterface: [ OK ]
Bringing up loopback insterface: [ OK ]
Bringing up interface eth0: Device eth0 does not seem to be present,delaying initialization. [FAILED]

用ifconfig查看发现缺少eth0，只有lo；用ifconfig -a查看发现多出了eth1的信息。

解决办法1：
# mv /etc/sysconfig/network-scripts/ifcfg-eth0  /etcsysconfig/network-scripts/ifcfg-eth1
将eth0的mac地址改为eth1的mac地址，同时改变其DEVICE名称为eth1，再重启网络即可。

解决办法2：
# rm -rf /etc/udev/rules.d/70-persistent-net.rules
# reboot

总之，只要保证/etc/sysconfig/network-scripts/ifcfg-eth0 与/etc/udev/rules.d/70-persistent-net.rules的信息一致即可，即网卡地址与网卡编号一致，这样service network restart 就可以配置成功。

时间： 2024-10-06 05:56:01

“Device eth0 does not seem to be present”解决办法的相关文章

CentOS中Device eth0 does not seem to be present错误解决办法

今天克隆的虚拟机,当需要多台虚拟机的时候,试用克隆真是方便,不过遇到了 Device eth0 does not seem to be present 的问题,在网上找到遇到同样问题的解决方法, 很顺利的解决,记录之: ifconfig…没有看到eth0..然后重启网卡又报下面错误. 故障现象: service network restart Shutting down loopback insterface: [ OK ] Bringing up loopback insterface: [

CentOS Linux解决Device eth0 does not seem to be present

在VMware里克隆出来的CentOS Linux.. ifconfig...没有看到eth0..然后重启网卡又报下面错误. 故障现象: service network restartShutting down loopback insterface:                                                                                                     [  OK  ]Bringing up loo

Bringing up interface eth0: Device eth0 does not seem to be present, delaying initialization.

--http://blog.csdn.net/xluren/article/details/38986667 Bringing up interface eth0:  Device eth0 does not seem to be present, delaying initialization. 在linux下的虚拟机出现了这个问题,问题的产生是因为之间做过部分的修改,clone等操作. 不就方案. CentOS Device does not seem to be present  故障现象

Device eth0 does not seem to be present,delaying initialization

centos6.4安装 minimal ifconfig...没有看到eth0..然后重启网卡又报下面错误. 故障现象: service network restartShutting down loopback insterface:                                                                                                     [  OK  ]Bringing up loopback in

虚拟机CentOS复制到其他主机vm下IP地址无效（Bringing up interface eth0: Device eth0 does not seem to be present, delaying initialization)

Bringing up interface eth0:  Device eth0 does not seem to be present, delaying initialization 在虚拟机VM下安装的CentOS遇到这个问题,我是将centos.vmx放到其他的VM下打开 #dhclient #service network restart Shutting down loopback insterface:                                        

Linux 克隆虚拟机引起的“Device eth0 does not seem to be present, delaying initialization”

虚拟机Vmware上克隆了一个Red Hat Enterprise Linx启动时发现找不到网卡,如下所示,如果你在命令窗口启动网络服务就会遇到"Device eth0 does not seem to be present, delaying initialization"错误 关于这个错误,搜索了一下网上的资料,发现还蛮多人遇到过这类错误,了解了一下错误产生的原因和解决方案 错误原因: 克隆的Linux系统在新的机器上运行,新服务器网卡物理地址已经改变.而/etc/udev/rul

问题:Bringing up interface eth0: Device eth0 does not seem to be present,delaying initialization. [FAILED]—— 找不到网卡。

克隆虚拟机的时候或其他情况出现以下问题(命令service network restart): Bringing up interface eth0:  Device eth0 does not seem to be present,delaying initialization.                    [FAILED] 1.造成的原因: 第一次创建的时候,在文件: /etc/sysconfig/network-scripts/ifcfg-eth0 里面设定了网卡0绑定了MAC地

CentOS Linux解决Device eth0 does not seem to be present【转】

在VMware里克隆出来的CentOS Linux.. ifconfig...没有看到eth0..然后重启网卡又报下面错误. 故障现象: service network restartShutting down loopback insterface:                                                                                                     [  OK  ]Bringing up loo

CentOS Linux解决 Device eth0 does not seem to be present

通过OVF部署Linux主机后提示 ringing up interface eth0:  Device eth0 does not seem to be present,delaying initialization. 解决办法: 首先,打开/etc/udev/rules.d/70-persistent-net.rules内容如下面例子所示: # vi /etc/udev/rules.d/70-persistent-net.rules# This file was automatically