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] Re: Dom0 to DomU and reverse works but Outside world to

To: James Harper <james.harper@xxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] Re: Dom0 to DomU and reverse works but Outside world toDomU only ping works
From: Vikas <kedia.vikas@xxxxxxxxx>
Date: Mon, 19 Jan 2009 18:26:03 -0600
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 19 Jan 2009 16:26:53 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=a2LuwX3Fle8foaDXSTemkW/PBb2Gh3r9eRicOfGEQpc=; b=QVcMepy5Lc6ksZJjrbihe91dma6d8zPQcWYPsFkGENwpFantCvF9LgM3ERUeIX5W9J 6xnu2YpJjc8Y0ykp6ctQ4fWbGnCT+uSCftIQ8ZnfpZnnbNibDsbDyoERi84gkQKuw7Hd lXuTa1KOxt336mck9OJT1lTAO/XCGuy4nQ+CM=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=o9e0bnkBtR09P6kohm0A4aVQVXjImmHkjC66ArCviqzSIqTlIdQ4gMl9OoCD1O53wg 6dEmyaRyLS/eEEVBPsljw8DkFQTWBgHdpm1WaOhnLImIMgHUICRjddGg6Uu+dWm88BsQ dlap1BYSjWLlXjMLISkmlGeC5LEWSXIj66zD0=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D0155041C@trantor>
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <fbe022af0901181049w4890db10t8f6ff78e81a47e84@xxxxxxxxxxxxxx> <fbe022af0901191555x6c5c0801w3e50a2bc57b545df@xxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D0155041C@trantor>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Is it ok to run a production machine with tx checsum stopped in the DomU ?

Thanks,
--
sysadmin
http://www.debtconsolidationcare.com

On Mon, Jan 19, 2009 at 6:24 PM, James Harper
<james.harper@xxxxxxxxxxxxxxxx> wrote:
>>
>> For others who might get stuck in the similar situation, the solution
>> was to stop tx checsum in the DomU
>>
>> $ethtool -K eth0 tx off
>>
>> I am wondering why do I need to do this ?
>>
>
> This is a common problem, and appears to be related to bugs in one or
> more of:
> . Xen frontend network driver (unlikely)
> . Xen backend network driver
> . Linux bridge code
> . Linux routing code
> . Linux physical NIC adapter
>
> I suspect it is the last one, but it's complicated enough that the bug
> could lie elsewhere but only show up on certain NIC's.
>
> You can be thankful that your problem was consistent. I have a setup
> where the packets from DomU are routed in Dom0 to one of 6 GRE tunnels,
> and occasionally for 30 minutes or so TCP packets stopped working. Took
> me ages to figure out that turning off tx checksum offload in the DomU
> would resolve the problem. It was made harder because by the time I
> could connect to the client to investigate, it had started working again
> so all I could do was to set up tcpdumps of some fairly high volume
> links and wade through those based on the times that the problem was
> occurring...
>
> James
>

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