Clock Drift Issue between Dom-0 and Dom-U on OVM Server
Last updated on MARCH 08, 2018
Applies to:Oracle VM - Version 2.1 to 2.1.2 [Release OVM21 to OVM212]
Linux OS - Version Oracle Linux 5.5 with Unbreakable Enterprise Kernel [2.6.32] to Oracle Linux 5.5 with Unbreakable Enterprise Kernel [2.6.32] [Release OL5U5]
Information in this document applies to any platform.
Checked for relevance on 07-Jun-2013
By default xen.independent_wallclock is set to 0 which causes the clock of a paravirtual guest OS to be synchronized with the time of the control domain Dom-0. This setting implies only the control domain needs to synchronize with an NTP server. Over time the clocks can drift away though.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms