[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13704512#comment-13704512
 ] 

ASF subversion and git services commented on CLOUDSTACK-3303:
-------------------------------------------------------------

Commit 664dc17b0b2a07eb0bd6f124a561b47bac03a33e in branch refs/heads/master 
from [~sateeshc]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=664dc17 ]

CLOUDSTACK-3303 Vmware - Put a mechanism to disable hot add vcpu if the number 
of cores per socket is not 1 and virtual machine hardware version=7

Following Hotadd memory checks are included now.
1) Check if guest operating system supports memory hotadd
2) Check if virtual machine is using hardware version 7 or later before 
enabling memory hotadd

Following Hotadd CPU checks are included now.
1) Check if guest operating system supports cpu hotadd
2) Check if virtual machine is using hardware version 8 or later.
3) Check if virtual machine has only 1 core per socket. If hardware version is 
7, then only 1 core per socket is supported. Hot adding multi-core vcpus is not 
allowed if hardware version is 7.

Signed-off-by: Sateesh Chodapuneedi <[email protected]>

                
> Vmware - Put a mechanism to disable hot add vcpu if the number of cores per 
> socket is not 1 and virtual machine hardware version=7
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3303
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3303
>             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: Nitin Mehta
>            Assignee: Sateesh Chodapuneedi
>             Fix For: 4.2.0
>
>


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

Reply via email to