0

The VMware document titled "Timekeeping in VMware Virtual Machines" have the following referente to the issues with the time drift:

If the virtual machine is running too slowly, perhaps as a result of competition for CPU time from other virtual machines or processes running on the host machine, it might be impossible to feed the virtual machine enough interrupts to keep up with real time. In current VMware products, if the backlog of interrupts grows beyond 60 seconds, the virtual machine gives up on catching up, simply setting its record of the backlog to zero.

Where is this backlog counter and how can I read it to monitor this behaviour?

Improve this question
5
  • What problem are you experiencing?
    – ewwhite
    Aug 14, 2017 at 16:00
  • 2
    Be aware that the doc you point to is several years old. Vmware (and linux distributions) have changed since then. See kb.vmware.com/selfservice/microsites/…
    – Dan Pritts
    Aug 14, 2017 at 19:18
  • I agree with @DanPritts, you shouldn't have any timekeeping problems with somewhat current Linux versions... and we're not talking about the latest versions, RHEL6 and SLES11 are already quite old in my view.
    – Mario Lenz
    Aug 15, 2017 at 20:07
  • Monitor this behaviour is helpfull because the recomendations only cover the issue, not fix the origin of the problem. Maybe the ntp is fixing the time frequently because there are a lot of vm in a host, in this case, the time is right, but the issue is in the background.
    – rfmoz
    Aug 24, 2017 at 7:55
  • Note that if you stop using vmware tools, the interrupt disruption certainly under windows vms goes down dramatically. It goes down from 20% cpu usage to practically zero. There's something very wrong with VMware tools!
    – Owl
    Aug 31, 2018 at 14:29

0

Reset to default

You must log in to answer this question.