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 :-)
Dan
On Sat, 27 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
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
Hi Dan,
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'
Yes - the '-S' parameter instructs the PCI device to use a
compatibility address so the console code can still access
