From owner-freebsd-virtualization@FreeBSD.ORG Tue Oct 29 22:31:01 2013 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 ESMTP id 23F2DF65 for ; Tue, 29 Oct 2013 22:31:01 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id D75B32D54 for ; Tue, 29 Oct 2013 22:31:00 +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 50F12123FC; Wed, 30 Oct 2013 08:30:59 +1000 (EST) Received: from Peter-Grehans-MacBook-Pro-2.local ([64.245.0.210]) by dommail.onthenet.com.au (MOS 4.2.4-GA) with ESMTP id BPM37365 (AUTH peterg@ptree32.com.au); Wed, 30 Oct 2013 08:30:58 +1000 Message-ID: <5270371F.1050502@freebsd.org> Date: Tue, 29 Oct 2013 15:30:55 -0700 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: Aryeh Friedman , "freebsd-virtualization@freebsd.org" Subject: Re: Fwd: Bhyve: acpi0: AcpiEnterSleepStatePrep failed - AE_NOT_FOUND References: <526F066C.2020001@freebsd.org> <52703376.6010608@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 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: Tue, 29 Oct 2013 22:31:01 -0000 >> Not sure what you're looking for here: something inside the guest that is >> told when the host is shutting down or suspending ? > > > More like the ability of the host to tell the guest to reboot Ah, yes: this has been requested by others. It would be done by implementing the ACPI event channel, and then allowing something like bhyvectl to send sleep/power-off events to bhyve which would then inject it into the guest via the event channel. later, Peter.