Date: Thu, 18 Jan 2018 02:25:27 +0000 From: bugzilla-noreply@freebsd.org To: vbox@FreeBSD.org Subject: [Bug 221294] emulators/virtualbox-ose 5.1.26 r117224 Win7 VM Creation Fails Message-ID: <bug-221294-26505-f0OUmG7eIR@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-221294-26505@https.bugs.freebsd.org/bugzilla/> References: <bug-221294-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=3D221294 --- Comment #3 from papowell@astart.com --- After reporting this problem, I got several suggestions. Here is the one = that appeared to reduce the problem. The following was added to /etc/sysctl.con= f: # https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212128 # # On FreeBSD-11 and on older versions using AIO VirtualBox can lose # disk access when the disk is heavily loaded. # # The symptoms are either the guest locking up with the guest's system # "disk" showing continuous access while the host system shows no # disk activity or by a crash on the guest. # # This can be fixed by adjusting the AIO sysctls to allow added # capacity before disk requests are lost. # # While I have no fix and this issue has existed for a long time, I # suggest that pkg-message have an added warning Here is a first-cut # that could use some word-smithing: #=20 # If AIO is enabled (always in FreeBSD-11.0 and newer), guests may # lose disk access. This can be mitigated by adjusting AIO sysctls # as follows: # # Current 11.0 Settings: # vfs.aio.max_buf_aio: 16 # vfs.aio.max_aio_queue_per_proc: 256 # vfs.aio.max_aio_per_proc: 32 # vfs.aio.aiod_lifetime: 30000 # vfs.aio.num_buf_aio: 0 # vfs.aio.num_queue_count: 0 # vfs.aio.max_aio_queue: 1024 # vfs.aio.target_aio_procs: 4 # vfs.aio.num_aio_procs: 0 # vfs.aio.max_aio_procs: 32 # vfs.aio.unsafe_warningcnt: 1 # vfs.aio.enable_unsafe: 0 # Set: # default # vfs.aio.aiod_lifetime=3D30000 # (30000) # vfs.aio.max_aio_procs=3D4 # (32) # vfs.aio.max_aio_queue=3D65536 # (1024) # vfs.aio.max_aio_queue_per_proc=3D65536 # (256) # vfs.aio.max_aio_per_proc=3D8192 # (32) # vfs.aio.max_buf_aio=3D8192 # (16) # # Alternative: # # From my sysctl.conf Default # vfs.aio.aiod_lifetime=3D30000 # (30000) # vfs.aio.max_aio_procs=3D4 # (32) # vfs.aio.max_aio_queue=3D8192 # (1024) # vfs.aio.max_aio_queue_per_proc=3D1024 # (256) # vfs.aio.max_aio_per_proc=3D128 # (32) # vfs.aio.max_buf_aio=3D64 # (16) # vfs.aio.aiod_lifetime=3D30000 vfs.aio.max_aio_procs=3D4 vfs.aio.max_aio_queue=3D8192 vfs.aio.max_aio_queue_per_proc=3D1024 vfs.aio.max_aio_per_proc=3D128 vfs.aio.max_buf_aio=3D64 --=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-221294-26505-f0OUmG7eIR>