CPU Spike with DRS and VMotion20 January 2008 · Filed in Explanation
An issue has been discovered that can cause a CPU spike when VMotion is used in a DRS-enabled cluster with ESX Server 3.5 and VirtualCenter 2.5. It is my understanding that this can occur with both DRS-initiated VMotion operations as well as manually-initiated VMotion operations.
Fortunately, there’s a workaround for this issue which involves editing the
vpxd.cfg on the VirtualCenter server. Full details on the change that needs to be made, as well as on the log entries that you should see on ESX Server afterward, are found in this article.
UPDATE: It appears that VMwarewolf has had to pull the original article that described this problem and the workaround. Fortunately, Google has a long memory, and here’s the workaround for this problem.
Immediately after the
<vpxd> line in
vpxd.cfg, add the following lines:
<cluster> <VMOverheadGrowthLimit>5</VMOverheadGrowthLimit> </cluster>
I’m guessing that this information may not be information that VMware wants easily disseminated to the world, or that the workaround has not been fully and completely tested. So, use this information at your own risk.
UPDATE 2: VMware has now published this KB article about the issue, along with the workaround for the problem.Tags: ESX · VMotion · VMware · Virtualization Previous Post: Leopard Upgrade Next Post: Recent Virtualization Links