Live-migration fails with CPU doesn't have compatibility
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Confirmed
|
Low
|
Vladik Romanovsky |
Bug Description
Live migration in nova does not seem to work as it fails with "CPU doesn't have compatibility" even between hosts with the exact same CPU models. This was introduced recently by the commit below. If I revert Nova to the offending commits parent, the live migration succeeds.
commit 79a0755597f4983
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
nova.conf's libvirt section on both nova nodes is:
[libvirt]
iscsi_use_multipath = True
vif_driver = nova.virt.
inject_partition = -2
live_migration_uri = qemu+ssh:
use_usb_tablet = False
cpu_mode = none
virt_type = kvm
and 'virsh capabilities' on both hosts show the same cpu information as follows:
<cpu>
<
<
<
<topology sockets='2' cores='1' threads='1'/>
<feature name='hypervisor'/>
<feature name='popcnt'/>
<feature name='vmx'/>
</cpu>
Changed in nova: | |
status: | New → Confirmed |
importance: | Undecided → Low |
Could you please add nova logs, so we could look into it?