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

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

Commit 617a71b450195d9dc5713ba2826f9d42a025a5cd in branch refs/heads/master 
from [~likithas]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=617a71b ]

CLOUDSTACK-5780. [VMware] ESXi 5.5 - During live volume migration of ROOT and 
DATA volumes, suitable storage list is always empty
Update hypervisor_capabilities to include capabilities for ESXi host 5.5


> [vmware] Vcenter 5.5  host ESXi 5.5  volume migration - if VM running, ROOT 
> volume and DATA volume shows empty drop down list for volume migration
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5780
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5780
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Management Server
>    Affects Versions: 4.3.0
>         Environment: MS   build   1/2/2014
> vcenter  5.5     host 1 host 2   ESXi 5.5
>            Reporter: angeline shen
>            Assignee: Likitha Shetty
>            Priority: Critical
>             Fix For: 4.3.0
>
>         Attachments: vm2.png, vm3.png
>
>
> 1. advance zone, create VMs
> 2. Add 2 cluster-based primary storage, 2 zone-wide primary storage
> 3. While VM running, ROOT volume > volume migration shows empty drop
> down list  of storage pool for volume migration.
> 4. DATA volume>  volume migration shows empty drop
> down list  of storage pool for volume migration.
> 5. According to 4.2.0 CP admin guide    13.4.5  volume migration should be 
> allowed while VM is running in vmware



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to