On Mar 08, 2014, at 04:59 PM, Martin Pitt wrote: >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?
Please note that this is a VMware Fusion VM. ntp is not installed, but if you go to System Settings -> Time & Date, you will see that "Set the time" is set to "Automatically from the Internet". Shouldn't this be enough to have time catch up after resume from VM suspend? If not, and ntp is actually required (as was the case way back when), then I rather think that the System Setting is misleading. I can handle installing and running ntp, as I used to do, but I think this is a regression (hard for me to remember exactly). So, if ntp is required not installed, what effect does the Time & Date dialog actually have, other than dimming the Time and Date widgets? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
