I recently built a new vmm with 6.4 and noticed this morning that it
had
a clock problem too, however all my other vmm's didn't.
FWIW, I don't have an issue with timekeeping on VMM clients on 6.4:
# uptime
4:40PM up 4 days, 22:29, 1 user, load averages: 0.00, 0.00, 0.00
# ntpctl -s all
1/1 sensors valid, clock synced, stratum 1
sensor
wt gd st next poll offset correction
vmmci0
* 1 1 0 15s 15s -0.227ms 0.000ms
I have same kern.timecounter values as you. However I rely on NTP of
the host
to keep good time. The clients are simply:
# ntpd.conf for our VMs
#
sensor *
While ntpd.conf for the host is the default:
#
servers pool.ntp.org
sensor *
constraints from "https://www.google.com";
And keeps time within a millisecond or so:
$ ntpctl -s all
4/4 peers valid, constraint offset 0s, clock synced, stratum 4
peer
wt tl st next poll offset delay jitter
69.17.158.101 from pool pool.ntp.org
1 10 3 207s 329s -0.050ms 72.067ms 7.430ms
72.38.129.202 from pool pool.ntp.org
1 10 2 285s 317s 1.819ms 80.729ms 2.943ms
198.50.139.209 from pool pool.ntp.org
1 10 2 278s 322s -5.043ms 87.529ms 8.652ms
207.34.48.31 from pool pool.ntp.org
* 1 10 3 1524s 1554s -0.425ms 30.868ms 3.349ms
Host CPU is old AMD:
OpenBSD 6.4 (GENERIC.MP) #364: Thu Oct 11 13:30:23 MDT 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD E-450 APU with Radeon(tm) HD Graphics, 6421.62 MHz, 14-02-00
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT,ITSC
cpu0: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 512KB
64b/line 16-way L2 cache
cpu0: 8 4MB entries fully associative
cpu0: DTLB 40 4KB entries fully associative, 8 4MB entries fully
associative
cpu0: smt 0, core 0, package 0
cpu0: apic clock running at 199MHz
cpu0: mwait min=64, max=64, IBE
--John
