You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sateesh Chodapuneedi (JIRA)" <ji...@apache.org> on 2013/09/13 17:34:51 UTC

[jira] [Updated] (CLOUDSTACK-4664) [ZWPS] High delay to start a stopped VM which has ROOT/DATA volumes migrated to Second Zone wide primary Storage(More than 10 mins)

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sateesh Chodapuneedi updated CLOUDSTACK-4664:
---------------------------------------------

    Summary: [ZWPS] High delay to start a stopped VM which has ROOT/DATA volumes migrated to Second Zone wide primary Storage(More than 10 mins)  (was: [VMWARE][ZWPS] High delay to start a stopped VM which has ROOT/DATA volumes migrated to Second Zone wide primary Storage(More than 10 mins))
    
> [ZWPS] High delay to start a stopped VM which has ROOT/DATA volumes migrated to Second Zone wide primary Storage(More than 10 mins)
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4664
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4664
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Storage Controller, VMware
>    Affects Versions: 4.2.1
>            Reporter: Sailaja Mada
>            Priority: Critical
>         Attachments: alllogs.rar, VMStartTimeinVMWARE.png
>
>
> Steps:
> 1. Configure VMWARE with 2 zone wide primary storages
> 2. Deploy 2 VM's
> 3. Stop one of the VM
> 4. Start the VM
> Observation:
> [VMWARE][ZWPS] High delay to start a stopped VM which has ROOT/DATA volumes migrated to Second Zone wide primary Storage(More than 10 mins)
> (Attached all the logs and Snap from vCenter) 

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