Date: Thu, 14 Jul 2011 00:05:09 -0500 From: Adam Vande More <amvandemore@gmail.com> To: Peter Ross <Peter.Ross@bogen.in-berlin.de> Cc: freebsd-emulation@freebsd.org Subject: Re: Network problems while running VirtualBox Message-ID: <CA%2BtpaK18s2wHEM%2BJ-vP9egZPu10wZHFAuxvShhzFWOwVfZ9Miw@mail.gmail.com> In-Reply-To: <CA%2BtpaK3GfLnWDWnS77m_yPoU6AWeFqS8Vusv_g6oPJ=_Voju%2BQ@mail.gmail.com> References: <20110714095717.35581xj4rdju1pel@webmail.in-berlin.de> <CA%2BtpaK3KXivGBEXxQQPPgUj0Ptt3Gadd%2BK2BT0Xg74RDfb42kA@mail.gmail.com> <20110714115504.20182xr8y5z7o3ug@webmail.in-berlin.de> <CA%2BtpaK3GfLnWDWnS77m_yPoU6AWeFqS8Vusv_g6oPJ=_Voju%2BQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jul 13, 2011 at 10:02 PM, Adam Vande More <amvandemore@gmail.com>wrote: > I suspect this has less to do with actual memory and more to do with some > other buffer-like bottleneck. Does tuning any of the network buffers make > any difference? A couple to try: > > net.inet.ip.intr_queue_maxlen > net.link.ifqmaxlen > kern.ipc.nmbclusters > > If possible, does changing from VM bridged -> NAT or vice-versa result in > any behavior change? > Also check vmstat -z, net.graph.maxdata may be a candidate as well. -- Adam Vande More
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BtpaK18s2wHEM%2BJ-vP9egZPu10wZHFAuxvShhzFWOwVfZ9Miw>