From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 12 09:28:38 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 83606F9C for ; Wed, 12 Feb 2014 09:28:38 +0000 (UTC) Received: from mail-lb0-x236.google.com (mail-lb0-x236.google.com [IPv6:2a00:1450:4010:c04::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 067841A88 for ; Wed, 12 Feb 2014 09:28:37 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id w7so6930667lbi.13 for ; Wed, 12 Feb 2014 01:28:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=4adEKyT8ZUKIOSV4fHAmoKFkzJ5j2uayqlqqmCbqE4o=; b=esedG3avLggsBuTPR9h73mBXTLBy17+WiZVZAF+KaugQCZDSelQwOiD8eAmxZGQsgM Bez/WknAB/jDNg8pz+kP5XN+Amb6lVSHpGbM2g63CDvZDsyNK8pidOeCEh8gPLSvjFcG 3pvbF+TeTb9/6IAehrhtJckMfoKDiwA3d/wW9slkOCtVfYPDWMxWVwANT0fXLrfombCE OX5uHr8PY+U7VngSEaDRRaZ90zu+rDyvYiQ536MELyydUL0E8uPCitk5Fin7YdjkFXIR gup4p3q4VpLnMnFm0GrMysSOupOiuyq4EO/8Oo1xmx/DoEEyUUyb3i6nnc3kUFLfOxco +dPA== MIME-Version: 1.0 X-Received: by 10.112.166.68 with SMTP id ze4mr1021210lbb.58.1392197315674; Wed, 12 Feb 2014 01:28:35 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.112.30.211 with HTTP; Wed, 12 Feb 2014 01:28:35 -0800 (PST) In-Reply-To: <21FA50D3-8092-40EA-9B66-9BAC34A4A548@gmail.com> References: <201402111411.33269.jhb@freebsd.org> <21FA50D3-8092-40EA-9B66-9BAC34A4A548@gmail.com> Date: Wed, 12 Feb 2014 01:28:35 -0800 X-Google-Sender-Auth: n93EvnzhY8Wv21Lj6dKRwcojxbQ Message-ID: Subject: Re: Detect of BHyve VM was powered off or rebooted? From: Craig Rodrigues To: "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 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, 12 Feb 2014 09:28:38 -0000 On Tue, Feb 11, 2014 at 3:18 PM, Neel Natu wrote: > > > > > > > > > One question, if "bhyve" exits, do I have to call bhyveload again before > > calling bhyve? > > Yes, that is correct. You will also need to destroy the VM after bhyve > exits. > Why can't bhyve clean up after itself as the bhyve process exits and destroy the VM? It seems pointless to me for the user to have to explictly destroy the VM. Once the bhyve process exits, I doesn't seem that I can use the VM again anyways. To run the VM again, I seem to need to call: -> bhyvectl to destroy the VM -> bhyveload to load -> bhyve to run the VM Aryeh has pointed out to me that it is the responsibility of the user to explictly destroy and tap and bridge devices used by the bhyve process after it exits. Is this right? What if I have a single bridge0 device, and 10 tap devices, one per VM? If one VM exits and needs to be restarted, do I need to tear down all the taps and bridge? -- Craig