Re: [Xen-devel] x86_64 - Networking disabled when starting xend

[David F Barrera <dfbp@xxxxxxxxxx>]

On Thu, 2005-07-14 at 15:50 -0500, David F Barrera wrote:
> 
> When starting xend on an x86_64 machine (IBM HS20 Blade EMT64) with SLES
> 9, networking is completely disabled.  I don't see any trace data or
> error messages coming out, simply when I type in 'xend start' on a
> remote login, the communication stops. On the serial console, I don't
> see any error or Oops,either. I first saw this problem today, July
> 14th. 
> 
> ** Note: the problem is NOT happening on an identical machine that has
> FC4.
> 
> changeset:   5781:98b83cc57eca28c4beff7d76cf0ddf1cc6e2c9da
> tag:         tip
> user:        kaf24@xxxxxxxxxxxxxxxxxxxx
> date:        Thu Jul 14 09:01:21 2005
> summary:     Missing quirks.c file.
Incidentally, I did not mean to point at this changeset; rather, it is
the LAST changeset in the Xen build on my test machine.
> 
> 
> 
> ifconfig before xend start:
> 
> eth1      Link encap:Ethernet  HWaddr 00:11:25:9D:69:87
>           inet addr:9.3.192.194  Bcast:9.3.192.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:2671 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:325 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:420983 (411.1 Kb)  TX bytes:108907 (106.3 Kb)
>           Interrupt:78
> 
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:28 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:2165 (2.1 Kb)  TX bytes:2165 (2.1 Kb)
> 
> 
> Ifconfig after xend start:
> 
> eth1      Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
>           RX packets:635 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:106924 (104.4 Kb)  TX bytes:0 (0.0 b)
>           Interrupt:78
> 
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:36 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:3189 (3.1 Kb)  TX bytes:3189 (3.1 Kb)
> 
> veth0     Link encap:Ethernet  HWaddr 00:11:25:9D:69:87
>           inet addr:9.3.192.194  Bcast:9.3.192.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:21 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:0 (0.0 b)  TX bytes:882 (882.0 b)
> 
> vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF  (garbage after
> this line)
> 
> The network card is a tg3, and I believe I saw some emails exchanged
> regarding some issues with veth0 and tg3
> 
-- 
Regards,

David F Barrera
Linux Technology Center
Systems and Technology Group, IBM

"The wisest men follow their own direction. "
                                                        Euripides


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