WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Re: eth1 changed to __tmp78668633 in recent kernels

Am Donnerstag, den 15.05.2008, 07:38 -0400 schrieb Christopher Isip:
> 
> 
> On Thu, May 15, 2008 at 7:22 AM, henry ritzlmayr <xen-list@xxxxxx>
> wrote:
>         Am Donnerstag, den 15.05.2008, 13:06 +0200 schrieb henry
>         ritzlmayr:
>         
>         > Hi list,
>         >
>         > kernel-xen-2.6.18-53.1.14.el5 and
>         > kernel-xen-2.6.18-53.1.19.el5
>         > do not detect/initialize/whatever my eth1 network card any
>         more.
>         >
>         > With
>         > kernel-xen-2.6.18-53.1.13.el5
>         > everything is working as expected.
>         >
>         > With the two recent kernels I only get an Interface named
>         __tmp786686833
>         > which is not added to xenbr...
>         >
>         > lspci -v to the adapter in question says
>         >
>         > 02:00.0 Ethernet controller: Intel Corporation 82572EI
>         Gigabit Ethernet
>         > Controller (Copper) (rev 06)
>         >         Subsystem: Intel Corporation PRO/1000 PT Desktop
>         Adapter
>         >         Flags: bus master, fast devsel, latency 0, IRQ 17
>         >         Memory at febe0000 (32-bit, non-prefetchable)
>         [size=128K]
>         >         Memory at febc0000 (32-bit, non-prefetchable)
>         [size=128K]
>         >         I/O ports at ec00 [size=32]
>         >         Expansion ROM at feba0000 [disabled] [size=128K]
>         >         Capabilities: [c8] Power Management version 2
>         >         Capabilities: [d0] Message Signalled Interrupts:
>         64bit+
>         > Queue=0/0 Enable-
>         >         Capabilities: [e0] Express Endpoint IRQ 0
>         >
>         > ip link says
>         >
>         > 2: __tmp786686833: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
>         qlen 1000
>         >     link/ether 00:1b:21:0e:a9:3b brd ff:ff:ff:ff:ff:ff
>         >
>         > In modprobe.conf I have
>         > alias eth1 e1000
>         > for the adapter in question. The module itself is loaded.
>         >
>         >
>         >
>         > Any Ideas how to fix this?
>         >
>         > cheers
>         > Henry
>         
>         
>         Sorry for the noise - this should have gone into the CentOS
>         List.
>         
>         
>         cheers
>         Henry
>         
>         
>         
>         _______________________________________________
>         Xen-users mailing list
>         Xen-users@xxxxxxxxxxxxxxxxxxx
>         http://lists.xensource.com/xen-users
>         
> 
> 
> 
> I think the creation of a temporary bridge is a result of xend
> failing.  Try to delete the var/lib/xend/state directory, reboot and
> restart xend.  That worked for me.
> 
> Chris

Thanks for the reply,

I have no /var/lib/xend/state directory under CentOS5 but you idea of
xend causing the trouble got me into some further digging. Now it gets
odd: I found a solution by disabling the start of xend in runlevel 2.
With this configuration every kernel works as expected. As soon I enable
xend in runlevel 2 again - only the older kernel works. I will post this
in the CentOS list as well since I think it is more related to the
distribution than to xen per se. 

thanks again
Henry 



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

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