Re: NetBSD vs. VirtualBox

[email protected] ("Greg A. Woods") writes:

>I've probably also mentioned that so far I've been unable to get a
>NetBSD VirtualBox VM to maintain anything even close to accurate time,
>even with ntpd running.  Up for 15 minutes and it's already almost 3m
>behind!

Time keeping is a common problem of emulators.

Maybe changing kern.timecounter.hardware helps.
Virtualbox also has multiple options.

As a wild guess (I'm not using virtualbox), enabling HPET
in virtualbox and ensuring that the NetBSD timecounter
is also using HPET sounds like a working option.


>wsdisplay0: screen 7 added (default, vt100 emulation)

>wsconscfg: screen 0 is already configured
>wsconscfg: WSDISPLAYIO_ADDSCREEN: Device not configured
>wsconscfg: WSDISPLAYIO_ADDSCREEN: Device not configured
>wsconscfg: WSDISPLAYIO_ADDSCREEN: Device not configured
>wsconscfg: WSDISPLAYIO_ADDSCREEN: Device not configured
>wsconscfg: WSDISPLAYIO_ADDSCREEN: Device not configured
>wsconscfg: WSDISPLAYIO_ADDSCREEN: Device not configured


That says that for screens 1-6 you configured an unknown type,
that is the second argument to 'screen' in /etc/wscons.conf.

The available types are driver specific and "-" means to
use a driver default. The genfb driver knows only the
screen type "default".