Red Hat Bugzilla – Bug 867867
Migration of CPU pinned VM's is enabled by default
Last modified: 2016-02-10 15:17:04 EST
Description of problem:
Currently migration of CPU pinned VM's is disabled on downstream, but CpuPinMigrationEnabled is set to true.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
After running rhevm-setup, run:
echo "select * from vdc_options where option_name='CpuPinMigrationEnabled'" | psql -U postgres -d engine
CpuPinMigrationEnabled is set to true
CpuPinMigrationEnabled should be set to false
Indeed RHEV should have CpuPinMigrationEnabled set to false.
Indeed, however you must give a good explanation of this parameter in RHEV Config file for the implication of setting to true
Something like: If set to true, allows migration for Virtual Machines that have CPU pinning. Note that the migration may fail if the destination host does not have a topology that corresponds to the CPU pinning. It is recommended allowing this only if all the hosts in the cluster have the same CPU topology.
Doron, do we also enforce pin to host? If not then what happens if the scheduler tries to run it on a host that does not have a matching topology? If yes, what happens if the values set in the field do not match the selected host?
Some more info as I wrote in a related bug 867039:
CPU pinning is controlled by 2 configurations;
CpuPinningEnabled configuration value, which has cluster compatibility level and has to be true in the first place.
Next, CpuPinMigrationEnabled configuration value should be set to True to enable pinning. Otherwise pinning is disabled.
Another valid combination for pinning is CpuPinMigrationEnabled set to false, and one of the pin-to-host radio buttons in the UI is checked.
So in first combination, we allow pinned VMs to be migrated. This is what upstream is doing.
In the other combination, we'll only allow pinning if the VM is pinned to host.
This is the default we need, in order to protect from marking hosts as problematic in case of multiple migration failure.
OK - SI22
CpuPinMigrationEnabled is now set to false by default.