Date: Sat, 14 Oct 2017 01:52:06 +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-NSNZnMau8Q@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=3D222916 --- Comment #3 from karihre@gmail.com --- Thank you for the quick reply. Hyperthreading was initially enabled, with t= he guest assigned 4 vCPUs, but disabled as part of the debug process due to re= cent problems with hyper-threading on Intel processors. The memory in the machine was indeed 64GB, and ZFS ARC usage was not being limited like you suggested. I have now set the limit to 20GB and plan to re= boot soon to see if this resolves the issue. I have also (since last boot of the guest) limited the vCPUs to 1 as part of the debug process. The system has = yet to hang, but in general it survived a few days before running into this iss= ue, so the verdict is still in on that mitigation. I will post as soon as I get the next crash, or consider this resolved if everything appears stable for the coming weeks. I'm not sure if you want to mark the bug as closed, or it can remain open until something (or nothing) happens. Thank you, Kari Hreinsson --=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-222916-27103-NSNZnMau8Q>