From owner-freebsd-virtualization@FreeBSD.ORG Tue Dec 3 00:08:50 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 ESMTPS id 0B34FE92 for ; Tue, 3 Dec 2013 00:08:50 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id C17CB1654 for ; Tue, 3 Dec 2013 00:08:49 +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 5867812407; Tue, 3 Dec 2013 10:08:47 +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 BQM67743 (AUTH peterg@ptree32.com.au); Tue, 3 Dec 2013 10:08:46 +1000 Message-ID: <529D210C.9020801@freebsd.org> Date: Mon, 02 Dec 2013 16:08:44 -0800 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Marc Fournier Subject: Re: Upcoming FreeBSD 10.x + bhyve ... References: <56DEE328-7C96-4AC9-BF87-2C41D4C7949F@hub.org> In-Reply-To: <56DEE328-7C96-4AC9-BF87-2C41D4C7949F@hub.org> Content-Type: text/plain; charset=windows-1252; 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: Tue, 03 Dec 2013 00:08:50 -0000 Hi Marc, > I just read through http://bhyve.org/bhyve-manual.txt, and one thing > that doesn’t seem to be supported (or, I’ve missed it) is HeadLess > support … I get the impression that using this on a remote server > isn’t currently possible, or am I missing something in the docs? It is. The easiest is using the recent change (r258668) which allows bhyveload and bhyve to direct output to a tty instead of just stdio. Use nmdm(4) to create a bidirectional null-modem, point bhyveload/bhyve at one end, and then use any mechanism to attach to the other end (cu, screen, socat etc) at any time. Remote access can be built on top of this if needed. I'm looking to MFC this particular change back to 10.0. later, Peter.