What is the virtual machine CPU Affinity in vSphere vCenter?
What this article shares to you is about the virtual machine CPU Affinity in vSphere vCenter. The editor thinks it is very practical, so I share it with you to learn. I hope you can get something after reading this article.
In VMware vSphere 6.7. in the vCenter management interface, you can set a parameter "Scheduling Affinity" for the CPU of the virtual machine, which means to lock a CPU, and be sure to use that CPU to provide the virtual CPU of the virtual machine. Literally translated as "nearest scheduling", difficult to understand, can be paraphrased as "CPU binding". If it is not set, it will be randomly assigned.
In the virtual machine settings interface, click the question mark after the parameter, you can see that this parameter has a very clear description.
0-3, using physical CPU numbered 0, 1, 2, 3.
0meme1Pol 3, using physical CPU numbered 0,1,3.
In the vSphere environment, there is also the Affinity and Anti-Affinity settings of the virtual machine, which is completely different from the Affinity of CPU. If virtual machine An is a Web server and virtual machine B is a database server, it is best to put them on the same physical host if they are to be used in pairs. Both need to be set to Affinity. Sometimes, virtual machines with similar functions, in order to ensure high availability, do not put eggs in the same basket and separate them as much as possible, they can be set to Anti-Affinity. The following figure shows the Affinity rule setting interface of the virtual machine.
The above is what the virtual machine CPU Affinity in vSphere vCenter is like, and the editor believes that there are some knowledge points that we may see or use in our daily work. I hope you can learn more from this article. For more details, please follow the industry information channel.
