当前位置:七道奇文章资讯系统安全Linux安全
日期:2011-11-06 23:47:00  来源:本站整理

RHEL6/Scientific Linux 6虚拟机克隆招致的网卡问题办理办法[Linux安全]

赞助商链接



  本文“RHEL6/Scientific Linux 6虚拟机克隆招致的网卡问题办理办法[Linux安全]”是由七道奇为您精心收集,来源于网络转载,文章版权归文章作者所有,本站不对其观点以及内容做任何评价,请读者自行判断,以下是其具体内容:

环境:Virtualbox+RHEL 6 x64
用VirtualBox的vboxmanager克隆的虚拟机,操作系统RHEL6,启动后发现网卡不能用了.重启网络服务,报以下错误:
Bringing up interface eth0: Device eth0 does not seem to be present, delaying initialization.

快速办理办法:
rm -rf /etc/udev/rules.d/70-persistent-net.rules 然后重启系统

解析:
在RHEL5里也发生近似事情,因为复制虚拟机MAC会重新生成,但是操作系统的MAC却写在ifcfg-ethx里,造成了不一致,所以不能启动网络接 口,在RHEL5里可以利用kudzu大概注释网卡配置文件的MAC字段来办理这个问题.但是在RHEL6里,kudzu已经被hal服务代替了.固然 lspci可以正常认到网卡,但是却无法利用/etc/init.d/network restart来启动服务.尝试注释ifcfg-eth0的MAC字段,还是报错.查看了下udev的法则,发现了问题的所在.

[root@Oracle ~]# cat /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.

# net device () (custom name provided by external tool)
SUBSYSTEM==”net”, ACTION==”add”, DRIVERS==”?*”, ATTR{address}==”08:00:27:16:31:11″, ATTR{type}==”1″, KERNEL==”eth*”, NAME=”eth0″

# net device ()
SUBSYSTEM==”net”, ACTION==”add”, DRIVERS==”?*”, ATTR{address}==”08:00:27:32:66:63″, ATTR{type}==”1″, KERNEL==”eth*”, NAME=”eth1″
[root@Oracle ~]#

本来UDEV这里把克隆前的MAC当作了当前虚拟机的eth0 MAC,而重新生成的08:00:27:32:66:63是eth1的MAC.

办理这个问题,只要删除旧的UDEV配置,改正成:
[root@Oracle ~]# cat /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.

# net device () (custom name provided by external tool)
SUBSYSTEM==”net”, ACTION==”add”, DRIVERS==”?*”, ATTR{address}==”08:00:27:32:66:63″, ATTR{type}==”1″, KERNEL==”eth*”, NAME=”eth0″

重启network服务,一切OK
[root@Oracle ~]# /etc/init.d/network restart
Shutting down interface eth0: [ OK ]
Shutting down loopback interface: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
[root@Oracle ~]# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 08:00:27:32:66:63
inet addr:172.16.100.3 Bcast:172.16.100.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe32:6663/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:206 errors:0 dropped:0 overruns:0 frame:0
TX packets:203 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:21157 (20.6 KiB) TX bytes:24515 (23.9 KiB)

Virtualbox有这个问题,VMWARE克隆虚拟机应当也是有这个问题的.   以上是“RHEL6/Scientific Linux 6虚拟机克隆招致的网卡问题办理办法[Linux安全]”的内容,如果你对以上该文章内容感兴趣,你可以看看七道奇为您推荐以下文章:

  • <b>yum源安装方法在RHEL5.5上布置LAMP</b>
  • RHEL6系统初体验之系统安装和本地YUN(源)服务器的构建
  • RHEL6/Scientific Linux 6虚拟机克隆招致的网卡问题办理办法
  • RHEL 4下安装VNC的一个小问题
  • <b>Linux(RHEL5)系统安全通例优化</b>
  • RHEL 6系统管理
  • RHEL 6网络配置
  • RHEL5上制作软件RAID 并在软件RAID底子上做LVM
  • <b>RHEL-5配置CentOS-5的yum源</b>
  • RHEL5下的Apache2.0+Tomcat5.5的集群配置
  • <b>Linux ( RHEL 4 )中ftp衔接530错误的办理办法</b>
  • <b>RHEL6安装Tomcat 6和hudson</b>
  • 本文地址: 与您的QQ/BBS好友分享!
    • 好的评价 如果您觉得此文章好,就请您
        0%(0)
    • 差的评价 如果您觉得此文章差,就请您
        0%(0)

    文章评论评论内容只代表网友观点,与本站立场无关!

       评论摘要(共 0 条,得分 0 分,平均 0 分) 查看完整评论
    Copyright © 2020-2022 www.xiamiku.com. All Rights Reserved .