From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephan Seitz Subject: Re: Jeremy's GIT-tree and network problems Date: Tue, 30 Mar 2010 14:33:40 +0200 Message-ID: <20100330T1426.GA.a8bba.stse@fsing.rootsland.net> References: <20100329T1647.GA.2c139.stse@fsing.rootsland.net> <4BB0F4A0.2000403@goop.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0760951283==" Return-path: Resent-Message-ID: <20100331060958.GA7822@fsing.rootsland.net> Resent-To: xen-devel@lists.xensource.com In-Reply-To: <4BB0F4A0.2000403@goop.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============0760951283== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/unnNtmY43mpUSKx" Content-Disposition: inline --/unnNtmY43mpUSKx Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Jeremy! On Mon, Mar 29, 2010 at 11:42:40AM -0700, Jeremy Fitzhardinge wrote: >Have you tried carpet-bombing the ethtools: turn off everything on all=20 >the dom0 interfaces (both the bridge(s) and all the component=20 >interfaces) and all the domU interfaces? It does look like some kind of=20 >checksum problem (or perhaps other offload?). Well, the physical interfaces only had RX on. The virtual interfaces in=20 Dom0 and DomU had RX, TX, SG, TSO and GSO on. Trying to switch off RX on=20 the virtual interfaces produced an error message, but after switching off= =20 the other features, RX was off as well. But after everything was off (in Dom0 bridge eth0 with peth0 and vif1.0=20 and bridge xenbr1 with eth1 and vif1.1 and in DomU eth0 and eth1), the=20 setup didn=E2=80=99t start working. So if this is some kind of checksum pro= blem,=20 switching the checksum and offload features off don=E2=80=99t change it. Do you have other suggestions? >Fortunately it looks like this is going to get some systematic=20 >attention. I'd really like any reasonable (ie, not inherently broken for= =20 >other reasons) network setup to just work. I hope so. Anf if there are patches to test, I will test it. Shade and sweet water! Stephan --=20 | Stephan Seitz E-Mail: stse@fsing.rootsland.net | | PGP Public Keys: http://fsing.rootsland.net/~stse/pgp.html | --/unnNtmY43mpUSKx Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkux76QACgkQXse+NwPOAZ6S3wCgoScN8rpj25TtMCriv2ndVJAl VlkAn3S1rEhoFCjgb+ST2g1tHhIUwA2x =FKqs -----END PGP SIGNATURE----- --/unnNtmY43mpUSKx-- --===============0760951283== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============0760951283==--