From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 23 17:00:42 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 8CA0EDBA for ; Sun, 23 Feb 2014 17:00:42 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 4C94810EE for ; Sun, 23 Feb 2014 17:00:42 +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 74E2312245; Mon, 24 Feb 2014 03:00:41 +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 BSA64307 (AUTH peterg@ptree32.com.au); Mon, 24 Feb 2014 03:00:40 +1000 Message-ID: <530A2938.40401@freebsd.org> Date: Sun, 23 Feb 2014 09:00:40 -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 FreeBSD 10.0 VM crashed References: <530A09B7.2030505@digiware.nl> In-Reply-To: <530A09B7.2030505@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 17:00:42 -0000 > I've kicked off 3 2G vm's which do a continous > while(1) { make -j 4 buidlworld } How many vCPUs on each VM, and on the host ? Hypervisors in general don't do too well when there is a lot of CPU oversubscription. bhyve may be a bit worse than the crowd with this since we've not had a lot of experience in scheduler tweaking etc to try and mitigate this. Destroying the VM with bhyvectl will reclaim all resources. later, Peter.