Date: Sat, 14 Oct 2017 02:21:20 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 222916] [bhyve] Debian guest kernel panics with message "CPU#0 stuck for Xs!" Message-ID: <bug-222916-27103-zzfp3y3KLR@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-222916-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-222916-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=222916 --- Comment #4 from Peter Grehan <grehan@FreeBSD.org> --- Single vCPU guests perform very well in oversubscribed environments since there are no lock-spins against other possibly de-scheduled vCPUs. However, you still may hit the ZFS memory competition issue. Note that you can set the ARC-max on the fly in 11.1 and avoid the reboot, using the vfs.zfs.arc_max sysctl var. ZFS should slowly drop down to this value if it is above it. >not sure if you want to mark the bug as closed Fine to keep this open until the issue is resolved. -- 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-222916-27103-zzfp3y3KLR>