From owner-freebsd-virtualization@FreeBSD.ORG Mon Dec 15 00:42:30 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 5A6E9FA9 for ; Mon, 15 Dec 2014 00:42:30 +0000 (UTC) Received: from alto.onthenet.com.au (alto2.onthenet.com.au [203.13.68.14]) by mx1.freebsd.org (Postfix) with ESMTP id 1CDBD84D for ; Mon, 15 Dec 2014 00:42:29 +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 80CA5126BF; Mon, 15 Dec 2014 10:42:21 +1000 (EST) Received: from Peters-MacBook-Pro.local (c-67-190-165-43.hsd1.co.comcast.net [67.190.165.43]) by dommail.onthenet.com.au (MOS 4.4.4-GA) with ESMTP id CAL11038 (AUTH peterg@ptree32.com.au); Mon, 15 Dec 2014 10:42:20 +1000 Message-ID: <548E2E66.1040104@freebsd.org> Date: Sun, 14 Dec 2014 17:42:14 -0700 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: Paul Chakravarti Subject: Re: bhyverun - mptable/smbios table requires mapped mem References: <6A5FD6A7-E3B2-4323-A21D-3770E7C3742E@gmail.com> In-Reply-To: <6A5FD6A7-E3B2-4323-A21D-3770E7C3742E@gmail.com> 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: Mon, 15 Dec 2014 00:42:30 -0000 Hi Paul, > # sh /usr/share/examples/bhyve/vmrun.sh -c 1 -m 512K I've not tried to run bhyve with that small an amount of RAM - you may want to bump it up a bit. That may also point to a bug in bhyveload in that it should have failed to load a kernel (that usually requires a few MB minimum). Also, before running again you usually have to reset the state with either another bhyveload or a 'bhyvectl --destroy'. later, Peter.