Seasons Greetings!
We've had a minor case open with VMware support for 1 month now. We have a repeatable issue that can occur on any of our 2.5.3 hosts that are all managed with VC 2.01 (we're in the slow process of migrating our large farm to ESX 3.0x).
We started getting alerts from our monitoring software that console CPU resources we're at 100% and holding on random servers. The vpxa process which turns out to be the new VC agent was the culprit. Issuing a "service vmware-vpxa restart" will clear it up. We've found that the issue is generally repeatable through the process of vmotioning a guest OFF of a server whereby the sending server CPU0 goes to 100% and stays. VMotion TO a server will not affect the "receiving" server.
Anybody else seen this issue? Seems to be quite a few issues with VC2 managing prior versions of ESX.
VMware support has taken all the usual logs. I periodically ping them via email for status.. Over the last week or more I get no response from them. Is this typical for Platinum Support to not even provide you with status via an email request? I'd rather not have to get on the phone just to request status.
RAF
