Date: Fri, 28 Dec 2018 13:09:58 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 231117] I/O lockups inside bhyve vms Message-ID: <bug-231117-27103-ZljnOtCfsI@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-231117-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-231117-27103@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=3D231117 --- Comment #17 from Kristian K. Christensen <kkc@duckpond.dk> --- So, after some extensive testing over the holidays: FreeBSD 11.1 with as low as 100mb ARC max, doesn't excert this behavior. FreeBSD 11.2 and 12.0 with 1024 ARC max and lower, excerts this behavior. FreeBSD 11.2 and 12.0 with over 4GB ARC max does not hang. (I need to see h= ow low I can make it go, but so far I've been unable to cause 4GB ARC max to h= ang) It may seem odd to want to limit ARC, but we have experienced high ARC usage and applications (bhyve VMs and MySQL daemons notably) being killed due to = OOM, if we don't enforce ARC limits. This causes a lot of nightly on-call activi= ty and data loss, which is not really something we care for. Furthermore, this= is on VMs that use a zvol as primary storage, on a host that has a fairly high= ARC limit, so ideally the host handles most of the ARC. --=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-231117-27103-ZljnOtCfsI>