From owner-freebsd-virtualization@FreeBSD.ORG Sat Dec 21 22:56:40 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 72FDB20B for ; Sat, 21 Dec 2013 22:56:40 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 330681898 for ; Sat, 21 Dec 2013 22:56:40 +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 D40701214B; Sun, 22 Dec 2013 08:56:13 +1000 (EST) Received: from Peters-MacBook-Pro.local (c-71-196-188-222.hsd1.co.comcast.net [71.196.188.222]) by dommail.onthenet.com.au (MOS 4.2.4-GA) with ESMTP id BQV81603 (AUTH peterg@ptree32.com.au); Sun, 22 Dec 2013 08:56:12 +1000 Message-ID: <52B61C94.4000006@freebsd.org> Date: Sat, 21 Dec 2013 14:56:20 -0800 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: =?UTF-8?B?TWljaGHFgiBEdWJpZWw=?= Subject: Re: Means to control a bhyve VM instance References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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: Sat, 21 Dec 2013 22:56:40 -0000 Hi MichaƂ, > May I ask you about the means to control a VM instance. I mean by that > something providing similar features as QEMU's monitor interface along > with QEMU > Machine Protocol (QMP) do. Has it already been decided/designed how bhyve > is going to handle features like a soft start/stop of a VM instance, > hot-plugging of additional blk/net devices, etc? Decided, no, though the broad direction we're moving in is for bhyve to be a single process (reboots in-process, no external loader), and control from bhyvectl via some form of RPC. later, Peter.