It would be a bit of work, but I'd consider looking at how the host clock is exposed by vmt(4) and whether vmm(4) and vmmci(4) could/should be extended in the same way. If so, you could use Ted Unangst's solution to a similar problem with VMWare guests.
http://www.tedunangst.com/flak/post/vmtimed On Fri, Feb 10, 2017 at 1:57 AM, Stuart Henderson <[email protected]> wrote: > On 2017-02-09, Eric Brown <[email protected]> wrote: > > Dear List, > > > > I've recently learned (and discovered) that time in VM's is tricky > > business. I'm looking for the least stupid way to keep any semblance of > > time in vmd instances while I hungrily await a "correct solution" to > > descend from the heavens. > > > > I've disabled openntpd, installed ntp package (but not its daemon). Now > > I am running ntpdate every minute from cron. It seems to keep the > > clock, well, within a minute. > > > > Can anyone think of a better solution to this problem? > > Not a hugely better solution, but rdate(8) is in base, so at least you > don't need the ntp package..
