From owner-freebsd-virtualization@FreeBSD.ORG  Wed Feb 12 15:28:23 2014
Return-Path: <owner-freebsd-virtualization@FreeBSD.ORG>
Delivered-To: freebsd-virtualization@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id B0ABC770;
 Wed, 12 Feb 2014 15:28:23 +0000 (UTC)
Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12])
 by mx1.freebsd.org (Postfix) with ESMTP id 6C3701D82;
 Wed, 12 Feb 2014 15:28:23 +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 6F73612183;
 Thu, 13 Feb 2014 01:28:21 +1000 (EST)
Received: from Peters-MacBook-Pro.local (c-69-181-164-196.hsd1.ca.comcast.net
 [69.181.164.196]) by dommail.onthenet.com.au (MOS 4.2.4-GA)
 with ESMTP id BRT85668 (AUTH peterg@ptree32.com.au);
 Thu, 13 Feb 2014 01:28:20 +1000
Message-ID: <52FB930B.1040607@freebsd.org>
Date: Wed, 12 Feb 2014 07:28:11 -0800
From: Peter Grehan <grehan@freebsd.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8;
 rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Craig Rodrigues <rodrigc@FreeBSD.org>
Subject: Re: Detect of BHyve VM was powered off or rebooted?
References: <CAG=rPVcfYQ2nUaZYuc6teL2r+QZzxhuoV052zgf6=Dxh8MeNcA@mail.gmail.com>
 <CAFgRE9Fw308+A14c1ttXj+Yv-CMVRZ-DSE_9DWz46sfpdWg3PQ@mail.gmail.com>
 <201402111411.33269.jhb@freebsd.org>
 <CAG=rPVd15giiO_ugOAt2uBDqzePR3A3iCNpXFcXd2QzS1=oqJQ@mail.gmail.com>
 <21FA50D3-8092-40EA-9B66-9BAC34A4A548@gmail.com>
 <CAG=rPVc4-Ph9+w1U3cGdYbe7WFDZx4sAvNr50ADRe2B7J34Phg@mail.gmail.com>
In-Reply-To: <CAG=rPVc4-Ph9+w1U3cGdYbe7WFDZx4sAvNr50ADRe2B7J34Phg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org>
X-BeenThere: freebsd-virtualization@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization/>
List-Post: <mailto:freebsd-virtualization@freebsd.org>
List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Feb 2014 15:28:23 -0000

Hi Craig,

> It seems pointless to me for the user to have to explictly
> destroy the VM.

  We're working on fixing it. What it gave during the development 
process (and still gives) is the ability to get post-mortem information 
when the bhyve process exits.

> 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

  Yes, that's correct. The future version will be: /usr/sbin/bhyve to 
load/run/reboot the VM in a single process.

> 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?

  Only if you won't be using them anymore.

> 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?

  No - leave them there. Think of the tap interfaces as ports on a 
switch, and the bhyve processes as being plugged/unplugged from the ports.

later,

Peter.