On Wed, Aug 24, 2022 at 11:40 AM Uwe Schindler <u...@thetaphi.de> wrote: > > Hi, > > this is the MacOS virtualbox. This one often hast timeshifts caused by > Virtualbox and the NTP daemon of OSX is bullshit (no chrony). > > Actually earlier versions of MacOS had a bug in their OS libc > segfaulting the app to crash on backwards jumps of wall time, which was > fixed a few years ago. Now it looks like sometimes only Gradle/Java > hangs because of this. Macos and backwards-jumping time do not fit well! > Maybe a reason why Apple does not like their OS virtualized :-) Their > bullshit kernel only works for 100% INTEL CPUs with all hardware > behaving exactly in order to time. >
Honestly, some of it is the virtualbox, too. Once you eliminate or workaround wall-clock time and just deal with monotonic time, there can still be annoying issues with just monotonic time. With a linux guest, you'll see strange stuff, such as kernel's softlockup detector trip a lot when this happens. There are corresponding errors printed in the vbox logging too. I set VBOX_RELEASE_LOG_DEST to allow archiving the virtualbox VM log for jenkins pickup along with other logs: it helps with debugging shit like this. For linux guest, I basically exhausted all possible kernel clock sources, and found the kvm-clock virtualized one that happens by default is the best by far. I'm guessing MacOS may not support this, which probably makes things worse there. I found in my environment for linux guests, remaining timer issues can be greatly improved with a 'vboxmanage setextradata <vmid> VBoxInternal/TM/TSCModeSwitchAllowed 0'. Don't ask me what it does :) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
