Device eth0 does not seem to be present,delaying initialization. 虚拟机克隆后出现网卡起不来

一.故障现象:

[[email protected] ~]# 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]

解决办法:

[[email protected] ~]# rm -rf /etc/udev/rules.d/70-persistent-net.rules

[[email protected] ~]# reboot ………………

[[email protected] ~]# service network restart

Shutting down loopback insterface:                                                         [   OK   ]

Bringing up loopback insterface:                                                              [   OK   ]

Bringing up interface eth0:                                                                     [   OK   ]

[[email protected] ~]#

二.另一种方法

造成这样的原因,是因为在虚拟机(Vmware)中移动了Centos系统对应的文件,导致重新配置时,网卡的MAC地址变了,输入ifconfig -a,找不到eth0

·······

安装完一个centos虚拟机,又拷贝一份,开机后网卡无法正常启动,报错:Device eth0 does not seem to be present, 
delaying initialization

解决:# mv /etc/sysconfig/network-scripts/ifcfg-eth0 
sysconfig/network-scripts/ifcfg-eth1

vim 
sysconfig/network-scripts/ifcfg-eth1

修改DEVICE="eth0" 
为DEVICE="eth1"

可删掉uuid、物理地址

然后重启启动网卡尝试下

三.比第一种更深入一点

故障前的操作:

DELL刀片装的是CentOS6.3的操作系统,网卡识别的是em1和em2,由于工作需要做了槽位调整,并启动了刀片

故障现象:

启动后网络不通,通过iDRAC登录后route查看缺省路由正常;

重启网络服务:

[[email protected] ~]# service network restart Shutting down loopback insterface: [ OK ] Bringing up loopback insterface: [ OK ] Bringing up interface em1: Device em1 does not seem to be present,delaying initialization. [FAILED]

分析问题和解决:

之前在别的文章中我们提过70-persistent-net.rules文件,所以看了一下:

[[email protected] ~]# vi /etc/udev/rules.d/70-persistent-net.rules

# This file was automatically generated by the /lib/udev/write_net_rules # program, run by the persistent-net-generator.rules rules file. # # You can modify it, as long as you keep each rule on a single # line, and change only the value of the NAME= key.

# PCI device 0x14e4:0x163a (bnx2) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="24:b6:fd:ab:76:1e", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x14e4:0x163a (bnx2) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="24:b6:fd:ab:76:1c", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

发现NAME的名称不正确,依次将上述红色字体中的eth0改为em1,eth1改为em2;

*切记:网卡编号由MAC地址大小决定,MAC越小网卡编号越小;

如下:

…………

# PCI device 0x14e4:0x163a (bnx2)

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="24:b6:fd:ab:76:1e", ATTR{type}=="1", KERNEL=="eth*", NAME="em2"

# PCI device 0x14e4:0x163a (bnx2) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="24:b6:fd:ab:76:1c", ATTR{type}=="1", KERNEL=="eth*", NAME="em1"

保存退出~!

[[email protected] ~]#reboot

………………

问题解决~!

时间: 2024-10-08 20:27:16

Device eth0 does not seem to be present,delaying initialization. 虚拟机克隆后出现网卡起不来的相关文章

问题: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地

linux 网卡问题 Device eth0 does not seem to be present,delaying initialization.

Device eth0 does not seem to be present,delaying initialization. 网上搜索后才发现原因所在:原来vmware在复制了虚拟机后会自动生成一个新的网卡设备供该虚拟机使用,比如 原先的网卡是eth0,复制虚拟机后后就会增加eth1.但是由于没有生成相应的/etc/sysconfig/network-scripts /ifcfg-eth1文件,导致网络连接失败,这个应该是vmware的一个bug. 查看网卡配置文件/etc/udev/rul

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

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"错误 关于这个错误,搜索了一下网

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

vmware报Device eth0 does not seem to be present, delaying initialization错误

系统环境: CentOS-6.8-X86_64 使用vmware的克隆功能后,使用新克隆的虚拟机会报Device eth0 does not seem to be present, delaying initialization这样一个错误,这是由于网卡MAC地址错误导致的问题. 解决方法: 1.删除/etc/udev/rules.d/70-persistent-net.rules文件 2.编辑/etc/sysconfig/network-scripts/ifcfg-ethX文件,删除关于MAC

Device eth0 does not seem to be present,delaying initialization解决方法

Bringing up interface eth0:  Device eth0 does not seem to be present, delaying initialization. 在linux下的虚拟机出现了这个问题,原因是要修改固定ip,作了部分修改. 故障现象:[[email protected]~]# service network restart Shutting down loopback insterface: