I use OpenSUSE in a VM and sometimes want to save the machine and get back to work later. I haven't had much success with hibernate or suspend, so I simply save the state of the machine and resume later.

Most of the time the clock is wrong and shows the time from when I saved it, which is somewhat expected. Eventually it will re-sync and work on it's own, but sometimes that takes an hour.

The strange part is also if I try to go and manually set the time of the click it will complain about the NTP dbus service not working, so I can't even fix the clock manually :(

The reason I care about this is because TLS negotiation (for SSL/HTTPS) usually fails if the clock is off by a few hours.

  • Should I set the date from the command line ?

  • Can I restart the time service somehow?

  • Is there a better way to save the machine? I would use suspend/resume but it doesn't do anything when I try.

  • What VM technology are you using? There may be a way to trigger a clock update when the machine state is restored. Apr 5, 2015 at 22:52
  • VirtualBox, not sure how CMOS timer style stuff is emulated Apr 8, 2015 at 10:31
  • @Gilles Stop removing the OpenSUSE tag please this question is related to OpenSUSE. Apr 11, 2015 at 20:03
  • 3
    No, this question should not have the opensuse tag. A distribution tag means “this question is specific to this distribution”, not “I am running this distribution”. Answers to your question do not depend on the distribution, or only in minor aspects, so this question should not have a tag that means “doesn't apply to other distributions”. Apr 11, 2015 at 20:36
  • 1
    How is syncing the time distro-specific? It has nothing to do with your distro Apr 11, 2015 at 22:18

1 Answer 1


Put ntpd -qg in /root/.profile and run it by invoking a login shell via su - first thing you log in.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .