22 May
2018
22 May
'18
11:33 a.m.
On Wed, May 16, 2018 at 10:39:19 +0200, Jiri Denemark wrote:
The current virConnectCompareCPU and virConnectBaselineCPU APIs are not very useful because they ignore what a hypervisor can do on the current host. This series adds two new APIs which are designed to work with capabilities of a specific hypervisor to provide usable results.
The third CPU related API virConnectGetCPUModelNames is pretty useless too, but no new API with similar functionality is needed because domain capabilities XML already contains the relevant data.
Any comments? I'd like to have these new APIs in the upcoming 4.4 release. Jirka