From owner-freebsd-virtualization@FreeBSD.ORG Thu Jan 23 08:46:35 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8B8ABC06 for ; Thu, 23 Jan 2014 08:46:35 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 46D10133A for ; Thu, 23 Jan 2014 08:46:35 +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 D1690122C4; Thu, 23 Jan 2014 18:46:32 +1000 (EST) Received: from Peter-Grehans-MacBook-Pro-2.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 BRI33414 (AUTH peterg@ptree32.com.au); Thu, 23 Jan 2014 18:46:29 +1000 Message-ID: <52E0D6E3.3060903@freebsd.org> Date: Thu, 23 Jan 2014 00:46:27 -0800 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Jonas_B=FClow?= Subject: Re: Linux on BHyVe in 10.0-RELEASE References: <52E0C1D4.9000304@freebsd.org> <52E0D1BB.2050807@callfortesting.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-virtualization 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: Thu, 23 Jan 2014 08:46:35 -0000 > So, the conclusion is that it's not possible to run Linux on bhyve > running on 10.0-RELEASE ? Not at all - there have been lots of reports of it working. It is known that there is a problem with using zvols for guest images, though this is related to GEOM and not specific to bhyve. We just need to narrow down what's causing the problem with your setup. later, Peter.