StepBee commented on issue #6807:
URL: https://github.com/apache/cloudstack/issues/6807#issuecomment-1287889614
In addition i compared again a custom offering vs a fixed offering and maybe
discovered the main difference at a different spot.
`virsh dumpxml` Custom constrained/unconstrained offering 4 vCPUs (`not`
working):
~~~
<vcpu placement='static' current='4'>64</vcpu>
<vcpus>
<vcpu id='0' enabled='yes' hotpluggable='no' order='1'/>
<vcpu id='1' enabled='yes' hotpluggable='no' order='2'/>
<vcpu id='2' enabled='yes' hotpluggable='yes' order='3'/>
<vcpu id='3' enabled='yes' hotpluggable='yes' order='4'/>
<vcpu id='4' enabled='no' hotpluggable='yes'/>
...
<vcpu id='62' enabled='no' hotpluggable='yes'/>
<vcpu id='63' enabled='no' hotpluggable='yes'/>
</vcpus>
<cputune>
<shares>1600</shares>
</cputune>
~~~
and a little more down the same xml:
~~~
<cpu mode='custom' match='exact' check='full'>
<model fallback='forbid'>Icelake-Server</model>
<vendor>Intel</vendor>
<feature policy='require' name='ss'/>
<feature policy='require' name='vmx'/>
<feature policy='require' name='hypervisor'/>
<feature policy='require' name='tsc_adjust'/>
...
<feature policy='disable' name='intel-pt'/>
<numa>
<cell id='0' cpus='0-63' memory='4194304' unit='KiB'/>
</numa>
</cpu>
~~~
Compared with
`virsh dumpxml` fixed offering 4 vCPU (**working**):
~~~
<vcpu placement='static'>4</vcpu>
<cputune>
<shares>1600</shares>
</cputune>
~~~
and a little more down the same xml:
~~~
<cpu mode='custom' match='exact' check='full'>
<model fallback='forbid'>Icelake-Server</model>
<vendor>Intel</vendor>
<topology sockets='1' cores='4' threads='1'/>
<feature policy='require' name='ss'/>
<feature policy='require' name='vmx'/>
<feature policy='require' name='hypervisor'/>
<feature policy='require' name='tsc_adjust'/>
...
<feature policy='disable' name='intel-pt'/>
</cpu>
~~~
Notice how the **fixed offering** **is defining** the cpus socket / cores /
threads
` <topology sockets='1' cores='4' threads='1'/>`
The **custom offerings** **does not define** the cpu / socket / thread model.
This would kind of make sense looking at the qemu error message
`... due to unsupported configuration: CPU topology doesn't match maximum
vcpu count`
What do you think?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
