From owner-freebsd-virtualization@FreeBSD.ORG  Thu Aug 28 01:26:29 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 D76D0867
 for <freebsd-virtualization@FreeBSD.org>; Thu, 28 Aug 2014 01:26:29 +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 BDF5B3490
 for <freebsd-virtualization@FreeBSD.org>; Thu, 28 Aug 2014 01:26:29 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s7S1QTpD033992
 for <freebsd-virtualization@FreeBSD.org>; Thu, 28 Aug 2014 01:26:29 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: Thu, 28 Aug 2014 01:26:29 +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: 
Message-ID: <bug-192470-27103-N57B0b7R5R@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: Thu, 28 Aug 2014 01:26:29 -0000

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

--- Comment #9 from Peter Grehan <grehan@FreeBSD.org> ---
Comment on attachment 146425
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=146425
cpuid difference

Thanks - I think this explains it.

-Vendor ID: "GenuineIntel"; CPUID level 13
+Vendor ID: "GenuineIntel"; CPUID level 2

The AP is coming up with a reduced number of CPU leaves compared to the BSP.
FreeBSD (and bhyve) assumes that this is the same in all CPUs. FreeBSD itself
pulls all information about the system from the BSP's leaf contents, and then
assumes this is the same for all other CPUs.

bhyve's assumption is that it can call do_cpuid() on any CPU and get the
same information to pass to guests on CPUID exits.

A lot of applications also assume this and will look at CPUID values to
determine whether they can use SSE/SSE2/AVX libraries etc.

What system is this ? Are there BIOS options to change max leaf values ? Is
it running nested ?

later,

Peter.

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