
26 Jun
2014
26 Jun
'14
12:46 a.m.
On Wed, Jun 25, 2014 at 14:34:42 +0200, Jiri Denemark wrote:
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
I updated the virsh man page as requested by Peter, amended virConnectCompareCPU docs as suggested by Eric and pushed this series. Jirka