having the same problem here.
ESXi: 6.7.0 Update 1 (Build 10302608)
ID GID NAME NWLD %USED %RUN %SYS %WAIT %VMWAIT %RDY %IDLE %OVRLP %CSTP %MLMTD %SWPWT 1 1 system 152 45.82 382.54 0.00 14532.68 - 54.70 0.00 16.19 0.00 0.00 0.00
Having the same problem here. ESXi: 6.7.0 Update 1 (Build 10302608). It seams is dependent on the hardware. I have the same build installed on 5 different machines and this issue occurs only on one of them : ASRock E3C226D2I mother board with Intel Haswell Core i3-4170 3.7 GHz CPU and 16GB RAM.
Maybe we could compare the different device drivers the hosts are using to maybe sort out the culprit which is causing this kind of overflow (?)
Same issue here,
HPE Microserver Gen10, Opteron X3421 and 16GB RAM, ESXi 6.7 U1.
Current uptime is 64 days and I can tell the system process peaks are making it heat up a bit judging from the fan throttling up and down.
Same problem on my side too ... forcibly I'm using ESXi 6.7 Update 1 on an Intel NUC8i7BEH.
Could that be the reason why after some days/weeks, CPU consumption from process "system" rise slowy until heating up the server and making the fans go high ?
NB : Even when I switch off all the VMs residing on this ESXi host, "system" process continues to consume CPU for no obvious reason.
After a reboot, everything gets back to normal.
I'm planning on switching to 6.7 Update 2 to see if things get better ... or same ... or worse maybe ?
Can someone please advise on that one if you had some informations from VMware.
I got this working with 6.5.0 Update 1 (Build 5969303) only! Because in my case its a homelab issue too, this is a sufficient workaround for me.
1 person found this helpful
We have the same issue with ESXi 6.7U1 build 10764712.We have this version running on different hardware generations (Xeon E5-2600v4 and older and newer generations), and all suffer from the same issue. Latency to VMs increases a lot after 49 days of uptime.
We also raised a case with VMware Support, they sent it to engineering but so far no solution. However, after some testing (which takes 49 days per iteration...) we reached the preliminary conclusion that the issue is not present in ESXi 6.7U2 build 13473784.