[Bug 1157914] Re: time never catches up to reality after VM sleep

[Martin Pitt]

This is first and foremost a QEMU or linux bug (not sure which), it
should really update its internal time after suspend. But I suppose ntp
could also listen to resume events (perhaps through pm-utils' /usr/lib
/pm-utils/sleep.d/ scripts); although this should already be covered by
its existing if-up.d script, i. e. as soon as the VM gets back online
after resuming /etc/network/if-up.d/ntpdate ought to run. It doesn't in
your case?

** Package changed: systemd (Ubuntu) = qemu (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1157914

Title:
  time never catches up to reality after VM sleep

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1157914/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1157914] Re: time never catches up to reality after VM sleep

[Charles Kerr]

So if the entire system's time is falling out of sync after sleep, this
isn't an indicator-datetime bug.

Reassigning to systemd... though I'm not positive this is the right
package

** Package changed: indicator-datetime (Ubuntu) = systemd (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1157914

Title:
  time never catches up to reality after VM sleep

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1157914/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs