Knowledge Base

Search the Knowledge Base: |
Search the Knowledge Base: |
Virtual Machine Clock Reports Time Unpredictably on IBM x440/x445 Server or a Derivative System with a Windows Host Operating System
Details
Solution
If you are running VMware GSX Server or VMware Workstation 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.
This problem commonly occurs on IBM x440, x445, or x460 systems, or on Fujitsu, Siemens, or NEC derivatives of these systems. If you run GSX Server or Workstation on one of these multiprocessor systems and the clocks in your virtual machines are performing unpredictably, VMware recommends you apply the workaround described below.
Updating Your HAL Version
On IBM x440 and x445 servers (and derivative systems from Fujitsu Siemens or NEC, for example), running a Windows host operating system with a generic HAL (hardware abstraction level)provided by Microsoft can cause this bug to occur, as can running with versions of the IBM HAL earlier than 1.8.
To work around this issue, VMware recommends you install the latest IBM HAL specifically for the x440/x445. You can download the HAL from IBM's Web site. Go to www.ibm.com and search for x440 HAL. Perform the search in the Support and Downloads section. Make sure you use the Search field under Search technical support.
To determine what HAL you are running, complete the following steps.
- On the host, search for a file called hal.dll. It is generally found in C:\WINNT\system32 or C:\WINDOWS\system32.
- Right-click hal.dll and select Properties.
- Click the Version tab. The version information for your host's HAL appears here. Click each name in the Item name list to see its value.
A generic hal.dll from Microsoft typically lists copyright, company name, and product name information that mentions Microsoft. This item has a product version and file version that match the Windows version number. For example, on Windows 2000 Service Pack 4 system, the number may begin with 5.0.2195.
An IBM hal.dll typically lists copyright, company name, and product name information that mentions IBM, and has a product version (but not a file version) that begins with 1 or 2.
If you are running the generic Microsoft HAL or if you are running an IBM HAL with a product version number that does not match the one shown for your version of Windows on the IBM Web site, then download the latest HAL from the IBM Web site and install it according to IBM's instructions. As of this writing, the current IBM HAL versions are 2.4 for Windows 2000 and 1.41 for Windows Server 2003; VMware encourages you to check the IBM Web site for the latest version.
IBM x460 systems contain a more recent HAL version that is not affected by this issue. If an update is available for your x460 system's HAL, however, VMware suggests you apply the update.
Updating Your BIOS Version
If your IBM x440 or x445 server (or derivative system from Fujitsu, Siemens, or NEC) uses a BIOS older than version 1.18, you may experience problems running virtual machines on the server. Update the server's BIOS to version 1.18 or later.
IBM x460 systems contain a more recent BIOS version that is not affected by this issue. If an update is available for your x460 system's BIOS, however, VMware suggests you apply the update.
You should also read VMware knowledge base article 2039,
How to Run VMware Hosted Products on Systems on Which the TSCs Are Not in Sync.
Keywords
Feedback
- KB Article: 2040
- Updated: Aug 14, 2009
- Products:
VMware GSX Server
VMware Workstation - Product Versions:
VMware GSX Server 2.x (Windows)
VMware GSX Server 3.x (Windows)
VMware Workstation 3.x (Windows)
VMware Workstation 4.x (Windows)
VMware Workstation 5.x (Windows)

