Ahh, cool.   I wasn't paying attention I guess:

 uart2: <16550 or compatible> port 0x3f8-0x3ff irq 4 at device 31.0 on pci0
 uart2: console (9600,n,8,1)

which maps to the bhyve argument given:  '-S 31,uart,stdio'

and subsequently the serial console getty on ttyu2.  Nice.   Thank you,

It would be kind of cool to bind a guest's serial port to a named pipe on the host system (I think virtual box lets you do this too - an option when creating a guest serial port).

This would make it easy to have each bhyve guest with serial console attached to a list of device files upon which we could attach a screen session to later if we wanted to login or look at the console.

For now, I'll just spin up each vm guest within a separate screen window.

Take care,


On Sun, 28 Apr 2013, Peter Grehan wrote:

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



freebsd-virtualization@freebsd.org mailing list
To unsubscribe, send any mail to 

Reply via email to