I have deployed a fresh ISO installation into ESXi without a serial interface connected to the VM.
Removing the `system console` node from the CLI and even after a reboot did not fix the issue. My syslog is spammed.
```
Dec 12 19:27:32 VMU-02-AZURE systemd[1]: serial-getty@ttyS0.service holdoff time over, scheduling restart.
Dec 12 19:27:32 VMU-02-AZURE systemd[1]: Stopping Serial Getty on ttyS0...
Dec 12 19:27:32 VMU-02-AZURE systemd[1]: Starting Serial Getty on ttyS0...
Dec 12 19:27:32 VMU-02-AZURE systemd[1]: Started Serial Getty on ttyS0.
Dec 12 19:27:32 VMU-02-AZURE agetty[3580]: /dev/ttyS0: not a tty
Dec 12 19:27:43 VMU-02-AZURE systemd[1]: serial-getty@ttyS0.service holdoff time over, scheduling restart.
Dec 12 19:27:43 VMU-02-AZURE systemd[1]: Stopping Serial Getty on ttyS0...
Dec 12 19:27:43 VMU-02-AZURE systemd[1]: Starting Serial Getty on ttyS0...
Dec 12 19:27:43 VMU-02-AZURE systemd[1]: Started Serial Getty on ttyS0.
Dec 12 19:27:43 VMU-02-AZURE agetty[3617]: /dev/ttyS0: not a tty
Dec 12 19:27:53 VMU-02-AZURE systemd[1]: serial-getty@ttyS0.service holdoff time over, scheduling restart.
Dec 12 19:27:53 VMU-02-AZURE systemd[1]: Stopping Serial Getty on ttyS0...
Dec 12 19:27:53 VMU-02-AZURE systemd[1]: Starting Serial Getty on ttyS0...
Dec 12 19:27:53 VMU-02-AZURE systemd[1]: Started Serial Getty on ttyS0.
Dec 12 19:27:53 VMU-02-AZURE agetty[3624]: /dev/ttyS0: not a tty
```
Deleting the service by hand did not fix it.
```
$ sudo systemctl disable serial-getty@ttyS0
Removed symlink /etc/systemd/system/getty.target.wants/serial-getty@ttyS0.service.
```