From owner-freebsd-virtualization@FreeBSD.ORG Wed Apr 2 18:33:41 2014 Return-Path: Delivered-To: freebsd-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 B8D3AB2C for ; Wed, 2 Apr 2014 18:33:41 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 7B73D909 for ; Wed, 2 Apr 2014 18:33:41 +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 3925B1244E; Thu, 3 Apr 2014 04:33:34 +1000 (EST) Received: from Peter-Grehans-MacBook-Pro-2.local ([64.245.0.210]) by dommail.onthenet.com.au (MOS 4.2.4-GA) with ESMTP id BTB71905 (AUTH peterg@ptree32.com.au); Thu, 3 Apr 2014 04:33:33 +1000 Message-ID: <533C57FB.3000308@freebsd.org> Date: Wed, 02 Apr 2014 11:33:31 -0700 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: John , freebsd-virtualization@freebsd.org Subject: Re: virtualbox and bhyve questions References: <20140402155106.GA64789@potato.growveg.org> In-Reply-To: <20140402155106.GA64789@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.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: Wed, 02 Apr 2014 18:33:41 -0000 Hi John, > 1. I've read that virtualbox and bhyve cannot run at the same time. Is > this still the case? (because I've managed to start a bhyve instance > with virtualbox still running - is this a fluke?) If you use VirtualBox with VT-x disabled, i.e. binary translation mode, it will work. Otherwise, all bets are off. There is no way to share VT-x resources (vCPU TLB tags, CPU VMCS state etc) so eventually the hypervisors will collide. > 2. Can I take a system made in virtualbox and boot with it using bhyve? > The system 'hard drives' are all VDI (the default in virtualbox) You would have to convert the VDI file to a flat file with a tool like qemu-img. Depending on the o/s, the disk and network adapter type may have to be the same in vbox and bhyve or init scripts may not be able to locate interface/disk names. Also, the vbox guest should be configured with a serial console. > 3. if I can't boot it without conversion to something else, how do I go > about it? > > 4. what's the maximum number of cpu and the maximum ram and HD space > that I can give to a bhyve VM? bhyve's vCPU limit is 16. There are no limits on HD space. > 5. if I make a VM and put opensuse (latest) on it, is it preferable to > have the HD as raw or as ext-3 (or whatever the default for opensuse > is)? If the latter, is there a penalty in terms of performance or > security? The host runs zfs. Do you mean, the virtual disk type for the guest, something like vmdk/vdi/vhd/raw ? later, Peter.