Re: xn_txeof: WARNING: response is -1!
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-unsubscr...@freebsd.org
Re: xn_txeof: WARNING: response is -1!
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 h...@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-unsubscr...@freebsd.org ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Re: xn_txeof: WARNING: response is -1!
On 05/29/11 14:11, K. Macy wrote: 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. Hello, I'm not sure about Linux but a NetBSD 5.1 PV domU works fine. Others are running Linux PV on NetBSD afaik. Maybe http://www.freebsd.org/cgi/query-pr.cgi?pr=143340 is the same issue? (it may be of interest to note that pr is still open - maybe the patch does work and one less pr to worry about :)) I do get packet corrupt until txc and rxc are disabled, with both off then the xn_txeof warning is logged and the ssh connection seems to hang. Couldn't apply the patch in the link, the text appears to be mangled. I tried to correct it, but no luck. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
Re: xn_txeof: WARNING: response is -1!
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. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
