Date: Sun, 29 May 2011 15:11:09 +0200 From: "K. Macy" <kmacy@freebsd.org> To: Hugo Silva <hugo@barafranca.com> Cc: freebsd-xen@freebsd.org Subject: Re: xn_txeof: WARNING: response is -1! Message-ID: <BANLkTimU-oqGh7uQhOMotX97CgJ7sjaeZA@mail.gmail.com> In-Reply-To: <4DE227B5.6000903@barafranca.com> References: <4DDBB66F.6030608@barafranca.com> <4DDC11AA.6030106@barafranca.com> <4DDD2C41.2000302@barafranca.com> <4DE227B5.6000903@barafranca.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Just to verify, other guests (e.g. Linux || NetBSD) don't exhibit this problems? It sounds almost as if xend isn't configuring the domain properly. -Kip On Sun, May 29, 2011 at 1:02 PM, Hugo Silva <hugo@barafranca.com> wrote: > On 05/25/11 17:20, Hugo Silva wrote: >> On 05/24/11 21:14, Hugo Silva wrote: >>> 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. >> >> Same thing with i386 and full PV. > > Just tested, also in current. > _______________________________________________ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTimU-oqGh7uQhOMotX97CgJ7sjaeZA>