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

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

RE: [Xen-users] [Xen-devel] HELP! LOSING NETWORK CONNECTION after XENDST

from [wei huang] [Permanent Link][Original]
To: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
Subject: RE: [Xen-users] [Xen-devel] HELP! LOSING NETWORK CONNECTION after XENDSTART (fwd)
From: wei huang <huanwei@xxxxxxxxxxxxxxxxxx>
Date: Mon, 18 Jul 2005 10:36:52 -0400 (EDT)
Cc: ian.pratt@xxxxxxxxxxxx, Xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 18 Jul 2005 14:35:39 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <A95E2296287EAD4EB592B5DEEFCE0E9D282695@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
Hi,

Thanks for your suggestion. Unfortunately, they don't seem working in my
case. I have attached some more information, hope you can help find some
clues here:

After I do ' /etc/xen/scripts/network stop', the network starts working,
and this is the result of brctl show:
bridge name     bridge id               STP enabled     interfaces
xen-br0         8000.000000000000       no               can't get port
                                                        info: Function not
                                                        implemented

Then I do '/etc/xen/scripts/network start', the network dies again, and
this is the result of brctl show:
bridge name     bridge id               STP enabled     interfaces
xen-br0         8000.feffffffffff       no              eth0
                                                        vif0.0
By the way, I got following error when I do start:
*network start bridge=xen-br0 netdev=eth0 antispoof=yes
iptables: No chain/target/match by that name

No use to remove eth0 and add it again. And it seems that I cannot unload
tg3 module between that. No matter I do 'rmmod tg3' or 'rmmod -f tg3', the
module is still there ...

What is more, if I try to ssh to some other machine after the network
dies, I got following errors prompting on my screen:
vif0.0: received packet with  own address as source address

Do you have any further suggestions? Thank you very much!

Regards,
Wei Huang

