From owner-freebsd-virtualization@freebsd.org  Mon Nov  6 21:59:15 2017
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 D5134E681EB
 for <freebsd-virtualization@mailman.ysv.freebsd.org>;
 Mon,  6 Nov 2017 21:59:15 +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 B88A431F6
 for <freebsd-virtualization@FreeBSD.org>; Mon,  6 Nov 2017 21:59:15 +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 vA6LxFYd002663
 for <freebsd-virtualization@FreeBSD.org>; Mon, 6 Nov 2017 21:59:15 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
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!"
Date: Mon, 06 Nov 2017 21:59:15 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.1-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: karihre@gmail.com
X-Bugzilla-Status: Closed
X-Bugzilla-Resolution: Not A Bug
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-222916-27103-sKVpc24nj3@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/>
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.23
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: Mon, 06 Nov 2017 21:59:15 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222916

karihre@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|New                         |Closed
         Resolution|---                         |Not A Bug

--- Comment #7 from karihre@gmail.com ---
So the vm has now been running for more than 3 weeks without problems, with=
 4
vcpus and 32 GB of memory. I think it is safe to say this was not a bug, bu=
t in
fact a memory oversubscription. Thank you for your quick comments/advise!

Hopefully this (non-)bug report will shed a light on similar problems for
others. Marking this as closed/not-a-bug, feel free to change the status to
something else as appropriate.

--=20
You are receiving this mail because:
You are the assignee for the bug.=