WARNING - OLD ARCHIVES

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

xen-users

Re: [Xen-users] Network problem: packets are lost in domU

To: Jacek Konieczny <jajcus@xxxxxxxxxx>
Subject: Re: [Xen-users] Network problem: packets are lost in domU
From: Christophe Saout <christophe@xxxxxxxx>
Date: Mon, 26 Feb 2007 00:49:46 +0100
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 25 Feb 2007 15:49:11 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070222140906.GA9640@xxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <20070222140906.GA9640@xxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

> I am using Xen 3.0.4-1 and Linux 2.6.16.x in both dom0 and domU.
> I have tried kernel 2.6.16.35 and 2.6.16.41. 
> I have compiled the kernel and xen with PAE support and without it,
> using gcc 3.3 and gcc 4.2 (snapshot). I have played with various kernel
> compilation options. No luck: the same problem in every case.
> 
> [...]
>
> And there are errors in dmesg of domU for each package lost this way:
> 
> netfront: rx->offset: 12, size: 4294967295
> netfront: rx->offset: 12, size: 4294967295
> netfront: rx->offset: 12, size: 4294967295
> netfront: rx->offset: 12, size: 4294967295
> [...]
> 
> No other suspicious messages in dmesg of domU, nothing worying in dmesg
> of dom0.

I have the exact same problem. I just wanted to upgrade to 2.6.19 +
3.0.4 from the Fedora development and boom, same problem.

It works when I use my old Dom0 (2.6.18 + 3.0.3) with 3.0.4 guests. The
only visible difference is that with the new (broken) Dom0, the guests
are using the "copying receive path" while with the working old Dom0
they are using the "flipping receive path".

This smells like a serious bug in the netback or netfront driver in the
copying receive path.

I don't know what can trigger this, but my configuration is:

Dom0: xenbr0 with one netloop attached (int0) and several vif#.0 for
DomU's (no physical network card attached, done via routing on Dom0).

4294967295 is -1 writted as unsigned, which indicates some sort of error
state in the code, but I don't know from where that one might come.



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>