We currently pin vCPUs automatically when adding/updating the virtual machine based on what of the hosts that the VM is pinned to (under the assumptions these hosts are the same). This RFE is about doing it based on the host that the VM is going to migrate on.
The scope of this bug is to address: "Live migration to a new host requires manually checking CPU and NUMA node availability on the new host and then reconfiguring pinning for the VM with new CPU and NUMA node ids." In bz 1729464
This bug was meant for Auto pinning feature (Resize and Pin NUMA). But, for that we will need to modify the CPU topology of the VM. Currently with the new dedicated feature, it seems much more relevant for it. We can modify the CPU pinning and NUMA pinning on migration.
We are past 4.5.0 feature freeze, please re-target.
verified in ovirt-engine-4.5.0.5-0.7.el8ev.noarch on the base of migration cases from the attached polarion plan