[
https://issues.apache.org/jira/browse/CLOUDSTACK-3279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Animesh Chaturvedi updated CLOUDSTACK-3279:
-------------------------------------------
These blockers and critical issues are resolved but not verified. Reporters of
these issues please verify the fixes and help close these issues
> Need mechanism to detect if hotadd for cpu/memory is supported per a specific
> guest OS supported by VMware.
> -----------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3279
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3279
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
> Affects Versions: 4.2.0
> Reporter: Sateesh Chodapuneedi
> Assignee: Sateesh Chodapuneedi
> Priority: Critical
> Fix For: 4.2.0
>
>
> Vmware publishes a list for vmware guest os and their supported capabilities
> for each vmware release. Example for guest OS Ubuntu 10.04 and ESX some
> release 4.x we only support hot add of vcpu (and not hot add memory)
> GuestOS Release
> Ubuntu 10.04 Desktop
> Supported Releases
> ESX 4.1 U31, 2, 3, 4, 5, 6, 4.1 U21, 2, 3, 4, 5, 6, 4.1 U11, 2, 3, 4, 5, 6,
> 4.12, 1, 6, 5, 4, 3
> Support Details
> Hot Add vCPU etc....
> More info @
> http://partnerweb.vmware.com/comp_guide2/pdf/VMware_GOS_Compatibility_Guide.pdf
> Vmware says that the attributes hot add cpu and memory should be turned on
> during deployment of vm (i.e. As part of deployvm api) so that in future the
> user can dynamically scale cpu and memory(scale vm api). Now I wanted to
> understand how to enforce this check in Cloudstack. The best would be Vmware
> providing a method to check whether hot add cpu and memory is enabled for the
> current GuestOS version in the vmware release. Need such mechanism.
> This is related to dynamic scaling of cpu/memory in case of VMware
> environments.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
