StepBee commented on issue #6807:
URL: https://github.com/apache/cloudstack/issues/6807#issuecomment-1289435726
@DaanHoogland thanks for the correction.
I tested the agent.properties setting, unfortunately without any change in
results.
What makes it even harder to analyze, that i don't have this issue on our
staging environment - i perfectly see the cpu topology in the xml on newly
created VMs with custom service offering there and can run vms based on custom
offerings and >2 vCPUs.
Production and staging have the same setting for the guest cpu mode in
agent.properties:
`guest.cpu.mode=host-model`
They have the same settings for the custom service offering, the same
settings for the fixed service offering.
For testing i created a new custom constrained service offering on our
production system, but the issue stays.
Whats interesting:
In the working XML of a VM based on custom serviceoffering and >2 vCPUs in
the staging environment i don't see any lines like:
(taken from the non-working production system which is missing the cpu
topology)
~~~
<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='5' enabled='no' hotpluggable='yes'/>
<vcpu id='6' enabled='no' hotpluggable='yes'/>
<vcpu id='7' enabled='no' hotpluggable='yes'/>
<vcpu id='8' enabled='no' hotpluggable='yes'/>
<vcpu id='9' enabled='no' hotpluggable='yes'/>
<vcpu id='10' enabled='no' hotpluggable='yes'/>
<vcpu id='11' enabled='no' hotpluggable='yes'/>
<vcpu id='12' enabled='no' hotpluggable='yes'/>
<vcpu id='13' enabled='no' hotpluggable='yes'/>
<vcpu id='14' enabled='no' hotpluggable='yes'/>
<vcpu id='15' enabled='no' hotpluggable='yes'/>
</vcpus>
~~~
and i dont see any lines like
(taken from the non-working production system which is missing the cpu
topology)
~~~
<numa>
<cell id='0' cpus='0-15' memory='4194304' unit='KiB'/>
</numa>
~~~
which do appear in the wrong XML in our production environment, where i am
missing the cpu topology setting.
Maybe thats giving a hint which wrong path the xml build is going in our
production (defining `<vcpu id=` lines and defining `<numa>` lines instead of
cpu topology setting)?
--
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]
