From owner-freebsd-virtualization@FreeBSD.ORG Tue Jun 2 16:19:01 2015 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 65DCC54D for ; Tue, 2 Jun 2015 16:19:01 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) by mx1.freebsd.org (Postfix) with ESMTP id 43F9116C0 for ; Tue, 2 Jun 2015 16:19:00 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [192.168.1.10] (unknown [192.168.1.10]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id E9D8B95D3 for ; Tue, 2 Jun 2015 16:18:59 +0000 (UTC) Message-ID: <556DD771.9080402@freebsd.org> Date: Tue, 02 Jun 2015 12:18:57 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: freebsd-virtualization@freebsd.org Subject: Re: bhyve: bhyveload, bhyve, bhyvectl --destroy References: <556D9163.1080704@FreeBSD.org> <556DC2FE.1000308@freebsd.org> <556DD6EE.3050104@FreeBSD.org> In-Reply-To: <556DD6EE.3050104@FreeBSD.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 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: Tue, 02 Jun 2015 16:19:01 -0000 On 2015-06-02 12:16, Andriy Gapon wrote: > On 02/06/2015 17:51, Peter Grehan wrote: >> Hi Andriy, >> >>> I am very new to bhyve, so sorry if I am asking something silly or obvious. >>> I am using bhyve to speed up my testing and it seems that each time I need to >>> restart a VM I need to go through the cycle of destroying it with bhyvectl >>> --destroy, then re-loading a kernel with bhyveload and then actually booting the >>> VM with bhyve. It seems that I have to do this even if I don't change th kernel >>> between reboots. My first naive impression was that the point of bhyveload was >>> to load the kernel once. Seems it ain't so? >> >> bhyveload does the job of what BIOS/boot0/1/2/loader would do on real h/w, so >> it has to be executed each time on restart. >> >> One optimization to the cycle you mentioned is that bhyvectl --destroy only has >> to be done when the VM is no longer needed i.e you can loop with bhyveload/bhyve. > > I see now. Thank you very much! > > BTW, and probably you are already aware of this, the documentation could use > some work :-) I noticed at least the following: > - bhyvectl is not documented > - bhyve(8) and bhyveload(8) refer to vmm(4), which does not exist > - bhyveload(8) does not mention that -d can be used multiple times > - bhyve(8) has at least one incorrect reference to bhyveload(*4*) > - bhyve(8) mentions vmnet - does that exist? > > But these are very minor things. bhyve rules :) > vmnet does exist, it is a type of tap, I'll get it hooked up as an alias to the tap man page. -- Allan Jude