Drift file vmware

Supposedly updating regularly via ntp is not a good solution. Improve this question. Interested to know why ntp isn't supposed to be a good idea? What operating system is your Virtual Machine running? Add a comment. Active Oldest Votes. Read you vmware documentation carefully before you listen to anyone. We are running ESX5. Note: The directive tinker panic 0 must be at the top of the ntp. An example of such a configuration is: server Improve this answer.

David Leonard David Leonard 1, 1 1 gold badge 17 17 silver badges 14 14 bronze badges. As of late, many most? Linux kernels distributed are actually "tickless", a concept I can't explain but this thread can: kerneltrap. This was true 10 years ago.

Asclepius Linulin Linulin 3, 1 1 gold badge 18 18 silver badges 12 12 bronze badges. Atul Sengar Atul Sengar 11 1 1 bronze badge. Mark Biek k 53 53 gold badges silver badges bronze badges. Darren Kopp Darren Kopp Supposedly updating regularly via ntp is not a good solution That's the solution I would recommend, though. Why is it not considered good at your location? Mike Elkins Mike Elkins 1, 1 1 gold badge 10 10 silver badges 12 12 bronze badges.

Install NTP if you don't already have it. David Precious David Precious 6, 1 1 gold badge 22 22 silver badges 29 29 bronze badges. GHad GHad 9, 6 6 gold badges 33 33 silver badges 40 40 bronze badges.

Sign up or log in Sign up using Google. Sign up using Facebook. ERROR: adding a server to the tree. An operating system needs to have some way to schedule work in the future at a precise time. A processor supporting such an operating system must have a programmable interrupt timer that can periodically interrupt the processor in order for it to run scheduled work.

This periodic interrupt is known as a system clock tick. All activities are scheduled using this constant "heartbeat". Within the Linux kernel time is seen as the amount of clock ticks since the system booted.

This measurement is known as jiffies. The Linux 2. A dual-processor Linux 2. This is usually not an issue when running on a bare metal server under moderate load. However, issues can easily arise in a virtualized environment where multiple instances of the Linux kernel are in competition for the host's actual hardware based processor's attention. When the system gets busy for extended periods lost ticks can occur in a virtualized environment little actual guest OS activity is required.

When the interrupts are disabled for an extended amount of time ticks will pile up and the kernel can lose track of their count - they are considered lost. Due to the descrepency of how many interrupts the Linux kernel guest occurances can generate and the amount the ESX host kernel can service, lost ticks are a frequent concern.

Code was added to the 2. However, it is difficult at times to accurately detect when a tick was lost. Due to the way x86 queues the interrupt handlers an extra tick may be added by this code when, in fact, none were actually lost. These extra ticks can lead to time gaining or moving forward beyond the server's time source.

Lost ticks in themselves lead to time being lost time slowing from the source. To minimize time advancing beyond the time source due to the kernel's compensation code adding too many ticks use the following boot parameter:. The following settings and recommendations for Linux guests running under ESX should avoid timesync issues in this environment. The timesource should not be the ESX host itself nor a virtual server running under it. Doing otherwise will only add to a virtual machine's interrupt load and exacerbate the issue.

Start the NTP daemon again. Wait for this server to show a reach of by typing: ntpq -p. Make changes to the VMware Environment. This helps with time lagging. If you don't have accurate host time, see the end of this section for how to get that set up. If tries to synchronize with that as well, that can cause problems, as explained in detail in the VMware document. VMware says they disable this by default, but it may have gotten enabled again, especially if you'd been trying different fixes.

Since you have a Linux guest on the same host, I'd set up NTP there and let it keep the host clock up to date. Here is an excellent set of answers keeping a VM in good time sync, even though it's for a Linux VM, along with occasional bonus answers on why the problem occurs: How to keep a VMWare VM's clock in sync?

Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 9 years, 1 month ago. Active 9 years, 1 month ago. Viewed 3k times. Deruwyn Deruwyn 63 1 1 silver badge 5 5 bronze badges. This'd probably do better on serverfault. Add a comment. Active Oldest Votes. Why does it happen? How to fix it: If you have accurate host time, then I'm pretty sure an adequate solution is to have VMware Tools time sync every 60 seconds.

Place this in the VM's.