On Mon, Apr 23, 2018 at 7:43 AM, Tom Jones <t...@freebsd.org> wrote: > On Tue, Mar 13, 2018 at 09:38:54AM +0000, Roger Pau Monné wrote: > > Author: royger > > Date: Tue Mar 13 09:38:53 2018 > > New Revision: 330834 > > URL: https://svnweb.freebsd.org/changeset/base/330834 > > > > Log: > > vt_vga: check if VGA is available from ACPI FADT table > > > > On x86 the IA-PC Boot Flags in the FADT can signal whether VGA is > > available or not. > > > > Sponsored by: Citrix systems R&D > > Reviewed by: marcel > > Differential revision: https://reviews.freebsd.org/D14397 > > > > Modified: > > head/sys/dev/vt/hw/vga/vt_vga.c > > Hi, > > Running the latest vm snapshots on bhyve, /dev/ttyv[0-b] devices are not > created leading to getty spamming the console: > > Apr 23 13:28:49 freebsd getty[710]: open /dev/ttyv6: No such file or > directory > Apr 23 13:28:49 freebsd getty[709]: open /dev/ttyv1: No such file or > directory > Apr 23 13:28:49 freebsd getty[715]: open /dev/ttyv5: No such file or > directory > Apr 23 13:28:49 freebsd getty[713]: open /dev/ttyv7: No such file or > directory > > Tracking through snapshots the change is somewhere between: > > good ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/ > 12.0-CURRENT/amd64/20180307/ > bad ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/ > 12.0-CURRENT/amd64/20180315/ > > reverting r330834 returns to the old behaviour. >
You need to change /etc/ttys to have 'onifexists' or 'off' for those devices. There was a change to init/getty to support pluggable TTYs that is causing it. Historically, there was no 'onifexists' so init/getty basically stopped looking at a device that wasn't there. Now we have TTYs that we want to present a getty on come and go, we need to adapt. Warner _______________________________________________ svn-src-head@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-head To unsubscribe, send any mail to "svn-src-head-unsubscr...@freebsd.org"
