When CPU virConnectCompareCPU returns VIR_CPU_COMPARE_INCOMPATIBLE, the
caller has no clue why the CPU is considered incompatible with host CPU.
And in some cases, it would be nice to be able to get such info in a
client rather than having to look in logs.
Jiri Denemark (2):
cpuCompare*: Add support for reporting failure on incompatible CPUs
virConnectCompareCPU: Introduce FAIL_INCOMPATIBLE flag
include/libvirt/libvirt.h.in | 5 +++++
include/libvirt/virterror.h | 2 ++
src/bhyve/bhyve_driver.c | 17 +++++++++++++----
src/cpu/cpu.c | 10 ++++++----
src/cpu/cpu.h | 9 ++++++---
src/cpu/cpu_aarch64.c | 3 ++-
src/cpu/cpu_arm.c | 3 ++-
src/cpu/cpu_generic.c | 15 +++++++++++----
src/cpu/cpu_powerpc.c | 10 ++++++++--
src/cpu/cpu_x86.c | 20 ++++++++++++++++++--
src/libvirt.c | 9 +++++++--
src/qemu/qemu_driver.c | 17 +++++++++++++----
src/util/virerror.c | 6 ++++++
tests/cputest.c | 4 ++--
tools/virsh-domain.c | 11 +++++++++--
15 files changed, 110 insertions(+), 31 deletions(-)
--
2.0.0