From owner-freebsd-virtualization@FreeBSD.ORG Fri Nov 7 18:57:24 2014 Return-Path: Delivered-To: virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2EA42FE4 for ; Fri, 7 Nov 2014 18:57:24 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id E6A3DD28 for ; Fri, 7 Nov 2014 18:57:23 +0000 (UTC) Received: from dommail.onthenet.com.au (dommail.OntheNet.com.au [203.13.70.57]) by alto.onthenet.com.au (Postfix) with ESMTP id A2A981279D; Sat, 8 Nov 2014 04:57:21 +1000 (EST) Received: from Peter-Grehans-MacBook-Pro-2.local ([64.245.0.210]) by dommail.onthenet.com.au (MOS 4.4.4-GA) with ESMTP id BZN64352 (AUTH peterg@ptree32.com.au); Sat, 8 Nov 2014 04:57:20 +1000 Message-ID: <545D160E.7060208@freebsd.org> Date: Fri, 07 Nov 2014 10:57:18 -0800 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Marcel Moolenaar Subject: Re: [current] bhyve under VMware borked? References: <3054C397-B9F4-44A7-8D71-FF83CB058671@mac.com> In-Reply-To: <3054C397-B9F4-44A7-8D71-FF83CB058671@mac.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 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: Fri, 07 Nov 2014 18:57:24 -0000 Hi Marcel, What version of VMWare and host are you using ? > Any reason why the fallback was removed? Do we need PAT-related > exit controls to make vmm work? I saw the problem with a beta version of Fusion 5. It went away with the release version, and we made the perhaps wrong assumption that it was no longer an issue. It's easy to put that change back. later, Peter.