Comment 3 for bug 1370390

While it's true that this bug would cover the resize case that I mentioned in note #1 of bug #1417667, I think that we still need to keep that bug open for the more general case of live-migration, evacuate, rebuild, etc.

The key different for that bug is that when using dedicated CPUs we need to recalculate which CPUs to use on the destination compute node (and claim those resources) before actually doing the migration/evacuation/rebuild. As it stands, we'll continue to use the originally-specific vcpu/pcpu mapping, even though it may not be valid on the new host.