Solaris time drifts when a local zone is configured with an offset of virtual zone clock from the global system clock
(Doc ID 2188937.1)
Last updated on SEPTEMBER 05, 2019
Applies to:Solaris Operating System - Version 11.3 to 11.3 [Release 11.0]
Oracle Solaris on SPARC (64-bit)
Starting with Solaris 11.3 a local zone can be configured to have its own time configuration different from the one on the global zone, through the configuration of the global-time property, which can be set to false so the local zone can change the zone-specific time.
When there is high CPU load on a local zone that has the zonecfg(1M) property global-time configured to false to have the zone-specific time, the time on the global zone can jump and if NTP is enabled it could go into maintenance state, with the following errors on the /var/adm/messages file:
Also cron jobs could fail and the cron daemon will be restarted.
This issue happens on SPARC platforms running Solaris 11.3 without SRU 12.4 or later.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document