[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] xen "set encode" (8b2a) problem
On 18/12/09 10:48, Zhenhua Du wrote: More Information This host has two NICs. Eth0 is default bridge for virtual machines. I don't use Eth1. I did a test about this problem. When eth1 is the default bridge of virtual machines, eth1 will have the same problem. Take a close look at /etc/sysconfig/network-scripts/ifcfg-eth0 -- I suspect it has some wireless device settings. -----Original Message----- From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Zhenhua Du Sent: 2009å12æ18æ 17:59 To: xen-users@xxxxxxxxxxxxxxxxxxx Subject: [Xen-users] xen "set encode" (8b2a) problem 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 #boot=/dev/md0 default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu 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 xen-kernel. Anyone can help me? Or give me some advice? _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |