Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

VMware ESXi 5 CPU Affinity and DRS

Posted on 2012-08-27
3
Medium Priority
?
1,506 Views
Last Modified: 2012-08-27
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?
0
Comment
Question by:jpletcher1
  • 2
3 Comments
 
LVL 124

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 1200 total points
ID: 38338263
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.

Rules
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!
0
 

Author Comment

by:jpletcher1
ID: 38338296
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?
0
 
LVL 124
ID: 38338303
That rule takes care of everthing.

Rules override everything when the VM is in the Cluster.

Just create a Rule.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
It’s time for spooky stories and consuming way too much sugar, including the many treats we’ve whipped for you in the world of tech. Check it out!
This Micro Tutorial steps you through the configuration steps to configure your ESXi host Management Network settings and test the management network, ensure the host is recognized by the DNS Server, configure a new password, and the troubleshooting…
This course is ideal for IT System Administrators working with VMware vSphere and its associated products in their company infrastructure. This course teaches you how to install and maintain this virtualization technology to store data, prevent vuln…
Suggested Courses

810 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question