From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 12 09:47:13 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 927EAC8F; Wed, 12 Feb 2014 09:47:13 +0000 (UTC) Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5DC931C36; Wed, 12 Feb 2014 09:47:13 +0000 (UTC) Received: by mail-pa0-f53.google.com with SMTP id lj1so8982869pab.12 for ; Wed, 12 Feb 2014 01:47:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=XaZOMBI0LA6heBwXrrGNzv8dXy4zsTCJHkG6OAmSeFc=; b=X/UWs00mnf94rkFwlJz+uBuggdAAUHlobVeXUo4mbEufKLaDqNbeD0pFlxWRfSMqyr fOilhXWiLZX8pIW5WnDnbgIDunULCrLC6Ox8TKywQqO0xfMKpUUNrz4lPS8gX1dMDSFS DjbHloYrKTxaoFKaIGVqnHFc2U2wEOxG7s5e67jsTXf4rvuTty6N/GRzrPnBiA42wsoF QuQfhOdeGVWjKmpaWOp+tJrKJpBkeRrTRvaW7h2hZnnxnfPqGJUYjprCrfAJdNnl7jZ6 rhDJSEMix4CU97HXaYyT6Y0rpIcL6z/a9odU6NUuSlA88gZHnP3Sh8n3Kx+d68N74DGu uYxA== MIME-Version: 1.0 X-Received: by 10.66.141.231 with SMTP id rr7mr37625102pab.41.1392198433053; Wed, 12 Feb 2014 01:47:13 -0800 (PST) Received: by 10.68.155.38 with HTTP; Wed, 12 Feb 2014 01:47:12 -0800 (PST) In-Reply-To: References: <201402111411.33269.jhb@freebsd.org> <21FA50D3-8092-40EA-9B66-9BAC34A4A548@gmail.com> Date: Wed, 12 Feb 2014 04:47:12 -0500 Message-ID: Subject: Re: Detect of BHyve VM was powered off or rebooted? From: Aryeh Friedman To: Craig Rodrigues Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Feb 2014 09:47:13 -0000 On Wed, Feb 12, 2014 at 4:28 AM, Craig Rodrigues wrote: > 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? > Yes you do. It gets really harry when you have multple vm's and taps per instance that need to start and stop at arbitrary times. We are currently disccusing this issue on the petitecloud mailing list it might be off topic here to get into too much detail. -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org