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


Re: [Xen-devel] pv_ops network problem: Attempting to checksu

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] pv_ops network problem: Attempting to checksum a non-TCP/UDP packet, dropping a protocol 1 packet
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Thu, 27 May 2010 17:08:22 +0300
Cc: Gerry Reno <greno@xxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, andreas.olsowski@xxxxxxxxxxxxxxx
Delivery-date: Thu, 27 May 2010 07:09:32 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4BF456F9.8090606@xxxxxxxx>
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>
References: <4BF45370.8030406@xxxxxxxxxxx> <4BF456F9.8090606@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Wed, May 19, 2010 at 02:24:09PM -0700, Jeremy Fitzhardinge wrote:
> On 05/19/2010 02:09 PM, Gerry Reno wrote:
> > I am using a pv_ops dom0 kernel with xen 4.0.0-rc8.  My
> > domU's use 2.6.31-14-server ubuntu.
> >
> > When I try to ping another computer on the network from the domU I
> > still received this error:
> > Attempting to checksum a non-TCP/UDP packet, dropping a protocol 1 packet
> >
> > I thought this error was fixed somewhere around but
> > apparently it is still in
> >
> > How do I get around this problem?
> I applied a patch to fix up a checksum bug in netback, but I realized I
> hadn't applied it to stable-2.6.32.  Please try again (it will be
> and tell me how it goes.

Is this fix missing from xen/master (aka xen/stable-2.6.31.x) aswell?

There was an user complaining about this bug on ##xen (CC) and he said he was 
the latest xen/master.. he grabbed the patch from xen/stable-2.6.32.x and 
it to his 2.6.31 tree and it started to work OK after that.

-- Pasi

Xen-devel mailing list