That works too - On 15 September 2017 at 21:28, Maksym Sheremet <mshere...@sheremets.com> wrote:
> On Thu, 14 Sep 2017 23:46:14 +1200 > Joel Wirāmu Pauling <aener...@aenertia.net> wrote: > > > Run NTPd on the hypervisor and NTP client In VM. Run ntpdate at boot > before > > starting NTPd on the client to ensure the stepping is not too far off > > first. > > What is the reason to run ntpdate on boot? The "-s" flag of ntpd(8) sets > time immediately at startup. > > > > > On 14 Sep. 2017 11:35 pm, "Aaron Marcher" <m...@drkhsh.at> wrote: > > > > Hi all, > > > > I have a weird problem on my OpenBSD server. It is a virtualized guest > > under QEMU-KVM. Apperently time management is completely off. With HPET > and > > normal HW-clock the command "time sleep 1" shows a little bit more than a > > second after a fresh boot. After a few hours the result is about 10 > > seconds. Additionally the clock drifts slowly. The problem is on OpenBSD > > 6.1 with all syspatches applied. > > Does anybody know how to fix the problem? > > Thank you very much in advance! > > > > Regards, > > Aaron Marcher > > > >
