[jira] [Commented] (CLOUDSTACK-4802) [VMware] Unable to start VM if VM has VM snapshot been taken in vSphere version 5.0 Update 2

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

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

Commit 2976d9c7932ed160cf3205c06f4d82efdfa0f10a in branch refs/heads/4.2 from [~kelveny]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2976d9c ]

CLOUDSTACK-4802: Change VM start flow to better support VM snapshot on certian version of vSphere, (vSphere 5.0 Update 2). If we detect that VM has pending VM snapshot, we will fully honor VM disk info from vCenter, since in some version of vSphere (vSphere 5.0 U2) does not allow disk-editting when VM has pending snapshot.


> [VMware] Unable to start VM if VM has VM snapshot been taken in vSphere version 5.0 Update 2
> --------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4802
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4802
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Kelven Yang
>            Assignee: Kelven Yang
>            Priority: Critical
>
> CloudStack VM-start flow is broken by the behave of vSphere 5.0 Update 2. VM can not be started after VM has VM snapshot been taken. This issue is currently known to only happen in vSphere 5.0 Update 2



--
This message was sent by Atlassian JIRA
(v6.1#6144)