From owner-freebsd-virtualization@FreeBSD.ORG Sun Nov 23 03:27:57 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4FD06D91 for ; Sun, 23 Nov 2014 03:27:57 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 11C3ABB4 for ; Sun, 23 Nov 2014 03:27:56 +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 DDD2C123FE; Sun, 23 Nov 2014 13:27:54 +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.4.4-GA) with ESMTP id BZX17342 (AUTH peterg@ptree32.com.au); Sun, 23 Nov 2014 13:27:53 +1000 Message-ID: <54715438.3090905@freebsd.org> Date: Sat, 22 Nov 2014 19:27:52 -0800 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Shawn Webb Subject: Re: bhyve cannot allocate memory References: <20141122215245.d9380cc4e43cb5e60d479009@gmail.com> <20141122220202.09523b0ae828993174af05d8@gmail.com> <5471513C.6040400@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-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: Sun, 23 Nov 2014 03:27:57 -0000 Hi Shawn, > It's hardenedBSD. I'll try a stock build tomorrow. The only change we > have that could affect bhyve is the removal of map_at_zero. This may be the issue. bhyve creates a kernel-use-only vmspace that represents guest memory (starting at 0), and is used to allow the VM system to manage the EPT paging structures (full details in the AsiaBSDcon paper at http://people.freebsd.org/~neel/bhyve/bhyve_nested_paging.pdf). Is there a way to bypass the map-at-zero check for this usage in HardenedBSD ? later, Peter.