the short explanation is that both the VM container and ntp adjust the
clock tick, and both think they are the only application that does so.
There are longer explanations in many places around the internet.
On 2008 May 21 (Wed) at 23:39:17 +0200 (+0200), Bj??rn T Johansen wrote: :Why not? I have been running ntp inside vmware for many years now, without any problems.... : :BTJ : :On Wed, 21 May 2008 12:30:01 -0700 :Peter Hessler <phessler@theapt.org> wrote: : :> never ever ever run ntp on virtual hardware. :> :> instead, run ntp on the host hardware, and tell the client to always :> obey the bios clock. I add "* * * * * /sbin/hwclock --localtime --hctosys" :> to my crontab for that.
-- "A power so great, it can only be used for Good or Evil!" -- Firesign Theatre, "The Giant Rat of Sumatra"