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-devel

Re: [Xen-devel] netfront: rx->offset: 12, size: 4294967295

To: Jacek Konieczny <jajcus@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] netfront: rx->offset: 12, size: 4294967295
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Fri, 01 Jun 2007 15:22:03 +0100
Delivery-date: Fri, 01 Jun 2007 07:20:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070601140510.GC9591@xxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcekWDlfd6aIoxBLEdy1xAAX8io7RQ==
Thread-topic: [Xen-devel] netfront: rx->offset: 12, size: 4294967295
User-agent: Microsoft-Entourage/11.3.3.061214


On 1/6/07 15:05, "Jacek Konieczny" <jajcus@xxxxxxxxxx> wrote:

> I recompiled the kernel again and again, with different options (of
> course, I am not able to test all possible configurations) and still no
> go. I am using vanilla 2.6.18 kernel patched with output of Xen's
> 'make mkpatches' and with squashfs (it touches nothing but the
> filesystem).
> 
> Any idea what may be wrong? What else may I try?

Any weird options on your dom0 or domU command lines?

Netback is sending error responses to your domUs, hence the messages you get
from netfront in domU. Have you tried a debug build of Xen, and also
redefine the DPRINTK() macro in netback.c to printk(KERN_ALERT)? This will
very likely get you some tracing per packet about what is going wrong.

 -- Keir


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