From owner-freebsd-virtualization@FreeBSD.ORG Tue Jul 2 23:04:02 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id CD521B10 for ; Tue, 2 Jul 2013 23:04:02 +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 922EB1B08 for ; Tue, 2 Jul 2013 23:04:02 +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 3CBF01254E; Wed, 3 Jul 2013 09:04:00 +1000 (EST) Received: from Peter-Grehans-MacBook-Pro.local ([64.245.0.210]) by dommail.onthenet.com.au (MOS 4.2.4-GA) with ESMTP id BNC00120 (AUTH peterg@ptree32.com.au); Wed, 3 Jul 2013 09:03:59 +1000 Message-ID: <51D35C5D.90703@freebsd.org> Date: Tue, 02 Jul 2013 16:03:57 -0700 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Aryeh Friedman Subject: Re: bhyve bug report and a question References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-virtualization@freebsd.org 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, 02 Jul 2013 23:04:02 -0000 Hi Aryeh, > bhyve does not send a shutdown signal to guest OS's and wait from them > to halt.... This requires a couple of things - an ACPI event channel in bhyve to inform the guest of events, and a way to signal bhyve to raise these events e.g. a simulated power-button press. On the TODO list. > this is despite having -H on the command line Ah, so that's different: the -H option signals the VT-x hardware that it should exit when the guest issues a HALT instruction. This is then used by bhyve as an indication that the guest vCPU is in an idle state and can be put to sleep until an async event arrives. later, Peter.