On 11/2/18 8:35 AM, Daniel Henrique Barboza wrote:
> Hi. Sorry for the late reply.
>
> On 10/11/18 9:03 PM, John Ferlan wrote:
>> On 10/4/18 9:14 AM, Daniel Henrique Barboza wrote:
>>> This patch makes two quality of life changes for non-x86 guests. The
>>> first one is a maxCpus validation at
Hi. Sorry for the late reply.
On 10/11/18 9:03 PM, John Ferlan wrote:
On 10/4/18 9:14 AM, Daniel Henrique Barboza wrote:
This patch makes two quality of life changes for non-x86 guests. The
first one is a maxCpus validation at qemuDomainDefValidate. The check
is made by the same function used
On 10/4/18 9:14 AM, Daniel Henrique Barboza wrote:
> This patch makes two quality of life changes for non-x86 guests. The
> first one is a maxCpus validation at qemuDomainDefValidate. The check
> is made by the same function used to do that at qemuProcessStartValidateXML,
> qemuValidateCpuCount.
This patch makes two quality of life changes for non-x86 guests. The
first one is a maxCpus validation at qemuDomainDefValidate. The check
is made by the same function used to do that at qemuProcessStartValidateXML,
qemuValidateCpuCount. This ensures that the user doesn't goes over the
board with t
