Description of problem:

During the Train release, we added support for live migration of pinned instances [1]. However, pinned instances - that is, instances with the 'hw:cpu_policy=dedicated' flavor extra spec or equivalent image metadata property - are not the only instances that are "pinned". If the '[compute] cpu_shared_set' config option or deprecated '[DEFAULT] vcpu_pin_set' config options are set on a host, then standard unpinned, non-NUMA instances will be "pinned" to the range of cores specified in this list. We do not currently account for this fact when live migrating an instance, meaning an instance moving from a host with neither of these options set to one with it set will not be updated. This RFE tracks the resolution of this oversight.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1222414