[...]
>>> @@ -399,7 +412,16 @@ virDomainCapsCPUFormat(virBufferPtr buf,
>>>virCPUModeTypeToString(VIR_CPU_MODE_CUSTOM));
>>> if (cpu->custom && cpu->custom->count) {
>>> virBufferAddLit(buf, "supported='yes'>\n");
>>> -virDomainCapsCPUCustomFormat(buf,
On Mon, Aug 29, 2016 at 19:21:24 -0400, John Ferlan wrote:
...
> > @@ -183,6 +183,10 @@
> >
> > The mode element contains a list of supported CPU
> > models, each described by a dedicated model element.
> > +The usable attribute specifies whether the model can
> >
On 08/12/2016 09:33 AM, Jiri Denemark wrote:
> In case a hypervisor is able to tell us a list of supported CPU models
> and whether each CPU models can be used on the current host, we can
> propagate this to domain capabilities. This is a better alternative
> to calling virConnectCompareCPU for e
In case a hypervisor is able to tell us a list of supported CPU models
and whether each CPU models can be used on the current host, we can
propagate this to domain capabilities. This is a better alternative
to calling virConnectCompareCPU for each supported CPU model.
Signed-off-by: Jiri Denemark
