qemu: Filter CPU features when using host CPU

When reconnecting to a domain started with a host-model CPU which was
started by old libvirt that did not replace host-model with the real CPU
definition, libvirt replaces the host-model CPU with the CPU from
capabilities (because this is what the old libvirt did when it started
the domain). Without this patch libvirt could use features unknown to
QEMU in the CPU definition which replaced the original host-model CPU.
Such domain would keep running just fine, but any attempt to migrate it
will fail and once the domain is saved or snapshotted, restoring it
would fail too.

In other words whenever we want to use the CPU definition from host
capabilities as a guest CPU definition, we have to filter the unknown
features.

https://bugzilla.redhat.com/show_bug.cgi?id=1495171

Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
Reviewed-by: Pavel Hrdina <phrdina@redhat.com>
This commit is contained in:
Jiri Denemark 2017-10-06 13:23:36 +02:00
parent 3276416904
commit e26cc8f82f

View File

@ -6882,6 +6882,7 @@ qemuProcessRefreshCPU(virQEMUDriverPtr driver,
{
virCapsPtr caps = virQEMUDriverGetCapabilities(driver, false);
virCPUDefPtr host = NULL;
virCPUDefPtr cpu = NULL;
int ret = -1;
if (!caps)
@ -6903,7 +6904,13 @@ qemuProcessRefreshCPU(virQEMUDriverPtr driver,
if (!(host = virCPUCopyMigratable(caps->host.cpu->arch, caps->host.cpu)))
goto cleanup;
if (virCPUUpdate(vm->def->os.arch, vm->def->cpu, host) < 0)
if (!(cpu = virCPUDefCopyWithoutModel(host)) ||
virCPUDefCopyModelFilter(cpu, host, false,
virQEMUCapsCPUFilterFeatures,
&caps->host.cpu->arch) < 0)
goto cleanup;
if (virCPUUpdate(vm->def->os.arch, vm->def->cpu, cpu) < 0)
goto cleanup;
if (qemuProcessUpdateCPU(driver, vm, QEMU_ASYNC_JOB_NONE) < 0)
@ -6913,6 +6920,7 @@ qemuProcessRefreshCPU(virQEMUDriverPtr driver,
ret = 0;
cleanup:
virCPUDefFree(cpu);
virCPUDefFree(host);
virObjectUnref(caps);
return ret;