From owner-freebsd-virtualization@freebsd.org  Sun May 22 00:30:58 2016
Return-Path: <owner-freebsd-virtualization@freebsd.org>
Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 12007B45BE7
 for <freebsd-virtualization@mailman.ysv.freebsd.org>;
 Sun, 22 May 2016 00:30:58 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 02B2310C3
 for <freebsd-virtualization@FreeBSD.org>; Sun, 22 May 2016 00:30:58 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u4M0UutR079189
 for <freebsd-virtualization@FreeBSD.org>; Sun, 22 May 2016 00:30:57 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-virtualization@FreeBSD.org
Subject: [Bug 209392] Panic on FreeBSD guest on bhyve
Date: Sun, 22 May 2016 00:30:57 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: misc
X-Bugzilla-Version: 10.3-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: grehan@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
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/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-virtualization@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization/>
List-Post: <mailto:freebsd-virtualization@freebsd.org>
List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 22 May 2016 00:30:58 -0000

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.=