Date: Tue, 07 Mar 2017 14:49:30 +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-cOx1a8jILL@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 martin@sugioarto.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin@sugioarto.com --- Comment #7 from martin@sugioarto.com --- Hi, I would like to confirm that the aio sysctl settings in comment #3 fix cras= hes (causing SIGILL in VBoxSDL) and broken guest filesystems on virtualbox-ose-5.1.14_2 (FreeBSD 11.0). I've tried different guest operating systems and all fail mostly with HDD problems during initial installation. I am using simple VDI files, by the way, not any ZVOL and no compression. My host CPU is a bit slow (AMD Athlon II X3 460), it is only capable to emula= te 32-bit guests. I've used these sysctl settings (probably still overdimensioned): vfs.aio.max_aio_queue=3D8192 vfs.aio.max_aio_queue_per_proc=3D8192 vfs.aio.max_aio_per_proc=3D4096 vfs.aio.max_buf_aio=3D4096 Thank you. --=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-cOx1a8jILL>