Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

High CPU utilization of inactive Windows virtual machines (1077)

Last Updated: 3/21/2016Categories: TroubleshootingTotal Views: 174178Language:
Chinese (Simplified)Portuguese (European)JapaneseSpanishEnglishGerman

5 like this article

Subscribe to get an email
newsletter with new updates

5 people found this helpful Please provide article feedback:

Details

Servers utilization is high when Windows virtual machine is inactive.

Solution

When a physical or virtual machine is idle, its operating system either issues a halt instruction or repeatedly executes an idle loop.

When an idle virtual machine executes a halt, it stops processing all instructions and requires no cycles on the server's physical CPU. This is an expected behavior in a virtual machine and causes no performance problems.

When an idle virtual machine executes its idle loop, it is actively executing instructions which run on the underlying physical processor. In this case, performance tools in the guest operating system show an inactive operating system, but the CPU on the server is fully utilized.

Idle loop behavior occurs most often when you try to add virtual processors to a virtual machine. For more information, see the CPU Virtual Machine Configuration section of the vSphere Virtual Machine Administration Guide.

For a virtual machine running a Windows operating system, having the incorrect HAL (Hardware Abstraction Layer) installed makes the guest operating system always spin in its idle loop instead of halting. A virtual machine with two or more vCPUs configured should be running with a Multiprocessor or SMP HAL. A virtual machine with one vCPU configured should be running with a Uniprocessor HAL.

To determine which HAL your virtual machine is using and if you are running with the correct vCPU count for the HAL :

Note: Windows Server 2008 and later detected that HAL is at boot time and does not require changes.

Right-click My Computer icon, and click Properties.

Click the Hardware tab.

Click the Device Manager tab.

Double-click the Computer icon to see the HAL that is currently loaded.

In the vSphere or VMware Infrastructure client, click the virtual machine and, then click the Summary tab to see how may vCPUs are configured.

Your configuration is correct if:

You have one vCPU and your virtual machine operating system is configured for a Uniprocessor ACPI.

Your virtual machine operating system is configured for two or more vCPUs and is running with a Multiprocessor ACPI.

Note: Downgrading the HAL from multiprocessor to uniprocessor is not supported by Microsoft in Windows Server 2003 and it is not supported by VMware. For more information, see Cannot Select MPS Uniprocessor or ACPI Uniprocessor HAL.

You can add processors to a virtual machine that were created under ESX 2.x or higher and Workstation 5.5 or higher, but you must update the Windows HAL in your guest operating system. This is true if you are running a Windows 2000 guest operating system.
For more information on adding processors in:

ESXi 5.x virtual machines, see the Configuring a Virtual Machines section in the vSphere Virtual Machine Administration Guide.

ESX/ESXi 4.x virtual machines, see the Virtual Machine Hardware Configuration in the vSphere Basic System Administration Guide.

ESX 3.x virtual machines, see the Changing the Hardware Configuration of a Virtual Machine in the Basic System Administration Guide.

Workstation 7.0 virtual machines, see the Use Four-Way Virtual Symmetric Multiprocessing in the Workstation User's Manual

Workstation 6.5 virtual machines, see the Use Two-Way Virtual Symmetric Multiprocessing in the Workstation User's Manual

Note: When the correct HAL is installed, some guest operating systems halt more aggressively than others. When the system is inactive, some guest operating systems may spin in their idle loop for some time before issuing a halt instruction, whereas others may halt immediately. Typically, operating systems that spin in idle loops before halting are running with multiple processors.

For additional information about HAL, see Windows Virtual Machines with Latency-Sensitive I/O Workloads Can Slow Down in Four-Way SMP Configurations (2231) and the Microsoft Knowledge Base articles 309283 and 237556.

Note: The preceding links were correct as of August 25, 2015. If you find a link to be broken, provide feedback on the article and a VMware employee will update the article as necessary.

Additional Information
For translated versions of this article, see:

Deutsch: Hohe CPU-Auslastung von inaktiven virtuellen Windows-Maschinen (2144660)

Español: Uso intensivo de la CPU de máquinas virtuales de Windows inactivas (2073030)

Português: Alta utilização de CPU em máquinas virtuais do Windows (2018876)

日本語: 非アクティブの Windows 仮想マシンの高い CPU 使用率 (2078479)

简体中文: 非活动 Windows 虚拟机的高 CPU 利用率 (2074837)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)Portuguese (European)JapaneseSpanishEnglishGerman

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 vSphere ESXi

VMware Player

VMware GSX Server

VMware Fusion

VMware ESX Server

VMware ACE

Related Versions:

VMware Workstation 9.x (Windows)

VMware Workstation 9.x (Linux)

VMware Workstation 8.x (Windows)

VMware Workstation 8.x (Linux)

VMware Workstation 7.x (Windows)

VMware Workstation 7.x (Linux)

VMware Workstation 6.x (Windows)

VMware Workstation 6.x (Linux)

VMware Workstation 5.x (Windows)

VMware Workstation 5.x (Linux)

VMware Workstation 4.x (Windows)

VMware Workstation 4.x (Linux)

VMware Workstation 11.x (for Windows)

VMware Workstation 11.x (for Linux)

VMware Workstation 10.x (Windows)

VMware Workstation 10.x (Linux)

VMware vSphere ESXi 5.0

VMware Player Pro 7.x (Windows)

VMware Player Pro 7.x (Linux)

VMware Player 7.x (Windows)

VMware Player 7.x (Linux)

VMware Player 6.x (Windows)

VMware Player 6.x (Linux)

VMware Player 5.x (Windows)

VMware Player 5.x (Linux)

VMware Player 4.x (Windows)

VMware Player 4.x (Linux)

VMware Player 3.x (Windows )

VMware Player 3.x (Linux)

VMware GSX Server 3.x (Windows)

VMware GSX Server 3.x (Linux)

VMware GSX Server 2.x (Windows)

VMware GSX Server 2.x (Linux)

VMware Fusion 7.x

VMware Fusion 6.x

VMware Fusion 5.x

VMware Fusion 4.x

VMware Fusion 3.x

VMware Fusion 2.x

VMware Fusion 1.x

VMware ESXi 4.0.x Installable

VMware ESXi 4.0.x Embedded

VMware ESX Server 3.5.x

VMware ESX Server 3.0.x

VMware ESX Server 2.5.x

VMware ESX Server 2.1.x

VMware ESX Server 2.0.x

VMware ESX Server 1.5.x

VMware ESX 4.0.x

VMware ACE 1.0.x

view all

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