After editing and saving virtual machine settings using the ESXi Host Client, you may observe that the parameter sched.cpu.affinity = "all" is added to the virtual machine configuration file (.vmx).
This parameter is not present when the virtual machine is initially created via vCenter Server or the vSphere Client.
VMware vSphere ESXi ESXi Host Client
When settings are saved via the ESXi Host Client, the user interface validates the CPU affinity settings. If no specific affinity is defined (which is the default), the ESXi Host Client explicitly writes sched.cpu.affinity = "all" to the configuration file. This differs from the vSphere Client behavior, which typically leaves the entry absent for the default configuration.
No action is required.
The setting sched.cpu.affinity = "all" explicitly states that the virtual machine is allowed to run on all available logical processors. This is functionally identical to the default behavior when the parameter is absent from the configuration file.
The presence of this parameter does not negatively impact performance or scheduling. It is not necessary to remove this line from the .vmx file.