You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Anthony Xu (JIRA)" <ji...@apache.org> on 2013/10/30 23:03:25 UTC
[jira] [Resolved] (CLOUDSTACK-4953) VMsnapshot - Revert VM from
running/stopped to a disk+memory snapshot DOES NOT result in running state
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anthony Xu resolved CLOUDSTACK-4953.
------------------------------------
Resolution: Fixed
> VMsnapshot - Revert VM from running/stopped to a disk+memory snapshot DOES NOT result in running state
> -------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4953
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4953
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Affects Versions: 4.2.1
> Environment: MS 10.223.130.59 internal build 758 rhel6.3
> host XS 6.0.2 + patches
> Reporter: angeline shen
> Assignee: Anthony Xu
> Priority: Critical
> Fix For: 4.2.1
>
> Attachments: management-server.log.gz, vm1.png
>
>
> 1. Advance zone. Deploy VM1.
> 2. VM1 add files. Create VM1SS2 Disk+mem
> VM1 at VM1SS2 add files Create VM1SS3 Disk+mem
> VM1 at VM1SS3 add files Create VM1SS4 Disk
> VM1 at VM1SS4 add files Create VM1SS5 Disk
>
> 3. VM1 at VM1SS4. VM1 in stop state. Revert to VM1SS3.
> result: VM1 in stop state
> 4. VM1 at VM1SS4. VM1 in running state. Revert to VM1SS3.
> result: VM1 in running state
> 5. VM1 at VM1SS2. VM1 in stop state. Revert to VM1SS3
> result: VM1 in stop state
> Conclusion: VMsnapshot - Revert VM from running/stopped to a disk+memory snapshot DOES NOT result in running state.
> It result in the VM state before the Revert.
--
This message was sent by Atlassian JIRA
(v6.1#6144)