Hi,

I'm using the same nanobsd image on Virtualbox and bhyve (-CURRENT r265101).

The nanobsd image I'm using is configured for serial port as default
console:

[root@nanobsd]~# cat /boot.config
-S38400 -h
[root@nanobsd]~# grep ttyu0 /etc/ttys
ttyu0   "/usr/libexec/getty std.38400"  vt100   on secure

The Virtualbox VM is configured for creating a serial pipe:
VBoxManage modifyvm nanobsd --uart1 0x3F8 4 --uartmode1 server
/tmp/nanobsd.serial
and I connect to this guest using "socat unix-connect:/tmp/nanobsd.serial
stdio,raw,echo=0,icanon=0"
=> And it's works without problem.

The bhyve is configured with a com1 redirecting to a nmdm device: "-l
com1,/dev/nmdm1"
and I connect to this guest using "cu -l /dev/nmdm1B"

=> But this bhyve console didn't works correctly: I can't use tool like
less/more (even ssh-keygen can't ask for a passphrase).
If I run truss with these tools, It seems they hang for opening /dev/tty.

Some differences between virtualbox and bhyve (don't know if it can help):

[root@vbox_guest]~# kenv | grep console
comconsole_pcidev=""
comconsole_port="1016"
comconsole_speed="9600"
console="comconsole"

[root@bhyve_guest]~# kenv | grep console
console="userboot"

Regards,

Olivier
_______________________________________________
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Reply via email to