From owner-freebsd-virtualization@FreeBSD.ORG Mon Feb 10 00:03:42 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 E5BB4AD1; Mon, 10 Feb 2014 00:03:42 +0000 (UTC) Received: from mail-qa0-x22a.google.com (mail-qa0-x22a.google.com [IPv6:2607:f8b0:400d:c00::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7CBF31602; Mon, 10 Feb 2014 00:03:42 +0000 (UTC) Received: by mail-qa0-f42.google.com with SMTP id k4so8636192qaq.15 for ; Sun, 09 Feb 2014 16:03:41 -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=zNhlXhLdz98Ljbw5Juny0AUjlKdR6nqBbGOXAi6VYbc=; b=T2kwib9IaQl2sNjRRAs+1icxKDF1RWk1xQUDnDTOT7Wjns/16klcNyrIPowiqn7QQ8 yFRjUpWXwhdclsRwVuz+nR9r8a524lgvOQzw9Gr1FOB8KTGF0jipuRgF+Bx7E8v3ecXI 87eW7XXh/lSB14WK94MvNUO1jKg/qx63vZGtqW8hcXN6+fFVlb9aMHC8GYmdIbw3azp4 AzXMd9ROOVLKYrx7gMe+5aG/4cMYY2HoUe0nWvNQ7zzlGHxtPsza2pOZK9xmAYhjJsLv 8m5OM+lm/9H0WtN7BQe8KKS0HBc02nwjuMksvsdQyQcDi3AocLgNA7WrMwq2fVmIj9bS jugw== MIME-Version: 1.0 X-Received: by 10.224.132.65 with SMTP id a1mr43406124qat.69.1391990621437; Sun, 09 Feb 2014 16:03:41 -0800 (PST) Received: by 10.140.87.71 with HTTP; Sun, 9 Feb 2014 16:03:41 -0800 (PST) In-Reply-To: References: Date: Sun, 9 Feb 2014 16:03:41 -0800 Message-ID: Subject: Re: Detect of BHyve VM was powered off or rebooted? From: Neel Natu To: Craig Rodrigues Content-Type: text/plain; charset=ISO-8859-1 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: Mon, 10 Feb 2014 00:03:43 -0000 Hi Craig, On Sun, Feb 9, 2014 at 1: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)? The exit code of the bhyve process will be 0 if it exited because the guest rebooted and will be non-zero if the guest did an acpi poweroff. You can use that to distinguish between cases (2) and (3). Having said that there are error conditions for which bhyve exits with a non-zero exit code. So, we'll need to explicitly define an exit code to distinguish between an acpi poweroff and these error conditions. best Neel > > Thanks for any advice. > > -- > Craig > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebsd.org"