VMware ESXi 5 CPU Affinity and DRS

I have a 4 host cluster in our VMware environment.  3 of the 4 hosts are identical boxes, and one is newer.  When I do a migration with one of our virtual machines between one of the older hosts and the new host, or vice-versa, it breaks our licensing for Pervasive SQL software.  I called support and Pervasive says this is expected, and if we want to have this in a virtual environment, then we need to setup CPU affinity for the VM hosting the Pervasive SQL server.  We have DRS enabled.  Am I still able to set CPU affinity for this VM?  Would I be better off assigning the VM itself to a physical host?  Or does DRS prevent that too?

Any ideas I'm not thinking of to address this issue?
Who is Participating?
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
Create a DRS Affinity rule to STICK the VM to a HOST, DRS will then NOT move the VM, and will not break your licensing.

Edit the Cluster, DRS, and Create a Rule.

We have a VOIP VM, with similar issues, because it uses the Machines CPU Serial Number!

So we "stick" it to a host, so it does not move!
jpletcher1Author Commented:
Do I also then need to set the specific VM to Manual under the individual VM listed in the DRS area "Virtual Machine Options"?  Or does setting the rule take care of everything?
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
That rule takes care of everthing.

Rules override everything when the VM is in the Cluster.

Just create a Rule.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.