Some virtualization solutions have a VM clock connected to some clock (nodes) of the host, so the VM clock does not quench independently. In other cases, such a thing cannot occur (for example, on the basis of an emulated interrupt clock), which in turn leads to a skewed clock. You can try to fight ntpd with a wall clock, but for things like CLOCK_MONOTONIC, you probably have to live with it.
source share