From owner-freebsd-bugs@freebsd.org Wed Aug 24 23:28:21 2016 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4CE14BC5EA2 for ; Wed, 24 Aug 2016 23:28:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 322A11BDD for ; Wed, 24 Aug 2016 23:28:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u7ONSKCe032600 for ; Wed, 24 Aug 2016 23:28:21 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 168298] VirtualBox using AIO on a zvol crashes Date: Wed, 24 Aug 2016 23:28:20 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 8.3-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rkoberman@gmail.com X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Aug 2016 23:28:21 -0000 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.=