OPERATIONAL DEFECT DATABASE
...
...
Servers utilization is high when Windows virtual machine is inactive.
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 ManualWorkstation 6.5 virtual machines, see the Use Two-Way Virtual Symmetric Multiprocessing in the Workstation User's ManualNote: 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 InformationFor 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)
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
