The host CPU definitions reported in the capabilities XML may contain CPU features unknown to QEMU, but the result of virConnectBaselineCPU is supposed to be directly usable as a guest CPU definition and thus it should only contain features QEMU knows about. https://bugzilla.redhat.com/show_bug.cgi?id=1450317 Jiri Denemark (7): cpu_conf: Introduce virCPUDefList{Parse,Free} cpu: Use virCPUDefListParse in cpuBaselineXML cpu: Don't log CPU models in cpuBaselineXML cpu: Drop cpuBaselineXML qemu: Pass virArch * to virQEMUCapsCPUFilterFeatures qemu: Publish virQEMUCapsCPUFilterFeatures qemu: Filter CPU features returned by qemuConnectBaselineCPU src/bhyve/bhyve_driver.c | 22 +++++++-- src/conf/cpu_conf.c | 78 ++++++++++++++++++++++++++++++++ src/conf/cpu_conf.h | 7 +++ src/cpu/cpu.c | 104 ------------------------------------------- src/cpu/cpu.h | 7 --- src/libvirt_private.syms | 3 +- src/libxl/libxl_driver.c | 22 +++++++-- src/qemu/qemu_capabilities.c | 8 ++-- src/qemu/qemu_capabilities.h | 3 ++ src/qemu/qemu_driver.c | 32 +++++++++++-- src/test/test_driver.c | 22 +++++++-- src/vz/vz_driver.c | 22 ++++++++- 12 files changed, 201 insertions(+), 129 deletions(-) -- 2.14.1 -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
