From owner-freebsd-virtualization@FreeBSD.ORG Tue Jun 2 14:59:23 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 35DB6345 for ; Tue, 2 Jun 2015 14:59:23 +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 128371D29 for ; Tue, 2 Jun 2015 14:59:22 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [192.168.1.2] (unknown [192.168.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id EAD479500 for ; Tue, 2 Jun 2015 14:59:21 +0000 (UTC) Message-ID: <556DC4D1.7070205@freebsd.org> Date: Tue, 02 Jun 2015 10:59:29 -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> In-Reply-To: <556D9163.1080704@FreeBSD.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="RF8P9t3xU2KVagw2sj5at2JSMh2WMuVlX" 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 14:59:23 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --RF8P9t3xU2KVagw2sj5at2JSMh2WMuVlX Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2015-06-02 07:20, Andriy Gapon wrote: >=20 > I am very new to bhyve, so sorry if I am asking something silly or obvi= ous. > I am using bhyve to speed up my testing and it seems that each time I n= eed to > restart a VM I need to go through the cycle of destroying it with bhyve= ctl > --destroy, then re-loading a kernel with bhyveload and then actually bo= oting 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 bhyve= load was > to load the kernel once. Seems it ain't so? >=20 Are you running -CURRENT, 10-STABLE, or 10.1? I think there was talk recently of removing the requirement to destroy the VM before running bhyveload again. --=20 Allan Jude --RF8P9t3xU2KVagw2sj5at2JSMh2WMuVlX Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJVbcTVAAoJEJrBFpNRJZKfPl4P/RHy41iajqAQcB5sxuIUh+zE laP4G5zaKFYjj/YzsWPM6bU1K2h7oT3teOUJaxs7mR8NB5Z5I9V0EjXMeGRVJVKw yr0fO/oKTar9vDMoIgVHsAsp3pJ2UQST77wPzYo/7amVOyV+4eWrqAkiAksXjTUQ MU08cwl4AwJq/owneONu7eboy7sr3NHc686TlW0NLXkXsUXvnneD9DQwy2WgJh2i +PyTlklkG378/2DrKQlyXHMyc7SIovlmHmi9WpNADfi5OpHJQnfY6R2+p5ArnSEt jSjTM7DMu+l2Eqp4eObThtTYw6rAgYjqhMrFpOrhOgCiu1I7KYHGTjQ98P5JLeqQ qmkE1ELmRqkP4/3Qd+TTsT04Uvxg1llct0gTTrzYa7Y58e3VCeQbX3aWxQZb9Hay TSWtdqTlKPY0GHK7a1P8dG80ogRU4BcCgbtyIB/g67P/Bfb0EGv799NU21IiWTUC UY63HSheQnU2mWP8tQKmB1xsJKday39IQWaW4T+PJCHKsj2kKIJjVKpSsOYrnSsV NGMhFkeD21zwLuKqa8Pk1hZohelyVAodpxxJBA+xMesBpJPufbQVCITGoR34dG+U gGayPAhMuJIO9wvdHDiit8IvI/uxheCdbSPhPEn87rCFddmSowc6m8zvFafQaWIM +caDhBZhKi/uRvbzicKm =U0V5 -----END PGP SIGNATURE----- --RF8P9t3xU2KVagw2sj5at2JSMh2WMuVlX--