From owner-freebsd-virtualization@freebsd.org  Mon Apr  4 22:53:27 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 7E527B03791
 for <freebsd-virtualization@mailman.ysv.freebsd.org>;
 Mon,  4 Apr 2016 22:53:27 +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 6EA3113AC
 for <freebsd-virtualization@FreeBSD.org>; Mon,  4 Apr 2016 22:53:27 +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 u34MrRZO051030
 for <freebsd-virtualization@FreeBSD.org>; Mon, 4 Apr 2016 22:53:27 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-virtualization@FreeBSD.org
Subject: [Bug 203820] kernel panic when trying to unload vmm(4) and
 VirtualBox VMs are running
Date: Mon, 04 Apr 2016 22:53:27 +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: 10.2-RELEASE
X-Bugzilla-Keywords: crash
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: jhb@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-203820-27103-vtAI7aHtnR@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-203820-27103@https.bugs.freebsd.org/bugzilla/>
References: <bug-203820-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.21
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, 04 Apr 2016 22:53:27 -0000

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

--- Comment #11 from John Baldwin <jhb@FreeBSD.org> ---
(In reply to nospam from comment #9)
Do you mean kldloading virtual box in an instance of FreeBSD running in a b=
hyve
VM?  I think that will just not work as bhyve doesn't let the guest see any=
 of
the VT-x capabilities of the CPU since it doesn't support nested VT-x.  The
reverse might work if VirtualBox supports nested VT-x (I haven't tried).

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