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

ASF GitHub Bot commented on CLOUDSTACK-9025:
--------------------------------------------

mike-tutkowski commented on issue #2315: A comprehensive solution for 
#CLOUDSTACK-9025.
URL: https://github.com/apache/cloudstack/pull/2315#issuecomment-344724604
 
 
   @rafaelweingartner Yes, you are correct: Use the 'managed' property of the 
storage pool in question.
   
   Also, the supportsResign property is really only relevant for XenServer. All 
versions of ESXi supports UUID resigning by default and KVM doesn't require 
such support. (Note: Managed storage is only currently supported for XenServer, 
VMware, and KVM).

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


> Unable to deploy VM instance from template if template spin from linked clone 
> snapshot
> --------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9025
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9025
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: XenServer
>    Affects Versions: 4.5.2
>         Environment: XenServer 6.5
>            Reporter: Anshul Gangwar
>            Assignee: Anshul Gangwar
>            Priority: Critical
>             Fix For: 4.6.0
>
>
> As default, CloudStack create linked clone snapshot for VM instance . When we 
> take a snapshot for the VM, and create a template based on such snapshot, 
> CloudStack only download incremental VHD as template file, as a result, the 
> VM instance fail to deploy as it is incomplete.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to