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


[mdlabriola@xxxxxxxxx: [Xen-devel] Re: Re: [Xen-users] DomU routed traff

To: mdlabriola@xxxxxxxxx, zary@xxxxxxxxx
Subject: [mdlabriola@xxxxxxxxx: [Xen-devel] Re: Re: [Xen-users] DomU routed traffic disappearing in vif.]
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Mon, 10 May 2010 11:18:35 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 10 May 2010 08:24:41 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.19 (2009-01-05)
> On Sat, 2010-05-08 at 02:53 +0200, Matej Zary wrote:
> > Hello,
> > 
> > 
> > XEN 4.0 with pvops Dom0 kernel. Configured PV DomU with the same 
> > pvops Xen kernel on top of it.
> > 
> > Physical computers has 3 NICs - every NIC in own bridge (first one created 
> > by Xen).
> > 
> > eth0                8000.00138fe78f1b       no              peth0
> > mst1                8000.0040f4b5286e       no              eth1
> >                                                     vif5.0
> > mst2                8000.000e2e68db10       no              eth2
> >                                                     vif5.1
> > 
> > Attached 2 virtual NICs to the PV DomU and bridges - I want to use that 
> > DomU as router between that two bridges (enabled ip_forwarding in DomU) - 
> > mst1 and mst2.
> > 
> > I can ping from netwok on eth1 the vif5.0 interface.
> > I can ping from network on eth2 the vif5.1 interface.
> > I can see with tcpdump, that the DomU routes the traffic between its eth0 
> > and eth1 interfaces (tcpdump inside the domu).
> > I can see with tcpdump the incoming traffic in mst1 and vif5.0.
> > But there's nothing on the vif5.1and mst2 bridge - even when tcpdump on the 
> > eth1 in that PV DomU shows the routed traffic ("works"  the same in 
> > opposite direction too).
> > 
> > Looks like all traffic routed by that PV DomU cant't get from DomU eth 
> > interface to the vif interface. Ping from the DomU works (non routed 
> > traffic), but no routed traffic can get thu this Dom0.
> > 
> > IPltables flushed with -F 
> > 
> > Thanks for every idea, i'm clueless right now. :(
> > 
> > Regars 
> > 
> > Matej
> Well, it's the dreaded cksum incorrect error (and Real(BAD)tek PCI
> NICs). Tried to set off the tx check-summing on all interfaces (eth
> interfaces in DomU, eth and bridge interfaces in Dom0) with ethtool -K
> iface tx off, and it changed the situation a little bit - now are these
> packets with incorrect checksum visible on the outgoing eth2 physical
> NIC in the mst2 bridge and also on physical host in the physical network
> connected to mst2 bridge via the eth2 NIC. Final result ist still the
> same, physical hosts routed via the DomU can't communicate (now they are
> getting packets with wrong checksum at least :D). 
> Any chances that newer pv_ops kernel that the (git stable)
> version will solve this issue? Or I have to switch to the 2.6.18 and the
> forwardported oldstyle kernels? 

Ian had a patch that he backported from XCP that might fix this, not
sure thought. Jeremy is trying it out but he ran in some other issues
(pvgrub messing up UDP checksums). Stay tuned.

Xen-devel mailing list