On Wed, Oct 18, 2017 at 12:07:16PM -0700, Mike Larkin wrote: > On Sat, Oct 14, 2017 at 01:31:28PM -0600, Shane Harbour wrote: > > On 10/14/2017 13:01, x9p wrote: > > > Hi, > > > > > > While running Alpine-virt 3.6.2 VM guest under OpenBSD 6.1 host, i noticed > > > the clock frequency is 2x slower on the guest machine. This can be a > > > problem for applications that relies on accurate time. > > > > > > Even after sync clock with ntpd inside alpine-virt guest, it gets > > > out-of-sync a few seconds later. I get on the guest about half the clock > > > frequency of the host. > > > > > > Anyone having similar problems? > > > > > > cheers. > > > > > > x9p > > > > > > > I've noticed the same thing on my laptop running an amd64 6.2 install. It > > was really very slow to install and slow via console and ssh now that I've > > got it running. I just thought it was something I had done/was doing. Even > > with ntpd running, it's now way behind. > > > > Regards, > > Shane > > > > You should be able to set the timecounter source to 'tsc' in VMs running in > -current. It is not the default choice (so set it in sysctl.conf if you want > that). That should greatly help reduce time drifts. > > You will really need -current though as the fix for this went in today. > > -ml
To be super clear - you need -current on both the host and VM. -ml
