Date: Sun, 28 Aug 2016 19:46:56 +0000 From: bugzilla-noreply@freebsd.org To: vbox@FreeBSD.org Subject: [Bug 212128] emulators/virtualbox-ose: Default AIO settings break VirtualBox Message-ID: <bug-212128-26505-mrOAthggQp@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-212128-26505@https.bugs.freebsd.org/bugzilla/> References: <bug-212128-26505@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212128 --- Comment #2 from rkoberman@gmail.com --- The use of large amounts of KVM by these AIO parameters is a concern tome a= nd I have been testing with more moderate values to see if these make VBox stabl= e. I have now reduced the two biggest changes to: vfs.aio.max_aio_queue=3D8192 vfs.aio.max_aio_queue_per_proc=3D1024 So far, after two days of use, my guest system has remained stable. I should also note that the maximum number of AIO processes is reduced from= 32 to 8 which will tend to limit the KVM consumed substantially. I will also be looking at the 10x increase in process lifetime. It is conceivable that thi= s is either critical to working around the problem or is unneeded. Those more familiar with the inner workings of the AIO daemons might have a better idea than I do. I will continue to adjust parameters, but must do that slowly as it can take some time before the problem pops up depending on disk load (whether from V= Box or other activity). I am testing on a older (5 yrs) laptop with an 2.5 GHz Sandy Bridge i5 CPU and standard HGST disk 1TB disk, so disk I/O will not be impressive. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-212128-26505-mrOAthggQp>