Date: Wed, 24 Aug 2016 23:28:20 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 168298] VirtualBox using AIO on a zvol crashes Message-ID: <bug-168298-8-2Lyvfkz0Jj@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-168298-8@https.bugs.freebsd.org/bugzilla/> References: <bug-168298-8@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=3D168298 --- Comment #6 from rkoberman@gmail.com --- The adjustments in comment 3 seem to work, although vfs.aio.aiod_timeout do= es not exist in 11.0 and vfs.aio.max_aio_procs defaults to 4, so is a noop. Some of the others seem a bit extreme and I suspect tuning them back would = be reasonable. The queue depths are being set to the maximum possible. I suspe= ct 4096 and 1024 would be adequate. Not really sure why the reduction of maximum AIO processes to 4, but does n= ot seem unreasonable. Likewise the 10x increase in idle time for AIO processes. The final two, max_aio_per_proc and max_buf_aio also look a bit extreme. Bu= mped from 32 and 16 to 8K is probably overkill. I'll play around with them and s= ee what I find. Finally, these may require tuning for the number of VMs. In any case, I can now run my VM without the disk lock-ups. --=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-168298-8-2Lyvfkz0Jj>