From owner-freebsd-virtualization@FreeBSD.ORG Sun Apr 28 17:43:15 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1EA1FDB8 for ; Sun, 28 Apr 2013 17:43:15 +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 CF7CB1EF3 for ; Sun, 28 Apr 2013 17:43:14 +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 A303411DC7; Mon, 29 Apr 2013 03:43:12 +1000 (EST) Received: from Peter-Grehans-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 BLS67556 (AUTH peterg@ptree32.com.au); Mon, 29 Apr 2013 03:43:09 +1000 Message-ID: <517D5F9F.6030809@freebsd.org> Date: Sun, 28 Apr 2013 11:42:55 -0600 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.28) Gecko/20120306 Thunderbird/3.1.20 MIME-Version: 1.0 To: Dan Mack Subject: Re: bhyve console question References: <20130427154625.X29498@coco.macktronics.com> <517C4F9C.9020200@freebsd.org> <20130428083458.S95875@coco.macktronics.com> In-Reply-To: <20130428083458.S95875@coco.macktronics.com> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Junkmail-Info: RCVD_IN_PBL,RCVD_IN_SORBS_DUL,RDNS_DYNAMIC,SPF_SOFTFAIL X-Junkmail-Status: score=29/51, host=dommail.onthenet.com.au 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: Sun, 28 Apr 2013 17:43:15 -0000 HI Dan, > Yes, the current bhyve-manual has that as a step in the configuration > (http://bhyve.org/bhyve-manual.txt) which I guess is the culprit. I > guess I just didn't expect that side effect but admit to not spending > much time thinking about it first :-) I think it was done that way since /dev/console will always work, whereas the tty line to use changed at one point when we cut over from the ISA uart device to the PCI uart device resulting in a different tty device being used. However, it looks like we may switch back to using a PCI-ISA bridge device and that will change things again :( For now, you can edit the stock /etc/ttys as follows: -ttyu2 "/usr/libexec/getty std.9600" dialup off secure +ttyu2 "/usr/libexec/getty std.9600" vt100 on secure later, Peter.