Re: [Bug 1157914] Re: time never catches up to reality after VM sleep
On Mar 11, 2014, at 04:54 AM, Serge Hallyn wrote: Thanks for filing this bug. I'd like to try to reproduce it but need a few more details. Can you tell us exactly how you set up the vm, how you start it, and how you initiate suspend? Is this all done through virt-manager? You say it is a vmware fusion vm - does that mean you started with a .vmdk of an appliance, converted it to qcow2 or raw, and are using that? If not, what does it mean? This is a Trusty guest running in VMware Fusion 6.0.2 on an OS X 10.9.2 host. Trusty was installed fresh some time ago and has been rolling updated ever since. When you quit Fusion, it suspends the VM. You can of course suspend the VM explicitly any other time. You can also take a disk snapshot and restore that snapshot at a later date. All of these exhibit the same symptom - the VM's time gets behind, sometimes by a long while, and it never catches up. If you go to System Settings (in Ubuntu of course) - Time Date, and look at Set time: then Automatically from the Internet is set. What this implies to me at least, is that the system will keep its time in sync with the network servers. I would thus expect that when the VM is resumed, it would eventually catch up either with the real time. What I think is happening is that this settings panel actually only has an effect at system boot time. Can you confirm whether this setting should periodically sync system time to the internet servers, or whether ntp must be installed in order to keep time in sync. ntp is *not* currently installed. I'm perfectly willing to accept that ntp is required in order for a suspended VM's time to resync with internet server time. If that's the case, then I think we have a design bug here - the Automatically from the Internet setting is either misleading, or should prompt to install ntp (maybe with panic 0 set?). At one point I think this did happen. However, if this setting is supposed to keep time in sync without ntp, then there's a functional bug here. I'm mostly trying to get verification on what expected behavior is. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1157914] Re: time never catches up to reality after VM sleep
Thanks, Barry. So IIUC this has nothing to do with qemu, so I'm switching it to linux. Is it safe to assume that other VMs - other Ubuntu releases, or other distros, or windows, do not have this behavior? ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu) Status: Incomplete = Invalid ** No longer affects: qemu (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu 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/linux/+bug/1157914/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1157914] Re: time never catches up to reality after VM sleep
Hi, Thanks for filing this bug. I'd like to try to reproduce it but need a few more details. Can you tell us exactly how you set up the vm, how you start it, and how you initiate suspend? Is this all done through virt-manager? You say it is a vmware fusion vm - does that mean you started with a .vmdk of an appliance, converted it to qcow2 or raw, and are using that? If not, what does it mean? ** Changed in: qemu (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1157914] Re: time never catches up to reality after VM sleep
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 Server Team, which is subscribed to qemu 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1157914] Re: time never catches up to reality after VM sleep
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qemu (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1157914] Re: time never catches up to reality after VM sleep
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 Server Team, which is subscribed to qemu 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
