I want to do thsis for the whole cluster, not per each VM (i have 200+)
Tha nks,
Craig
I do not think you can or at least I can think of any way off the top of my head except maybe a bash script with sed
In VC 1.x it was just edit the .cfg file.
I sure hope they didn't remove that and instead making it a per vm..That would be detrimental.
Not sure you can do this, see this post...
http://www.vmware.com/community/thread.jspa?messageID=582038򎆖
thanks I tried adding that false for cpu checking, but that didnt seam to do anything...hrmm
Did you try restarting the VC server afterwards?
Yes but i'm not sure if I put it in the right area...
I'm not sure where it goes, there is no real documentation on it. The vpxd.cfg is only read at VC startup. This kb article has some info on modifying the vpxd.cfg...
http://kb.vmware.com/selfservice/viewContent.do?externalId=1993
Looks like it's only per VM on ESX 3 and VC 2.
\--SNIP From Your Link--
VirtualCenter Server 2.x
VirtualCenter Server 2.x provides two different ways to modify VMotion CPU constraints, depending on the version of ESX Server systems.
For ESX Server 3.x hosts, CPU constraints on a per-virtual-machine basis are editable through the Virtual Infrastructure Client (VI Client) graphical user-interface.
For ESX Server 2.x hosts (managed using VirtualCenter 2.0.1 Patch 2 and subsequent releases only), the CPU constraints can be edited directly in the VirtualCenter configuration file (vpxd.cfg).
ESX Server 3.x
In Virtual Center 2.x, the default bit mask for VMotion constraints among ESX Server 3.x systems is applied on a per-virtual-machine basis using the VI Client.
\--END SNIP--
I'm not sure where it goes, there is no real
documentation on it. The vpxd.cfg is only read at VC
startup. This kb article has some info on modifying
the vpxd.cfg...
http://kb.vmware.com/selfservice/viewContent.do?extern
alId=1993
I think that did it... I left work last night frustrated, came back in this morning only to see Vm's moved around the way i've been trying to do!!
So i think it worked!! We'll see today.