libvirt: fix overly strict CPU model comparison in live migration
The current libvirt driver migration code checks whether the
dest host can support the guest, by comparing the source host
CPU model. This is overly strict, as the guest may well be
running with a more restrictive CPU model that hides many
host features. The correct approach is to compare against
the guest's configured CPU model.
To achieve the compatibility when migrate instance from old compute
node which does not provide vcpu_model in instance object, the source
host's compute info is still provided.
Co-authored: Daniel P. Berrange <email address hidden>
Co-authored: Yunhong Jiang <email address hidden>
Reviewed: https:/ /review. openstack. org/53746 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=79a0755597f 4983367eb0caf46 69ffb881b4f720
Committed: https:/
Submitter: Jenkins
Branch: master
commit 79a0755597f4983 367eb0caf4669ff b881b4f720
Author: yunhong jiang <email address hidden>
Date: Fri Feb 6 07:03:45 2015 -0800
libvirt: fix overly strict CPU model comparison in live migration
The current libvirt driver migration code checks whether the
dest host can support the guest, by comparing the source host
CPU model. This is overly strict, as the guest may well be
running with a more restrictive CPU model that hides many
host features. The correct approach is to compare against
the guest's configured CPU model.
To achieve the compatibility when migrate instance from old compute
node which does not provide vcpu_model in instance object, the source
host's compute info is still provided.
Co-authored: Daniel P. Berrange <email address hidden>
Co-authored: Yunhong Jiang <email address hidden>
Closes-Bug: 1082414
Change-Id: I65f505fec64c65 d2641d2bfd940cd e44bcd83a78