CPU features are usually checked by libvirt, but not if libvirt decides it should not check the CPU at all, which happens with host-passthrough CPUs, for example. Let's check all used CPU features are valid for all CPU definitions. https://bugzilla.redhat.com/show_bug.cgi?id=1460086 Jiri Denemark (4): cpu: Introduce virCPUValidateFeatures qemu: Validate guest CPU features before starting a domain cpu_s390: Implement virCPUValidateFeatures cpu_x86: Implement virCPUValidateFeatures src/cpu/cpu.c | 29 +++++++++++++++++++++++++++++ src/cpu/cpu.h | 9 +++++++++ src/cpu/cpu_s390.c | 29 +++++++++++++++++++++-------- src/cpu/cpu_x86.c | 23 +++++++++++++++++++++++ src/libvirt_private.syms | 1 + src/qemu/qemu_process.c | 4 ++++ 6 files changed, 87 insertions(+), 8 deletions(-) -- 2.14.1 -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
