From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 9 21:32: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 065471F0; Sun, 9 Feb 2014 21:32:38 +0000 (UTC) Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CA1EE196D; Sun, 9 Feb 2014 21:32:37 +0000 (UTC) Received: by mail-pa0-f41.google.com with SMTP id fa1so5346013pad.14 for ; Sun, 09 Feb 2014 13:32:37 -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=r6T/c6x5CnvM7EGmnoh73ZPUArjmLRDDyYGEw2X6Z2o=; b=kdsgHlNSjOKmOu/+0InRxqmrqZfA3FAtGfP4vOZn7UyB5J4aHqxNJxpZukjYUAr7oH 6XPM65NnlxiYLG3kDXlHDEyiu+ot3L2myg4VmdYca/TRQp5Kuua4l7CuTKjySOkXxj6l U4zyOEoryWRYQO++CnJnBaf2ew+v5IIPfL9QyJOJM6L+JqT1a8c7lyK8Lqo8lZRsfT6m +gzxM9WtNE/exqpJuC/GoWPn17K+DukUVAReME6MFrrjDu6KCF3tzHRN5eEp3V1FVCvj sST1UT8L2V1Hu1hENe5BCRNlEGoK1xnclh8Rk6bDZ5WI3LFsx6cX0Oh8qWvNhZ+37vyh pU9w== MIME-Version: 1.0 X-Received: by 10.66.121.234 with SMTP id ln10mr21631634pab.20.1391981557393; Sun, 09 Feb 2014 13:32:37 -0800 (PST) Received: by 10.68.155.38 with HTTP; Sun, 9 Feb 2014 13:32:37 -0800 (PST) In-Reply-To: References: Date: Sun, 9 Feb 2014 16:32:37 -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: Sun, 09 Feb 2014 21:32:38 -0000 On Sun, Feb 9, 2014 at 4:11 PM, Craig Rodrigues wrote: > Hi, > > I posted some rc.d scripts that I am using to boot a BHyve VM > and send the output to a serial console using the /dev/nmdm > driver: > > > http://lists.freebsd.org/pipermail/freebsd-virtualization/2014-January/002040.html > > It works quite well. There is some things I would like to improve, > and would like some advice on the best way to do it. > > (1) If the VM was destroyed with bhyvectl --destroy --vm ${VM_NAME}, > then I do not want to automatically restart the VM in the script. > User should manually: service bhyvevm start > > (2) If the VM was powered down, via shutdown -p, or halt -p, > then in my script I do not want to restart the VM in the script. > User should manually: service bhyvevm start > > (3) If the VM was rebooted via "reboot" or "shutdown -r", > then I *do* want the script to restart the VM. > > I think if I change my start_vm.sh script to do something like: > > > > ( > while [ -e /dev/vmm/${VM} ]; do > /usr/sbin/bhyve -c 16 -m 8G -A -H -P -g 0 -s 0:0,hostbridge -s 1:0,lpc > -s 2:0,virtio-net,${TAP} -s 3:0,virtio-blk,${IMG} -l com1,${CONS_A} ${VM}" > done > > ) & > > > then this might cover cases (1) and (3), but what will cover > case (2)? > > Thanks for any advice. > The options you gave (which are really the only ones available) do not distinguish between the reason for the termination of the instance of bhyve pointing to /dev/vmm/XXX (it just does a normal termination). In my playing with this for almost a month the only solution seems to be put a trigger on instance shutdown via whatever method to leave a "cookie" file behind on the host (note I have not nor plan to do this in any of my own work). An other question is it wise to auto-reboot regardless of reason of the hypervisor termination? -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org