Oddly enough, this bug/issue is triggered by another SW product, Log & Event Manager. When I loaded up the vSphere appliance with the default resources (2 vCPUs), I noticed that VMan was alerting "VM CPU Underallocated". When I looked, though, it recommended "Increase 2 to 2". Hmm...
Well, it did look busy, so I raised the virtual appliance to 4 vCPUs. Now the alert is active again and suggests: "Increase 4 to 4". Am I missing something? That's not a recommendation and the virtual appliance isn't even using half of what it could now that it has 4 vCPUs (it's using the MHz from about 2 vCPUs).
Thanks,
Chris
