From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 23 16:40:32 2014 Return-Path: Delivered-To: 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 79E25B0A for ; Sun, 23 Feb 2014 16:40:32 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 36B481F70 for ; Sun, 23 Feb 2014 16:40:32 +0000 (UTC) Received: from dommail.onthenet.com.au (dommail.OntheNet.com.au [203.13.70.57]) by alto.onthenet.com.au (Postfix) with ESMTPS id 859D812373; Mon, 24 Feb 2014 02:40:30 +1000 (EST) Received: from Peters-MacBook-Pro.local (c-67-161-27-37.hsd1.ca.comcast.net [67.161.27.37]) by dommail.onthenet.com.au (MOS 4.2.4-GA) with ESMTP id BSA63826 (AUTH peterg@ptree32.com.au); Mon, 24 Feb 2014 02:40:29 +1000 Message-ID: <530A2475.6090608@freebsd.org> Date: Sun, 23 Feb 2014 08:40:21 -0800 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Willem Jan Withagen Subject: Re: Bhyve and Ubuntu booting References: <53090599.5000505@digiware.nl> <20AAA4CA-38F9-4D07-BAAA-434F8BC20129@digiware.nl> <530A20BE.4050602@digiware.nl> In-Reply-To: <530A20BE.4050602@digiware.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Feb 2014 16:40:32 -0000 > vm exit rdmsr 0xc0010015, cpu 0 > --- > > And I've seen discussions in other threads about reading/writing cpu > registers where some bits should be 0, but trap when being set.... > (Or something close to this...???) > > So it could again be due to the amdsrc tree differences? It's Linux accessing different MSRs on AMD as opposed to Intel. There is an option to ignore unknown MSRs with bhyve, but that probably shouldn't be used on AMD systems until we've worked out if the MSRs need to be emulated or not. Hopefully that will be in the next updated :) later, Peter.