I received some interesting comments from Brian S., in response to my DC VMUG announcement - Washington DC VMUG Presentation on Aug 20 2020 - TinkerTry home lab’s VMware vSphere 7.0 upgrade challenges, successes, and lessons learned.. He tipped me off to an issue I had started to notice in my home lab, so I added some words of caution to my recent upgrade to 7.0c video description, giving suitable warnings about possible high CPU utilization. Brian also referred me to this VMware VMTN post:
- High CPU after vCenter update 7.0b -> 7.0c
Aug 01 2020 by Raudi at VMTN Discussions
with the temporary workaround nicely documented by LaurensvanDujin back on Aug 03 2020, using VAMI to stop the Workload Control Plane service. This action immediately lowers the CPU back to normal levels, but also prevents the host from being able to enter into Maintenance Mode. Also, this workaround doesn't persist through VCSA reboots, so your VCSA CPU use will just spike again after a restart of VCSA.
If you're on a host like an Intel NUC with just 4 cores, you could see 100% CPU utilization. That's a significant bug, not the first one related to CPUs this year, and it's unfortunate this made its way past QA testing. Gladly, we have a community looking out for one-another, read onward.
By the way, while I don't know Brian personally, in case you're looking for a consultant, Brian S. is currently seeking new opportunities.
The resolved issues are grouped as follows.
- After an upgrade to vCenter Server 7.0.0c, you see high CPU usage
After you upgrade your vCenter Server system to vCenter Server 7.0.0c, CPU usage continuously stays high. On a single core, CPU usage might spike up to 100% for hours. The Workload Control Plane service causes the issue, even if you do not have Workload Management enabled in your environment.
This issue is resolved in this release.
Strangely, searching for 7.0.0d on Google comes up nearly empty at the moment, but here's the download page for the ISO:
Release Date: 2020-08-25
Build Number: 16749653
or just use VAMI's built-in Update feature:
I have just completed my VCSA 7.0.0d update process, it went smoothly, and my VCSA is now showing normal CPU utilization levels. I may even be able to return to 2 vCPUs assigned to this VM. I've just published a video of the CPU problem followed by a straight-forward Update to 7.0.0d. I also moved from 4 vCPU down to 2 vCPU, and from 12GB of RAM to 10GB of RAM, and 7.0.0d seems to be running quite well with those VM settings in my home lab with 4 hosts / 32 cores, and few dozen VMs that are mostly powered off.
I tried moving from 4v CPUs down to 2, and 12GB of RAM down to 10GB which required a reboot. Afterward, I got these warnings when logging back in with vSphere Client. Even though the steady-state RAM usage seems to hover around only 4GB of RAM, I'm happy to simply get rid of the error by giving it back the 12GB it apparently wants. I've deleted the 7.0.0c snapshot, and am ready to move on to other projects now.
All vSphere 7 articles.
All vSphere 7 videos.
- Strange thermal Issue after Update to ESXi 7.0b
Jul 2020 by Michael Schroeder at ELASTICSKY
After I’ve monitored one host with the new BIOS for a while and nothing strange happened, I decided to flash all of my E300-9D host with the new BIOS. Then I fired up the vSAN cluster and applied latest ESXi patches. These patches used to cause thermal issues in combination with the old BIOS 1.3 but now with 1.3a CPU temperature remaind at a normal level.
- vSphere Mobile Client
App Store Preview by VMware, Inc., for iPhone or iPad, seen also here at VMware Flings including Android version. It's only tested with 6.5, but the July 23 2020 v1.13.2 version seems to work fine with VCSA 7.0.0d.
- VCSA 7.0.0d available to fix high CPU
Aug 25 2020 by u/CodeMonk84 on reddit
- VMware vCenter 7.0.0c high CPU usage
Aug 03 2020 by LaurensvanDuijn at vdr.one
The Workload Control Plane service causes the issue, even if you do not have Workload Management enabled in your environment.
This issue is resolved in this release.