You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by GitBox <gi...@apache.org> on 2021/11/23 08:10:16 UTC
[GitHub] [cloudstack] shwstppr opened a new issue #5706: vmware: on dynamic scaling a VM incorrect CPU reservation is set
shwstppr opened a new issue #5706:
URL: https://github.com/apache/cloudstack/issues/5706
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Bug Report
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
vmware
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main branch.
-->
~~~
4.16, may also exist on earlier versions
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network, advanced networking, etc. N/A otherwise
-->
4.16.0 Advanced zone; single VMware cluster with 2x ESXi 6.5 hosts
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
Any
##### SUMMARY
<!-- Explain the problem/feature briefly -->
Incorrect value of CPU reservation is set when a VM is dynamically scaled for a new offering.
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
<!-- Paste example playbooks or commands between quotes below -->
~~~
1. Global setting, vmware.reserve.cpu, is unchanged from default value false.
2. Enable global setting - enable.dynamic.scale.vm, create 2 offerings with dynamic scalable flag and different memory cpu/values, register dynamic scalable template and deploy a dynamic scalable VM
3. Once started, scale running VM to higher offering..
4. Observe in vCenter CPU reservation is set for the VM.
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
No CPU reservation set for the VM
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
CPU reservation set for the VM as seen from vCenter
~~~
Problem may be due to min CPU speed used here as CPU reservation, https://github.com/apache/cloudstack/blob/4.16/plugins/hypervisors/vmware/src/main/java/com/cloud/hypervisor/vmware/resource/VmwareResource.java#L1768
While during VM deployment CPU reservation is properly calculated, https://github.com/apache/cloudstack/blob/4.16/plugins/hypervisors/vmware/src/main/java/com/cloud/hypervisor/vmware/resource/VmwareResource.java#L1999
--
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: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] weizhouapache closed issue #5706: vmware: on dynamic scaling a VM incorrect CPU reservation is set
Posted by GitBox <gi...@apache.org>.
weizhouapache closed issue #5706:
URL: https://github.com/apache/cloudstack/issues/5706
--
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: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org