Oh that is interesting ...
# ntpctl -s all
0/1 sensors valid, clock unsynced
sensor
wt gd st next poll offset correction
vmmci0
1 0 0 13s 15s - sensor not valid -
sensor not valid - why would that happen?
I have no idea about the inner workings of vmd .. but
On Wed, Nov 07, 2018 at 06:40:20PM +, Gareth Ansell scribbled:
# Hi, I can confirm that this is also happening on my VM, also hosted at
# openbsd.amsterdam.
# Gareth
Same here, and none of the tricks I was finding worked. I was also
unsatisfied with the idea of running rdate or restarting ntp
Oh that is interesting ...
# ntpctl -s all
0/1 sensors valid, clock unsynced
sensor
wt gd st next poll offset correction
vmmci0
1 0 0 13s 15s - sensor not valid -
sensor not valid - why would that happen?
I have no idea about the inner workings of vmd .. but m
One more update .. when I look at `ntpctl -sa` now, it does not show any
"peer not valid" errors. However, it still rons a good 14 seconds behind.
And it gets worse every minute.
# ntpctl -sa
4/4 peers valid, 1/1 sensors valid, constraint offset -115s (4 errors),
clock unsynced
peer
wt tl st
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 -
Here is an update on the situation:
I installed -current on this VM, clean install, and the ntpd error does not
happen anymore. But the clock issues remain, even with ntpd running.
The ntpd starts without complaints now, and seems to be running with its
regular processes:
_ntp 70093 0.0 0
Hi,
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.
kern.timecounter.tick=1
kern.timecounter.timestepwarnings=0
kern.timecounter.hardware=tsc
kern.timecounter.choice=i8254(0) tsc(-1000) dummy(-100)
These are
Hi, I can confirm that this is also happening on my VM, also hosted at
openbsd.amsterdam.
Gareth
On Sat, November 3, 2018 7:10 pm, Stefan Arentz wrote:
> Hi everyone,
>
> I am having an issue where an OpenBSD VM running on vmd is having
> serious clock skew issues.
>
> I am relatively new to OpenBSD, so I am not sure how to properly debug
> this. What I hope is that I can provide a good amount
Hi everyone,
I am having an issue where an OpenBSD VM running on vmd is having
serious clock skew issues.
I am relatively new to OpenBSD, so I am not sure how to properly debug
this. What I hope is that I can provide a good amount of data and folks
here can give me some hints and ask me for addit
10 matches
Mail list logo
