Date: Wed, 23 Sep 2015 21:23:34 +0200 From: Martin Birgmeier <la5lbtyi@aon.at> To: Michael Butler <imb@protected-networks.net> Cc: =?UTF-8?Q?Bernhard_Fr=c3=b6hlich?= <decke@bluelife.at>, "freebsd-emulation@freebsd.org" <freebsd-emulation@freebsd.org> Subject: Re: VirtualBox mangles memory Message-ID: <5602FC36.1070805@aon.at> In-Reply-To: <5602ED01.20202@aon.at> References: <55FE9662.7000406@aon.at> <1442866256.1127084.389759513.29E96282@webmail.messagingengine.com> <56017026.6040809@aon.at> <CAE-m3X1eZww8FGu1kTmUwn7dyQNXjXySgHO=WRsGEbJKvWL=AA@mail.gmail.com> <5601AB71.9000003@aon.at> <CA%2BtpaK1w=KM93roeecF30Gvgva_sofGCwuDGOWn44y2O2L5x9Q@mail.gmail.com> <5601C0B8.4000905@protected-networks.net> <5602ED01.20202@aon.at>
next in thread | previous in thread | raw e-mail | index | archive | help
In https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195970, Larry Rosenman suggested setting net.graph.maxdata=8192. I set it to 4096, and the problem seems to have gone away (I am currently testing, and it has not failed so far). This is actually mentioned in https://wiki.freebsd.org/VirtualBox/Tuning, but I would never have guessed that the standard network stack is affected by setting this tunable: I am not copying anything in/out of the VB client, but rather run a completely independent regular IPv4 transfer alongside it. Maybe the description there could be expanded accordingly. Anyway, thanks to Larry for pointing me in the right direction. -- Martin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5602FC36.1070805>