From owner-freebsd-virtualization@FreeBSD.ORG Mon Oct 13 15:32:21 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 011BC517 for ; Mon, 13 Oct 2014 15:32:20 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id B80E12AD for ; Mon, 13 Oct 2014 15:32:20 +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 36CBC127A9 for ; Tue, 14 Oct 2014 01:32:18 +1000 (EST) Received: from Peters-MacBook-Pro.local (c-69-181-164-196.hsd1.ca.comcast.net [69.181.164.196]) by dommail.onthenet.com.au (MOS 4.4.4-GA) with ESMTP id BYZ14984 (AUTH peterg@ptree32.com.au); Tue, 14 Oct 2014 01:32:17 +1000 Message-ID: <543BF07C.6050604@freebsd.org> Date: Mon, 13 Oct 2014 08:32:12 -0700 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: freebsd-virtualization@freebsd.org Subject: Re: no routing from new bhyve install References: <20141012133835.GA39447@potato.growveg.org> In-Reply-To: <20141012133835.GA39447@potato.growveg.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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, 13 Oct 2014 15:32:21 -0000 > I have a machine that runs virtualbox guests currently. I have read elsewhere > that vbox and bhyve don't play well together, but that was a while ago, and > it seemed only on some chipsets. Is this still the case? No, I don't think so :( In theory it might be possible if you could restrict VirtualBox to software virtualization, but I don't know if it's kernel module unconditionally enables VT-x on load and disables on unload which would confuse bhyve a lot. later, Peter.