[ https://issues.apache.org/jira/browse/CLOUDSTACK-8970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15250077#comment-15250077 ]
ASF GitHub Bot commented on CLOUDSTACK-8970: -------------------------------------------- Github user bhaisaab commented on the pull request: https://github.com/apache/cloudstack/pull/956#issuecomment-212474106 @SudharmaJain The provided version have already released so these change need to go into 481to490 related sql /cc @swill any vmware/guest-os-mapping guru want to comment on the changes -- @anshulgangwar @devdeep @agneya2001 @koushik-das @sureshanaparti > Centos 6.{1,2,3,4,5} guest OS mapping for vmware is not available > ----------------------------------------------------------------- > > Key: CLOUDSTACK-8970 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8970 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Reporter: sudharma jain > > "Dynamically Scale" fails everytime because the setting of the guest OS in > VMware is not correctly set. When we set the OS Type of a > VM(account1-centos1) to "CentOS 6.5 (64-bit)". Then the value of the guest OS > in VMware is set to "Other (64-bit) and memory size is displayed by a grayed > out. > If the OS type of VM is "CentOS 6.4 (64-bit)" , "CentOS 6.3 (64-bit)" > ,"CentOS 6.2 (64-bit)" or "CentOS 6.1 (64-bit)", the same issue happen. > However, for "CentOS 6.0 (64-bit)", the value of the guest OS in VMware is > set to "Linux CentOS4/5/6/7(64-bit)" and memory size is not displayed by a > grayed out, we were able to "Dynamically Scale" the VM. -- This message was sent by Atlassian JIRA (v6.3.4#6332)