StepBee commented on issue #6807:
URL: https://github.com/apache/cloudstack/issues/6807#issuecomment-1286900761

   An update after further testing - i think the issue came with the update to 
Cloudstack Version 4.17.0.1
   
   I found out i can create a VM with a custom offering and 2 vCPU
   `virsh dumpxml <vmid>` shows:
   `  <vcpu placement='static' current='2'>16</vcpu>
     <cputune>
       <shares>800</shares>
     </cputune>`
   
   While the VM is running, i can scale the VM with the custom service offering 
to 4 vCPU, reboot the VM from the operating system (not cloudstack!) and the OS 
is seeing the 4 vCPUs and is running fine.
   `virsh dumpxml <vmid>` shows:
   `  <vcpu placement='static' current='4'>16</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='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>
     <cputune>
       <shares>1600</shares>
     </cputune>`
   
   When i stop the VM from cloudstack and try to start the VM via cloudstack 
again, it fails with the mentioned error.
   
   Today i looked at a VM, which was created before the update to 4.17.0.1, 
using exactly the same custom service offering and using 8 vCPUs:
   `virsh dumpxml <other-vmid>` shows
   `  <vcpu placement='static'>8</vcpu>
     <cputune>
       <shares>4000</shares>
     </cputune>`
   
   There seems to be a difference in 4.17.0.1 in the way the XML for qemu is 
generated for VMs based on custom contrained service offerings, mainly listing 
all vcpus in a <vcpus> tag, which seems to conflict with qemu ?


-- 
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]

Reply via email to