rhel 6 在虚拟机中,启动eth0 网卡时报错
2011-07-14 13:41
267 查看
Error: Connection activation failed: Device not managed by NetworkManager
rhel 6 在虚拟机中,启动eth0 网卡时报错:
Error: Connection activation failed: Device not managed by NetworkManager
于是在网上找了解决方法:
1. Remove Network Manager from startup Services.
chkconfig NetworkManager off
2. Add Default Net Manager
chkconfig network on
Stop NetworkManager first
service NetworkManager stop
and then start Default Manager
service network start
or you can change it easy:
system-config-network
uncheck the box that sets the eth0 as managed by NetworkManager and set IP info from there.
system-config-services
stop and disable NetworkManager , start and enable network
you have problem because both of NetworkManager and Network using same Network driver and default network blocking access for NetworkManager. if you disable NetworkManager your problem will disappeared after restart.
=================================================================================
结果还是有错:
在service network Start的时候
*出环回接口: [确定]
*出界面 eth0:
正在决定 eth0 的 IP 信息...失败了。
[失败]
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
于是在restart network一下,就OK了,不知道什么原理。
rhel 6 在虚拟机中,启动eth0 网卡时报错:
Error: Connection activation failed: Device not managed by NetworkManager
于是在网上找了解决方法:
1. Remove Network Manager from startup Services.
chkconfig NetworkManager off
2. Add Default Net Manager
chkconfig network on
Stop NetworkManager first
service NetworkManager stop
and then start Default Manager
service network start
or you can change it easy:
system-config-network
uncheck the box that sets the eth0 as managed by NetworkManager and set IP info from there.
system-config-services
stop and disable NetworkManager , start and enable network
you have problem because both of NetworkManager and Network using same Network driver and default network blocking access for NetworkManager. if you disable NetworkManager your problem will disappeared after restart.
=================================================================================
结果还是有错:
在service network Start的时候
*出环回接口: [确定]
*出界面 eth0:
正在决定 eth0 的 IP 信息...失败了。
[失败]
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
于是在restart network一下,就OK了,不知道什么原理。
相关文章推荐
- 虚拟机下rhel6网卡启动不起来
- RHEL6.3克隆虚拟机后的网卡启动失败问题解析 分类: Linux 2014-12-07 15:32 136人阅读 评论(0) 收藏
- openstack镜像-关于通过clone虚拟机制作的镜像开机后网卡eth0启动失败的问题
- RHEL6.3克隆虚拟机后的网卡启动失败问题解析 分类: Linux 2014-12-07 15:32 137人阅读 评论(0) 收藏
- RHEL6.3克隆虚拟机后的网卡启动失败问题解析
- RHEL6.3克隆虚拟机后的网卡启动失败问题解析
- VMware中copy一个Centos6.2虚拟机eth0网卡不能正常启动
- RHEL6.3克隆虚拟机后的网卡启动失败问题解析
- vmware克隆虚拟机eth0网卡无法启动
- RHEL6.3克隆虚拟机后的网卡启动失败问题解析
- RHEL7虚拟机添加新网卡后,网卡无法启动
- centos 不能上网,启动eth0 网卡时报错
- RHEL6.3克隆虚拟机后的网卡启动失败问题解析
- 虚拟机克隆系统linux出现的网卡无法启动 ip无法看到的解决方案
- vmware克隆linux虚拟机网卡无法启动问题
- 克隆虚拟机导致Linux无法启动网卡的分析与解决
- 虚拟机克隆造成网卡不能正常启动解决办法
- Device eth0 does not seem to be present, delaying initialization(解决克隆CentOS6.3虚拟机后网卡设备无法启动问题)
- VMWare下RHEL 6.4 启动到eth0会hang住的问题解决
- 虚拟机迁移或克隆后centos 5.8 6.4 网卡不能启动问题解决办法