From owner-freebsd-virtualization@FreeBSD.ORG  Wed Aug 27 23:50:40 2014
Return-Path: <owner-freebsd-virtualization@FreeBSD.ORG>
Delivered-To: freebsd-virtualization@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 77FC62D5
 for <freebsd-virtualization@FreeBSD.org>; Wed, 27 Aug 2014 23:50:40 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 5EE283C21
 for <freebsd-virtualization@FreeBSD.org>; Wed, 27 Aug 2014 23:50:40 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s7RNoecL049497
 for <freebsd-virtualization@FreeBSD.org>; Wed, 27 Aug 2014 23:50:40 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-virtualization@FreeBSD.org
Subject: [Bug 192470] [bhyve] can't boot FreeBSD in bhyve on CURRENT
Date: Wed, 27 Aug 2014 23:50:40 +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-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: grehan@FreeBSD.org
X-Bugzilla-Status: Needs Triage
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-192470-27103-m00brxc42b@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-192470-27103@https.bugs.freebsd.org/bugzilla/>
References: <bug-192470-27103@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
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.18-1
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Aug 2014 23:50:40 -0000

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

Peter Grehan <grehan@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |grehan@FreeBSD.org

--- Comment #6 from Peter Grehan <grehan@FreeBSD.org> ---
Just to confirm the negative: does pinning to CPUs other than 0 result in the
guest crashing ?

If so, would you be able to install the cpuid port (pkg install cpuid) and run
it on all cpus

cpuset -l <cpu> cpuid

.. and see if there are any differences in what is reported between CPUs, other
than obvious ones such as APIC ID.

later,

Peter.

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