Hi Ian,
I think this is a common problem, and has been an issue from time to
time on KVM machines
also, you can try an alternate counter and see how you get on,
if you check out Mischa Peters talk on VMM he has some workarounds
that he has deployed in production.
but for an NTP server the accuracy
‐‐‐ Original Message ‐‐‐
On Tuesday, March 3, 2020 8:52 PM, Jordan Geoghegan wrote:
> The clocks are basically broken on vmm. The pvclock stuff is definitely
> an improvement, but it's still not there. There's still a ways to go
> before we have proper, reasonably accurate clocks for vmm
On 2020-03-03 07:43, mabi wrote:
Hello,
I am running an OpenBSD 6.6 VMM server with a few virtual machines also running
6.6 and noticed that one of them which is running Dovecot 2.3.9 package outputs
the following warning every few 10-15 seconds:
dovecot: imap: Warning: Time jumped forward
‐‐‐ Original Message ‐‐‐
On Tuesday, March 3, 2020 5:58 PM, Ian Gregory
wrote:
> I've had similar issues with timekeeping within guests of VMM,
> although there are improvements in -current with the pvclock time
> source. Since the fix below I now see occasional instances of the
> cloc
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
Hello,
I am running an OpenBSD 6.6 VMM server with a few virtual machines also running
6.6 and noticed that one of them which is running Dovecot 2.3.9 package outputs
the following warning every few 10-15 seconds:
dovecot: imap: Warning: Time jumped forwards 28.294585 seconds
It looks like the
6 matches
Mail list logo
