Comments on: VMotion in 3.5 DRS enabled Cluster causes Guest CPU to rise Dramatically http://www.vmwarewolf.com/vmotion-in-35-drs-enabled-cluster-causes-guest-cpu-to-rise-dramatically/ Surplus Verbiage from a VMware Employee Fri, 05 Mar 2010 03:09:13 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: sandrar http://www.vmwarewolf.com/vmotion-in-35-drs-enabled-cluster-causes-guest-cpu-to-rise-dramatically/comment-page-1/#comment-637 sandrar Thu, 10 Sep 2009 22:14:17 +0000 http://www.vmwarewolf.com/vmotion-in-35-drs-enabled-cluster-causes-guest-cpu-to-rise-dramatically/#comment-637 Hi! I was surfing and found your blog post... nice! I love your blog. :) Cheers! Sandra. R. Hi! I was surfing and found your blog post… nice! I love your blog. :) Cheers! Sandra. R.

]]> By: Joe Fagnani http://www.vmwarewolf.com/vmotion-in-35-drs-enabled-cluster-causes-guest-cpu-to-rise-dramatically/comment-page-1/#comment-487 Joe Fagnani Wed, 18 Mar 2009 00:05:03 +0000 http://www.vmwarewolf.com/vmotion-in-35-drs-enabled-cluster-causes-guest-cpu-to-rise-dramatically/#comment-487 This is an Update 2 problem where the VM Overhead Growth Limit was set to zero (0) instead of minus 1 (-1). Set back to minus 1 (-1) in Update 3. With Update 2 and the fix, if you watch Syslog carefully, you see the value get set to zero, and after a while, the VC Setting comes along and it gets set to 5. I don't believe that VMware KB. In everything else, minus 1 (-1), means as-needed, unlimited, or the maximum value, so why should this be different? 1MB per minute seems ridiculously constrained and I don't think the Developers are trying to choke the VM? This is an Update 2 problem where the VM Overhead Growth Limit was set to zero (0) instead of minus 1 (-1). Set back to minus 1 (-1) in Update 3. With Update 2 and the fix, if you watch Syslog carefully, you see the value get set to zero, and after a while, the VC Setting comes along and it gets set to 5.

I don’t believe that VMware KB. In everything else, minus 1 (-1), means as-needed, unlimited, or the maximum value, so why should this be different? 1MB per minute seems ridiculously constrained and I don’t think the Developers are trying to choke the VM?

]]>