FreeBSD i386 guest doesn't see console...

[John-Mark Gurney]

Peter Grehan wrote this message on Tue, Dec 02, 2014 at 19:27 -0800:
> >This is w/ a resonably recent current i386 kernel (r275062)
> 
>  I verified the r274463 i386 snapshot boots fine. That's not quite as 
> recent, but:
> 
> >...  Any suggestions?
> 
> >uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 on acpi0
> ...
> >uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
> >uart0: console (9600,n,8,1)
> 
>  The "flags 0x10" text isn't being displayed in the i386 dmesg. This is 
> derived from /boot/device.hints i.e.
> 
> ...
> hint.uart.0.flags=0x10
> ...
> 
>  You can see this from bhyveload by issuing a 'show' command to dump 
> all the environment, including what was read in from device.hints by the 
> loader, or "more /boot/device.hints".

So, checking /boot/device.hints shows:
hint.uart.0.at="isa"
hint.uart.0.port="0x3F8"
hint.uart.0.flags="0x10"
hint.uart.0.irq="4"
hint.uart.1.at="isa"
hint.uart.1.port="0x2F8"
hint.uart.1.irq="3"

>  It may be possible that this file isn't being populated in your image, 
> or being read in by bhyveload.

show from loader:
OK show
LINES=24
boot_serial=1
console=userboot
currdev=disk0p3:
interpret=OK
kernelname=/boot/kernel/kernel
loaddev=disk0p3:
prompt=${interpret}
smbios.bios.vendor=BHYVE

Any ideas?

Oh, I did verify that uart0 is functional by logging into the system
and doing: echo foobar > /dev/cuau0

So, it's not like the console is not working, it's clearly a problem w/
the kernel deciding to use it as console..

-- 
  John-Mark Gurney				Voice: +1 415 225 5579

     "All that I will do, has been done, All that I have, has not."