Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

Virtual Machine Clock Reports Time Unpredictably on Multiprocessor Systems (2041)

Last Updated: 8/5/2020Categories: TroubleshootingTotal Views: 37863Language:
JapaneseEnglish

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Details

The clocks in my virtual machines run in an unpredictable manner. Sometimes they run too quickly, other times they run too slowly, and sometimes they just stop. What is happening?

Solution

If you are running VMware desktop virtualization products on a multiprocessor system in which the timestamp counters (TSCs) do not remain synchronized between all processors, the operating system clock in each virtual machine can perform unpredictably. In this context, "multiprocessor" includes systems with multiple cores but only one processor socket.

This problem can occur on some 64-bit AMD systems and on some Intel systems. See the relevant information described in the following sections:

64-bit AMD Systems

Intel Systems

64-bit AMD Systems

This problem can occur on some 64-bit AMD multiprocessor (including multicore) systems. If you run VMware products on one of these systems and the clocks in your virtual machines are performing unpredictably, VMware recommends you apply the workaround described below.

Timestamp counters (TSCs) on 64-bit AMD systems should ideally remain synchronized because these systems run all CPUs from a common clock oscillator. However, some 64-bit AMD systems have power management features that can cause the TSCs on some processor cores to lose time in relation to other cores.

You might be able to disable these features:

In your system's BIOS setup windows, look for settings labeled PowerNow or Cool'N'Quiet, and disable them.

If you are running a Linux host operating system, look for a system daemon or applet called cpufreqd, cpuspeed, powernowd, cpudyn, speedy, or cpufreq, and disable it. For example, on some systems the command service cpuspeed stop might work. The instructions to disable the daemon or applet found on your system vary. Refer to your system's documentation for more information.

If you require these features or you cannot find a way to disable them, you need to assign each of your virtual machines to a subset of processor cores on which the TSCs do remain synchronized. In some cases you may need to do this even after turning off power management in your system's BIOS; this occurs if your system only partially disables the power management features involved.

Note: If you are running Windows XP Service Pack 2 as the host operating system on a multiprocessor 64-bit AMD host that supports processor power management features, you also need to apply the hotfix described in Microsoft knowledge base article 896256 at http://support.microsoft.com/?id=896256. According to this Microsoft knowledge base article, the hotfix is needed for the following operating systems:

Microsoft Windows Server 2003, Standard and Enterprise x64 Editions

Microsoft Windows XP Service Pack 2, when used with Microsoft Windows XP Home and Professional Editions

Microsoft Windows XP Tablet PC Edition 2005

No hotfix is needed for Microsoft XP Media Center.

Note: VMware knowledge base articles 2039, 2040, and 2041 replace knowledge base article 1236.

Intel Systems

This problem can occur on some Intel multiprocessor (including multicore) systems. After a Windows host performs a "stand by" or "hibernation", the TSCs may be unsynchronized between cores.

The hotfix described in Microsoft knowledge base article 896256 addresses this issue. See http://support.microsoft.com/kb/896256.

If you cannot apply the hotfix for some reason, as a workaround, do not use Windows "stand by" and "hibernation" modes.

Additional Information

For translated versions of this article, see:

日本語: マルチプロセッサ システムで仮想マシンのクロックが予期せずに時間を報告する (2101610)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Workstation

VMware Server

VMware Player

VMware GSX Server

Related Versions:

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant