Date: Sun, 28 Apr 2013 11:42:55 -0600 From: Peter Grehan <grehan@freebsd.org> To: Dan Mack <mack@macktronics.com> Cc: freebsd-virtualization@freebsd.org Subject: Re: bhyve console question Message-ID: <517D5F9F.6030809@freebsd.org> In-Reply-To: <20130428083458.S95875@coco.macktronics.com> References: <20130427154625.X29498@coco.macktronics.com> <517C4F9C.9020200@freebsd.org> <20130428083458.S95875@coco.macktronics.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?517D5F9F.6030809>