Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

how are people handling clock drift? #46

Open
nlf opened this issue Aug 6, 2015 · 3 comments
Open

how are people handling clock drift? #46

nlf opened this issue Aug 6, 2015 · 3 comments

Comments

@nlf
Copy link

nlf commented Aug 6, 2015

just wondering how other people are handling clock drift in their vms when the host machine is put to sleep and wakes up later. currently i'm just restarting ntpd in a cron job, but it's pretty hacky. any better solutions?

@jakajancar
Copy link

Well, if you're using ntpd, you don't have to restart it, just add the following to /etc/ntpd.conf:

tinker panic 0

But I was hoping using ntpd would not even be needed when I reported this.

@xez
Copy link
Contributor

xez commented Aug 10, 2015

Not a workaround but the reason this happens is that xhyve's timers stop when the host goes to sleep. When it wakes up again it doesn't account for the time sleeping and the timers keep ticking from their old value. To fix this xhyve would have to subscribe to sleep/wake notifications. I'll take a look when I find some time.

@bfreis
Copy link

bfreis commented Oct 26, 2016

Any updates on this issue? It's very annoying for Docker on Mac!

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants