This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] xen "set encode" (8b2a) problem

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] xen "set encode" (8b2a) problem
From: Zhenhua Du <zdu@xxxxxxxxxxx>
Date: Fri, 18 Dec 2009 17:59:07 +0800 (CST)
Delivery-date: Fri, 18 Dec 2009 01:59:51 -0800
Domainkey-signature: a=rsa-sha1; s=dk-2008-12; d=ablesky.com; c=simple; q=dns; h=date:from:to:message-id:subject:mime-version:content-type: content-transfer-encoding:x-originating-ip:x-mailer; b=AL9ejQ1d5J44SjiqfNFubLoZJw2iBZ1Aq3UL0Nil8onXLN5h89S452o77h1mNfdmF Pm50Hzl1TEuul3UsbjieQ==
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi my friends,
I am running into a problem with my NIC.

[root@xxxx ~]# ifup eth0
Error for wireless request "Set Encode" (8B2A) :
SET failed on device eth0 ; No such device.
SIOCGIFFLAGS: No such device
Failed to bring up eth0.

eth0 is not a wireless device. Below are some information about my host:

[root@xxxx ~]# lspci |grep -i ether
00:04.0 Ethernet controller: Intel Corporation 82541GI Gigabit Ethernet 
Controller (rev 05)
00:05.0 Ethernet controller: Intel Corporation 82541GI Gigabit Ethernet 
Controller (rev 05)

[root@xxxx ~]# uname -a
Linux xxxx.xxxx.com 2.6.18-128.1.10.el5xen #1 SMP Thu May 7 11:07:18 EDT 2009 
x86_64 x86_64 x86_64 GNU/Linux

[root@xxxx ~]# less /etc/grub.conf
# grub.conf generated by anaconda
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/dom0/root
# initrd /initrd-version.img
title CentOS (2.6.18-128.1.10.el5xen)
root (hd0,0)
kernel /xen.gz-3.2
#kernel /xen.gz-3.2 dom0_mem=256M
module /vmlinuz-2.6.18-128.1.10.el5xen ro root=/dev/dom0/root
module /initrd-2.6.18-128.1.10.el5xen.img

I google this problem for a whole day. Someone says it is xen-kernel's problem. 
There are many virtual machines running in this host, so I must use the 

Anyone can help me? Or give me some advice?

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>