Highlighted
Enthusiast
Enthusiast

Windows 2000 VM on ESXi 6.7 showing 100% utilization, yet VM is idle

Jump to solution

Title says it all.  Was wondering if anyone else was seeing this issue?

I have one lousy Windows 2000 VM still left in my environment.  In the midst of upgrading the cluster where it runs to 6.7.  When I move this VM to a 6.7 host, the VM goes in to alarm that CPU is at 100%, and performance charts via vCenter confirm that status.  The guest is reporting idle usage via the task manager on the VM itself.  Move it back to a 6.5 host and all goes back to normal.

I'm going to guess I'm hitting something like the following issue:

High CPU utilization of inactive Windows virtual machines (1077)  VMware Knowledge Base

Note that I am running the proper HAL for my device (Multiprocessor ACPI).  Did something change in this behavior that I just can't find documentation on?  I know Windows 2000 isn't supported anymore, but I'm sure there are others like me that have a handful of them still running in their environments.

1 Solution

Accepted Solutions
Highlighted
VMware Employee
VMware Employee

You might want to check out KB 2147608 VMware Knowledge Base

6.5 was the last release of  hypervisor binary translation mode, and you need to change the virtual machine to be configured as uniprocessor. I wonder if this is the cause in your case?

View solution in original post

6 Replies
Highlighted
Expert
Expert

Hi,

Well apart from the Guest OS...

Did you check esxtop stats?

VM config?

-------------------------------------------------------- "I greet each challenge with expectation"
0 Kudos
Highlighted
Immortal
Immortal

I’m facing the same problem right now

how did you manage to solve yours?

I’ve searched on other forums but I wasn’t able to find a solution

moderator edit: removed irrelevant hyperlinks

0 Kudos
Highlighted
VMware Employee
VMware Employee

You might want to check out KB 2147608 VMware Knowledge Base

6.5 was the last release of  hypervisor binary translation mode, and you need to change the virtual machine to be configured as uniprocessor. I wonder if this is the cause in your case?

View solution in original post

Highlighted
Enthusiast
Enthusiast

To answer Oziejfjdjfb, I have not solved my problem yet.  My fix was to migrate my VM back to a 6.5 host and pause my upgrade.

To TotesHagopes, I stumbled across that article as well in my later searching over the weekend.  I think you're correct, and the removal of that feature is causing the issue.  My guess is 6.5 and earlier just "threw away" the halt messages with the binary translation so we didn't get the high CPU utilization.  And now that we're no longer doing that, we see the described behavior.

Unfortunately, the article suggests that upgrading to Windows 2000 SP3 or SP4 would fix the issue.  That doesn't appear to be the case, as my VM is already running SP4.

For this particular VM, I think I would be able to downgrade to a single vCPU from a resource perspective, but that appears to not be supported (see the first article I referenced):

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

Of course, running Windows 2000 here isn't supported either, so not sure this is really an issue.  I may try it to see if this is a fix and let you all know.  Thanks for taking the time to take a look...

0 Kudos
Highlighted
Enthusiast
Enthusiast

After a little more digging and taking a clone of my VM to do some testing, I found that my issue appears to be tied to an individual processor type for me.

My Windows 2000 VM that was having problems sits on one of my older clusters running AMD processors.  When I created my clone, I put it on one of my newer Intel-based clusters and couldn't reproduce the problem.  So I moved the original VM to the Intel Cluster and the problem went away.  Not 100% sure why, but I'm still guessing that the removal of Binary Translation gave me some unexpected behavior changes.  Either way, it's working, so I'm going to leave it as is and still try to get this Windows 2000 VM off the wire.  I've not tried across more processor types, but this is what's working for me:

AMD Cluster with the problem : AMD Opteron 6380

Intel Cluster working : Intel Xeon E5-2690 v4

Hope this maybe helps someone out there with the same issue...

Highlighted
Enthusiast
Enthusiast

We have a couple of major SAP system still running on Windows 2000. After the upgrade to vSphere 6.7 we start to have the problem report.

After analysis, our servers has the latest VMware Tools whch are version 10.0.0.12, latest SP4 + Rollup installed. However, we do have configured them with 8 vCPU with 1 cores each that give 8 sockets total. The KB said that uniprocessor is now required for legacy solution.

We only change our setting for 1 vCPU with 8 cores in our settingsand all servers back to normal.

Smiley Happy