Am 29.11.2016 um 16:40 schrieb Jim Fehlig <jfehlig@suse.com>:
Rieß Norman wrote:
Am 29.11.2016 um 08:48 schrieb Olaf Hering <olaf@aepfle.de>:
On Tue, Nov 29, Rieß Norman wrote:
we started using independent wallclock because the little timejump while live migrating was sufficient to disrupt some time dependent services. All our hosts (and VMs) use NTP, but the drift seems to be enough. Setting independent wallclock solved this behaviour. Are you saying that even with correctly running ntpd in both dom0s the migrated domU will see a timejump? A small jump forward is expected because the domU goes through a suspend/resume cycle while the last pages of dirty memory get transfered. I would be surprised if independent wallclock can change anything in this regard.
Olaf
Well, yes. This was the case several years ago. As the problem disappeared with the use of independent wallclock, we did not investigate in later releases.
To summarize the takeaway from this thread: The independent_wallclock control does not exist in the pvops kernel. If absence of this control causes problems, please enter a bug with the details.
Regards, Jim
You should update your documentation then. Norman N�����r��y隊Z)z{.���ۚ�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���ۚ��0�����Ǩ