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] domU network data payload corruption

To: Saku Ytti <saku+xen-devel@xxxxxxx>
Subject: Re: [Xen-devel] domU network data payload corruption
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Thu, 9 Feb 2006 17:03:49 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 09 Feb 2006 17:08:54 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20060209163407.GA26540@xxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20060209163407.GA26540@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 9 Feb 2006, at 16:34, Saku Ytti wrote:

Any clue what might be causing this? Reloading domU doesn't help, but
if I reload dom0 domU can be ok for long time (upgraded debian/unstable
etc) but after some time and especially after adding more domU it
seems always trigger at least after adding 3rd domU and then hits
also to the earlier domU's.

I'm happy to provide any information required, I'm using forcedeth
NIC driver in dom0.

How much RAM does your system have? Are you running 32-bit, PAE, or 64-bit? What does the Ethernet driver print out during boot (may tell us what sub-version forcedeth you have)?

 -- Keir

Xen-devel mailing list