From owner-freebsd-xen@FreeBSD.ORG Tue May 24 20:15:15 2011 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B586106566B for ; Tue, 24 May 2011 20:15:15 +0000 (UTC) (envelope-from hugo@barafranca.com) Received: from mail.barafranca.com (mail.barafranca.com [67.213.67.47]) by mx1.freebsd.org (Postfix) with ESMTP id EEE008FC12 for ; Tue, 24 May 2011 20:15:14 +0000 (UTC) Received: from localhost (unknown [172.16.100.24]) by mail.barafranca.com (Postfix) with ESMTP id 1DC2E5CF for ; Tue, 24 May 2011 20:15:14 +0000 (UTC) X-Virus-Scanned: amavisd-new at barafranca.com Received: from mail.barafranca.com ([172.16.100.24]) by localhost (mail.barafranca.com [172.16.100.24]) (amavisd-new, port 10024) with ESMTP id J33XogD850PM for ; Tue, 24 May 2011 20:14:35 +0000 (UTC) Received: from [192.168.1.1] (a94-132-1-126.cpe.netcabo.pt [94.132.1.126]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.barafranca.com (Postfix) with ESMTPSA id 592055CC for ; Tue, 24 May 2011 20:14:35 +0000 (UTC) Message-ID: <4DDC11AA.6030106@barafranca.com> Date: Tue, 24 May 2011 21:14:34 +0100 From: Hugo Silva User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-xen@freebsd.org References: <4DDBB66F.6030608@barafranca.com> In-Reply-To: <4DDBB66F.6030608@barafranca.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: xn_txeof: WARNING: response is -1! X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 May 2011 20:15:15 -0000 On 05/24/11 14:45, Hugo Silva wrote: > Trying to ssh to the VM produces the error in the subject line on the > FreeBSD domU; It's impossible to login. > Some more information for those looking to reproduce this: the above is with rxcsum and txcsum disabled in the xn interface: Without that, the ssh client on the other side would just say 'Disconnected: Packet corrupt'. With tx/rxsum disabled, the ssh client will seem to hang, while the server spits the xn_txeof message. I seem to recall that disabling TSO helped fix a similar error under Citrix XenServer, but alas. No difference.