James Dingwall
2008-Jun-27 08:24 UTC
[Xen-users] Network Bridge Fails After 3.1.3 -> 3.2.1 Upgrade
Hi, I''m running a Gentoo system using the 2.6.21-xen sources available in portage. The system has run reliably with 3.0 and 3.1 versions of Xen but now trying to upgrade to 3.2 I am facing some problems. I am letting Xen control the creation of the network bridge and this happens without a problem and when I start domUs they initially work without a problem. Unfortunately after a short time networking to the domU fails, dom0 remains ok. I have a broadcom network interface which is built on to the motherboard, ethtool -i reports: driver: tg3 version: 3.75.2 firmware-version: 5703-v2.33 bus-info: 0000:02:09.0 I have seen reports of issues with broadcom interfaces not working and that ethtool -K tx off rx off resolves them but this does not work in my case. Any suggestions on things to look at are welcome, let me know if any more information is required. Thanks, James This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
James Dingwall
2008-Jul-22 07:49 UTC
RE: [Xen-users] Network Bridge Fails After 3.1.3 -> 3.2.1 Upgrade
Let me start by apologising for reviving an old thread and for replying
to myself but I have some more information on this so perhaps I can get
to the bottom of the problem...
I am still running 3.1.3 because of the problems described below but I
have recently tried to migrate to init script created bridges. I
changed the network-bridge script in the xend config to just call a
dummy script and configured conf.d/net to create the bridge (breth0).
Unfortunately this demonstrates the same behaviour which I observed on
upgrading to 3.2.1. From this I can only conclude that the Xen bridge
scripts are doing something differently which stops the bridge dying
after a period of time but this changes between 3.1.3 and 3.2.1.
The output from the Gentoo created bridge (brctl show, ip show link)
bridge name bridge id STP enabled interfaces
breth0 8000.00e0812be348 no eth0
15: breth0: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
link/ether 00:e0:81:2b:e3:48 brd ff:ff:ff:ff:ff:ff
and the Xen created
bridge name bridge id STP enabled interfaces
xenbr0 8000.feffffffffff no vif0.0
peth0
15: xenbr0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
The differences that I see are in the bridge id and that the Xen bridge
as NOARP in the link. Would either of these differences explain the
behaviour I see?
Thanks,
James
I''m running a Gentoo system using the 2.6.21-xen sources available in
portage. The system has run reliably with 3.0 and 3.1 versions of Xen
but now trying to upgrade to 3.2 I am facing some problems. I am
letting Xen control the creation of the network bridge and this happens
without a problem and when I start domUs they initially work without a
problem. Unfortunately after a short time networking to the domU fails,
dom0 remains ok. I have a broadcom network interface which is built on
to the motherboard, ethtool -i reports:
driver: tg3
version: 3.75.2
firmware-version: 5703-v2.33
bus-info: 0000:02:09.0
I have seen reports of issues with broadcom interfaces not working and
that ethtool -K tx off rx off resolves them but this does not work in my
case. Any suggestions on things to look at are welcome, let me know if
any more information is required.
# ethtool -k peth0
Offload parameters for peth0:
Cannot get device udp large send offload settings: Operation not
supported
rx-checksumming: on
tx-checksumming: on
scatter-gather: on
tcp segmentation offload: off
udp fragmentation offload: off
generic segmentation offload: off
This message and the information contained herein is proprietary and
confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Fajar A. Nugraha
2008-Jul-22 08:00 UTC
Re: [Xen-users] Network Bridge Fails After 3.1.3 -> 3.2.1 Upgrade
James Dingwall wrote:> The output from the Gentoo created bridge (brctl show, ip show link) > bridge name bridge id STP enabled interfaces > breth0 8000.00e0812be348 no eth0 > > 15: breth0: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue > link/ether 00:e0:81:2b:e3:48 brd ff:ff:ff:ff:ff:ff > >In this scenario : - your eth0 should be up, no ip address - breth0 should be up, have an ip address (optional, if your dom0 needs it) in your example it seems like breth0 is missing an ip address. Is this intentional? What are the relevant entries in syslog when the bridge stops working? What is the status of eth0 (up, ip address?) -- Fajar> and the Xen created > > bridge name bridge id STP enabled interfaces > xenbr0 8000.feffffffffff no vif0.0 > peth0 > > 15: xenbr0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue > link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff > > > The differences that I see are in the bridge id and that the Xen bridge > as NOARP in the link. Would either of these differences explain the > behaviour I see? > > Thanks, > James > > > > I''m running a Gentoo system using the 2.6.21-xen sources available in > portage. The system has run reliably with 3.0 and 3.1 versions of Xen > but now trying to upgrade to 3.2 I am facing some problems. I am > letting Xen control the creation of the network bridge and this happens > without a problem and when I start domUs they initially work without a > problem. Unfortunately after a short time networking to the domU fails, > dom0 remains ok. I have a broadcom network interface which is built on > to the motherboard, ethtool -i reports: > > driver: tg3 > version: 3.75.2 > firmware-version: 5703-v2.33 > bus-info: 0000:02:09.0 > > I have seen reports of issues with broadcom interfaces not working and > that ethtool -K tx off rx off resolves them but this does not work in my > case. Any suggestions on things to look at are welcome, let me know if > any more information is required. > > # ethtool -k peth0 > Offload parameters for peth0: > Cannot get device udp large send offload settings: Operation not > supported > rx-checksumming: on > tx-checksumming: on > scatter-gather: on > tcp segmentation offload: off > udp fragmentation offload: off > generic segmentation offload: off > > This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, > you may review at http://www.amdocs.com/email_disclaimer.asp > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
James Dingwall
2008-Jul-22 08:29 UTC
RE: [Xen-users] Network Bridge Fails After 3.1.3 -> 3.2.1 Upgrade
James Dingwall wrote:> The output from the Gentoo created bridge (brctl show, ip show link) > bridge name bridge id STP enabled interfaces > breth0 8000.00e0812be348 no eth0 > > 15: breth0: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue > link/ether 00:e0:81:2b:e3:48 brd ff:ff:ff:ff:ff:ff > >In this scenario : - your eth0 should be up, no ip address - breth0 should be up, have an ip address (optional, if your dom0 needs it) in your example it seems like breth0 is missing an ip address. Is this intentional? What are the relevant entries in syslog when the bridge stops working? What is the status of eth0 (up, ip address?) The IP for the bridge is assigned correctly. The bridge functions correctly at boot (I can ssh in to domU) and then dies after some time. My logs show successful NFS mounts of a dom0 export for ~9 hours before it stops. James> and the Xen created > > bridge name bridge id STP enabled interfaces > xenbr0 8000.feffffffffff no vif0.0 > peth0 > > 15: xenbr0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue > link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff > > > The differences that I see are in the bridge id and that the Xenbridge> as NOARP in the link. Would either of these differences explain the > behaviour I see? > > Thanks, > James > > > > I''m running a Gentoo system using the 2.6.21-xen sources available in > portage. The system has run reliably with 3.0 and 3.1 versions of Xen > but now trying to upgrade to 3.2 I am facing some problems. I am > letting Xen control the creation of the network bridge and thishappens> without a problem and when I start domUs they initially work without a > problem. Unfortunately after a short time networking to the domUfails,> dom0 remains ok. I have a broadcom network interface which is builton> to the motherboard, ethtool -i reports: > > driver: tg3 > version: 3.75.2 > firmware-version: 5703-v2.33 > bus-info: 0000:02:09.0 > > I have seen reports of issues with broadcom interfaces not working and > that ethtool -K tx off rx off resolves them but this does not work inmy> case. Any suggestions on things to look at are welcome, let me knowif> any more information is required. > > # ethtool -k peth0 > Offload parameters for peth0: > Cannot get device udp large send offload settings: Operation not > supported > rx-checksumming: on > tx-checksumming: on > scatter-gather: on > tcp segmentation offload: off > udp fragmentation offload: off > generic segmentation offload: off > > This message and the information contained herein is proprietary andconfidential and subject to the Amdocs policy statement,> you may review at http://www.amdocs.com/email_disclaimer.asp > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users