From mboxrd@z Thu Jan 1 00:00:00 1970 From: Saku Ytti Subject: Re: domU network data payload corruption Date: Thu, 9 Feb 2006 19:23:49 +0200 Message-ID: <20060209172349.GA26911@ytti.fi> References: <20060209163407.GA26540@ytti.fi> <20060209170755.GC26540@ytti.fi> <16ef2083feb31b5140e53a88977cd787@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <16ef2083feb31b5140e53a88977cd787@cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On (2006-02-09 17:26 +0000), Keir Fraser wrote: > Hopefully you are building your own kernels. If so, try modifying the I am, due to need for areca support. > Linux file drivers/net/forcedeth.c. There is a line like this: > define DEV_HAS_HIGH_DMA 0x0008 > Try changing the 0x0008 to 0 > > I think this will probably work better for you. :-) Will try. Btw. just found vortex and the issue is not present there, will try installing 4th domU while three domU's are running and after that I'll try the change your suggesting and report back. Thanks, -- ++ytti