From owner-freebsd-virtualization@freebsd.org  Fri Jul 28 05:35:46 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 B3530DBE61A
 for <freebsd-virtualization@mailman.ysv.freebsd.org>;
 Fri, 28 Jul 2017 05:35:46 +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 9C6AD7483A
 for <freebsd-virtualization@FreeBSD.org>; Fri, 28 Jul 2017 05:35:46 +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 v6S5Zkt6008939
 for <freebsd-virtualization@FreeBSD.org>; Fri, 28 Jul 2017 05:35:46 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-virtualization@FreeBSD.org
Subject: [Bug 215972] Bhyve crash more then 1 cpu AMD
Date: Fri, 28 Jul 2017 05:35:46 +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.0-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
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: 
Message-ID: <bug-215972-27103-aELeYOGj3H@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-215972-27103@https.bugs.freebsd.org/bugzilla/>
References: <bug-215972-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: Fri, 28 Jul 2017 05:35:46 -0000

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

--- Comment #21 from Peter Grehan <grehan@FreeBSD.org> ---
(In reply to dgilbert from comment #20)

Sorry, didn't know that was you.

There are 2 other things to try here:

- when the guest is hung, on the host issue

  bhyvectl --get-rip --cpu=3D0 --vm=3D<your vm name>
  bhyvectl --get-rip --cpu=3D1 --vm=3D<your vm name>
  bhyvectl --get-rip --cpu=3D2 --vm=3D<your vm name>
  bhyvectl --get-rip --cpu=3D3 --vm=3D<your vm name>

 You can look at what the resulting RIP values correspond to by restarting =
the
guest, and within the guest,

   kgdb /boot/kernel/kernel
   x/i <rip value>

- Run the same test with a 12-current guest. With luck, it will panic and d=
rop
into ddb. If it hangs but doesn't panic, for the guest to drop into ddb from
the host by issuing

  bhyvectl --inject-nmi --vm=3D<your vm name>

 From within ddb you can issue a backtrace.

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