>
> > I am using the latest xen-unstable by Jul. 15th. Everything
> > is dom0 works
> > fine. But as soon as I input 'xend start', all the network connections
> > just die.
>
> There's a bug on the bugzilla that sounds a lot like this.
>
> When its in the bad state, please can you try putting eth0 into
> 'promisc' mode e.g.
>
>  ifconfig eth0 promisc up
>
> The other thing to try is using brctl to remove eth0 from the bridge and
> then re-add it.
>
> If that doesn't work, try running
>  /etc/xen/scripts/network stop
>  /etc/xen/scripts/network start
>
> You could also try unloading the modulefor your network card between the
> two.
>
> If any of these work we'll have a better idea of what is going on.
>
> Ian
>
> > I am using Broadcom NetXtreme network card, with tg3 driver.
> >
> > I have collected some basic information and post it in the
> > following part.
> > I remember some one seems to meet the same problem before,
> > and I try to
> > find the solution is that thread, but no luck.
> >
> > Could anyone give any help? Thanks.
> >
> > ======================================================================
> > Result for ifconfig:
> >
> > BEFORE xend start:
> > eth0      Link encap:Ethernet  HWaddr 00:0D:60:9A:15:60
> >           inet addr:9.2.72.112  Bcast:9.2.72.127  Mask:255.255.255.128
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:89 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:83 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:1000
> >           RX bytes:14402 (14.0 KiB)  TX bytes:7781 (7.5 KiB)
> >           Interrupt:16
> >
> > 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:16 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0
> >           RX bytes:1168 (1.1 KiB)  TX bytes:1168 (1.1 KiB)
> > AFTER xend start:
> > eth0      Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
> >           UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
> >           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:1000
> >           RX bytes:0 (0.0 b)  TX bytes:576 (576.0 b)
> >           Interrupt:16
> >
> > 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:16 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0
> >           RX bytes:1168 (1.1 KiB)  TX bytes:1168 (1.1 KiB)
> >
> > veth0     Link encap:Ethernet  HWaddr 00:0D:60:9A:15:60
> >           inet addr:9.2.72.112  Bcast:9.2.72.127  Mask:255.255.255.128
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0
> >           RX bytes:0 (0.0 b)  TX bytes:552 (552.0 b)
> >
> > vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:6 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0
> >           RX bytes:552 (552.0 b)  TX bytes:0 (0.0 b)
> >
> > xen-br0   Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:6 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0
> >           RX bytes:468 (468.0 b)  TX bytes:0 (0.0 b)
> >
> >
> > =================================================================
> > Result for 'ip route show'
> > BEFORE xend start:
> > 9.2.72.0/25 dev eth0  proto kernel  scope link  src 9.2.72.112
> > 169.254.0.0/16 dev eth0  scope link
> > default via 9.2.72.1 dev eth0
> > AFTER:
> > 9.2.72.0/25 dev veth0  proto kernel  scope link  src 9.2.72.112
> > 169.254.0.0/16 dev veth0  scope link
> > default via 9.2.72.1 dev veth0
> >
> > =================================================================
> > Result for 'ip addr show'
> > BEFORE:
> > 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
> >     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> >     inet 127.0.0.1/8 scope host lo
> > 2: vif0.0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
> >     link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
> > 3: veth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
> >     link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
> > 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
> >     link/ether 00:0d:60:9a:15:60 brd ff:ff:ff:ff:ff:ff
> >     inet 9.2.72.112/25 brd 9.2.72.127 scope global eth0
> > 5: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
> >     link/ether 00:0d:60:9a:15:61 brd ff:ff:ff:ff:ff:ff
> > AFTER:
> > 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
> >     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> >     inet 127.0.0.1/8 scope host lo
> > 2: vif0.0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
> >     link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
> > 3: veth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
> >     link/ether 00:0d:60:9a:15:60 brd ff:ff:ff:ff:ff:ff
> >     inet 9.2.72.112/25 brd 9.2.72.127 scope global veth0
> > 4: eth0: <BROADCAST,MULTICAST,NOARP,UP> mtu 1500 qdisc pfifo_fast qlen
> > 1000
> >     link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
> > 5: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
> >     link/ether 00:0d:60:9a:15:61 brd ff:ff:ff:ff:ff:ff
> > 6: xen-br0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
> >     link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
> >
> > =====================================================================
> > Result for "route -n"
> > BEFORE:
> > Kernel IP routing table
> > Destination     Gateway         Genmask         Flags Metric
> > Ref    Use  Iface
> > 9.2.72.0        0.0.0.0         255.255.255.128 U     0
> > 0        0   eth0
> > 169.254.0.0     0.0.0.0         255.255.0.0     U     0
> > 0        0   eth0
> > 0.0.0.0         9.2.72.1        0.0.0.0         UG    0
> > 0        0   eth0
> > AFTER:
> > Kernel IP routing table
> > Destination     Gateway         Genmask         Flags Metric
> > Ref    Use Iface
> > 9.2.72.0        0.0.0.0         255.255.255.128 U     0
> > 0        0  veth0
> > 169.254.0.0     0.0.0.0         255.255.0.0     U     0
> > 0        0  veth0
> > 0.0.0.0         9.2.72.1        0.0.0.0         UG    0
> > 0        0  veth0
> >
> > ======================================================================
> > xm log after xend start: (last few lines)
> > 2005-07-15 17:14:44 xend] DEBUG (XendDomainInfo:177) config='None'
> >
> > [2005-07-15 17:14:44 xend] INFO (SrvServer:63) unix
> > path=/var/lib/xend/xend-socket
> > [2005-07-15 17:14:44 xend] INFO (XendRoot:128) EVENT> xend.start 0
> > [2005-07-15 17:14:44 xend] INFO (process:35) [network] network start
> > bridge=xen-br0 netdev=eth0 antispoof=no
> >
> > ==============================================================
> > =========
> > dmesg after xend start:
> > device vif0.0 entered promiscuous mode
> > xen-br0: port 1(vif0.0) entering learning state
> > xen-br0: topology change detected, propagating
> > xen-br0: port 1(vif0.0) entering forwarding state
> > device eth0 entered promiscuous mode
> > tg3: eth0: Link is up at 100 Mbps, full duplex.
> > tg3: eth0: Flow control is off for TX and off for RX.
> > xen-br0: port 2(eth0) entering learning state
> > xen-br0: topology change detected, propagating
> > xen-br0: port 2(eth0) entering forwarding state
> >
> >
> >
> >
> > Regards,
> > Wei
> >
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-devel
> >
> >
> > _______________________________________________
> > 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
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  [Xen-users] Unable to communicate with Dom0, Subhabrata Bhattacharya
Next by Date:  Re: [Xen-users] hidden eth1, how to use in DomU?, JIT LEISHANGTHEM
Previous by Thread:  RE: [Xen-users] [Xen-devel] HELP! LOSING NETWORK CONNECTION after XENDSTART (fwd), Ian Pratt
Next by Thread:  [Xen-users] 2.6.12-xenU hangs at boot, tl2
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy