From owner-freebsd-virtualization@FreeBSD.ORG Tue Jun 2 23:09:55 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 5517D236 for ; Tue, 2 Jun 2015 23:09:55 +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 339D91B28 for ; Tue, 2 Jun 2015 23:09:54 +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 A7ADB98EE for ; Tue, 2 Jun 2015 23:09:53 +0000 (UTC) Message-ID: <556E37BF.8090901@freebsd.org> Date: Tue, 02 Jun 2015 19:09:51 -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> <20150602164949.GZ50817@funkthat.com> <556DF2AB.8070507@FreeBSD.org> <20150602230415.GC50817@funkthat.com> In-Reply-To: <20150602230415.GC50817@funkthat.com> 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 23:09:55 -0000 On 2015-06-02 19:04, John-Mark Gurney wrote: > Andriy Gapon wrote this message on Tue, Jun 02, 2015 at 21:15 +0300: >> On 02/06/2015 19:49, John-Mark Gurney wrote: >>> Andriy Gapon wrote this message on Tue, Jun 02, 2015 at 14:20 +0300: >>>> 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? >>> >>> Hmm... I'm not seeing that here... I just scp a new kernel into the >>> vm, install it, and run shutdown -r now which drops bhyve back to >>> loader, and loads the new kernel... I've been doing this quite >>> successfully over the last few months... >>> >>> I am running a month old HEAD though... >> >> I guess you are running bhyve through the shell script vmrun.sh? >> I am doing everything by hand. > > Correct: > sh /usr/share/examples/bhyve/vmrun.sh -g 6444 -d mach10s.img -t tap0 > > It's nice.. shutdown -r now and shutdown -p now both work exactly as > you'd expect them to... :) > yes, vmrun.sh puts bhyve in a while loop. -- Allan Jude