On Tue, 3 Mar 2020 at 15:47, mabi wrote:
> It looks like there is a time issue on that VM although I am running the
> default ntpd of OpenBSD 6.6 and I have added the following parameter into my
> /etc/sysctl.conf on that VM:
>
> kern.timecounter.hardware=tsc
I've had similar issues with timeke
On Tue, 19 Nov 2019 at 21:20, Ian Gregory wrote:
> I can
> confirm that change resolved the precision issue described in the
> linked thread, but it also seems to have resulted in much improved
> clock stability (4 steps in 24hr, 1.0s, 1.0s, 0.5s, 0.5s).
Correction - there wer
nt ntpd is able to keep the clock synced so in the absence
of further lines of investigation I'm inclined to leave as-is and
continue to monitor. I will update the list if I discover anything
new.
Ian
On Fri, 15 Nov 2019 at 09:17, Ian Gregory wrote:
>
> I continued to investigate this
dvise if I've missed something? Happy to provide further
data if needed.
Thanks
Ian
On Fri, 8 Nov 2019 at 13:53, Ian Gregory wrote:
>
> Hi
>
> Since the 6.6 release I've been experimenting with using pvclock as
> the selected timecounter on a virtual machine running under v
Hi
Since the 6.6 release I've been experimenting with using pvclock as
the selected timecounter on a virtual machine running under vmm. Both
the host and guest are running 6.6-stable (the environment is provided
by openbsd.amsterdam).
With 6.5 and the tsc source, the clock would drift linearly by
5 matches
Mail list logo
