Skip to content

Commit

Permalink
fix up numa-topology live migration hypervisor check
Browse files Browse the repository at this point in the history
It turns out that even when KVM is supported by qemu the libvirt
driver will report the hypervisor type as "QEMU".  So we need to
fix up the hypervisor type check in the live migration code that
checks whether the instance has a NUMA topology.

Closes-Bug: #1818092
Change-Id: I5127227a1e3d76dd413a820b048547ba578aff6b
Signed-off-by: Chris Friesen <[email protected]>
  • Loading branch information
cbf123 committed Feb 28, 2019
1 parent b01da49 commit 4da0587
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 2 deletions.
5 changes: 4 additions & 1 deletion nova/conductor/tasks/live_migrate.py
Original file line number Diff line number Diff line change
Expand Up @@ -163,7 +163,10 @@ def _check_instance_has_no_numa(self):
# HyperV's vNUMA feature doesn't allow specific pinning
hypervisor_type = objects.ComputeNode.get_by_host_and_nodename(
self.context, self.source, self.instance.node).hypervisor_type
if hypervisor_type != obj_fields.HVType.KVM:

# KVM is not a hypervisor, so when using a virt_type of "kvm" the
# hypervisor_type will still be "QEMU".
if hypervisor_type.lower() != obj_fields.HVType.QEMU:
return

msg = ('Instance has an associated NUMA topology. '
Expand Down
2 changes: 1 addition & 1 deletion nova/tests/unit/conductor/tasks/test_live_migrate.py
Original file line number Diff line number Diff line change
Expand Up @@ -205,7 +205,7 @@ def test_check_instance_has_no_numa_passes_workaround(self, mock_get):
def test_check_instance_has_no_numa_fails(self, mock_get):
self.flags(enable_numa_live_migration=False, group='workarounds')
mock_get.return_value = objects.ComputeNode(
uuid=uuids.cn1, hypervisor_type='kvm')
uuid=uuids.cn1, hypervisor_type='QEMU')
self.task.instance.numa_topology = objects.InstanceNUMATopology(
cells=[objects.InstanceNUMACell(id=0, cpuset=set([0]),
memory=1024)])
Expand Down

0 comments on commit 4da0587

Please sign in to comment.