I am running RL-8.8 as a bhyve guest on top of FreeBSD-13.1. I am having a problem connecting to the serial console of the guest from the host using cu via the vm console command. I obtain a connection with echoback but I do not get a shell, or at least I cannot get a prompt from one. Access to the serial console via cu has worked in the recent past on this particular guest.
The kernelopts on this guest was altered to include: console=tty0 console=ttyS0,115200. In the past I have successfully connected to ttyS0 from the host system. I can log into the guest using ssh. On the guest system I see many of these error messages continuously being written to /var/log/messages:
Jun 27 11:54:08 vhp3k101 systemd[1]: serial-getty@ttyS0.service: Service RestartSec=100ms expired, scheduling restart.
Jun 27 11:54:08 vhp3k101 systemd[1]: serial-getty@ttyS0.service: Scheduled restart job, restart counter is at 56.
Jun 27 11:54:08 vhp3k101 systemd[1]: Stopped Serial Getty on ttyS0.
Jun 27 11:54:08 vhp3k101 systemd[1]: Started Serial Getty on ttyS0.
Jun 27 11:54:18 vhp3k101 systemd[1]: serial-getty@ttyS0.service: Succeeded.
Jun 27 11:54:19 vhp3k101 systemd[1]: serial-getty@ttyS0.service: Service RestartSec=100ms expired, scheduling restart.
Jun 27 11:54:19 vhp3k101 systemd[1]: serial-getty@ttyS0.service: Scheduled restart job, restart counter is at 57.
Jun 27 11:54:19 vhp3k101 systemd[1]: Stopped Serial Getty on ttyS0.
Jun 27 11:54:19 vhp3k101 systemd[1]: Started Serial Getty on ttyS0.
I cannot help but think that the error messages and the inability to get a shell via cu are somehow related. Does anyone have any idea as to what may have happened and how this might be fixed?
I noted that /dev/ttyS0 looks like this:
ll /dev/ttyS0
crw--w----. 1 root 4, 64 Jun 26 10:57 /dev/ttyS0
But the other /dev/ttySx look like this:
ll /dev/ttyS*
crw--w----. 1 root 4, 64 Jun 26 10:57 /dev/ttyS0
crw-rw----. 1 root 4, 65 Jun 26 10:01 /dev/ttyS1
crw-rw----. 1 root 4, 66 Jun 26 10:01 /dev/ttyS2
crw-rw----. 1 root 4, 67 Jun 26 10:01 /dev/ttyS3