Date: Sun, 22 May 2016 00:30:57 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 209392] Panic on FreeBSD guest on bhyve Message-ID: <bug-209392-27103-WxjFfr49N9@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-209392-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-209392-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=3D209392 Peter Grehan <grehan@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |grehan@FreeBSD.org --- Comment #3 from Peter Grehan <grehan@FreeBSD.org> --- Thanks for the report. The panic was "spin lock held too long" which usually indicates that one of= the vCPUs wasn't able to run for some amount of time. Other than the 'portsnap extract' in the guest, was there much happening on= the host system at the same time ? i.e. lots of other processes running, high memory utilization etc ? (A simple interim workaround is to use a single-vCPU guest). --=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-209392-27103-WxjFfr49N9>