Likitha Shetty c8a437b782 BUG-ID: CLOUDSTACK-7102. Volume migration fails with 'VM i-2-3-VM does not exist in VMware datacenter' expection. ... Look for a VM in vCenter based on both the vCenter name and CS internal name (required in case 'vm.instancename.flag' is enabled). During Attach Volume and Volume Migration, for lookup and other operations use VM's name as obtained from vCenter instead of using the name set in the agent command. (cherry picked from commit b8fdda0a34) Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>		2015-02-02 13:51:04 +05:30
..
src/com/cloud/hypervisor/vmware	BUG-ID: CLOUDSTACK-7102. Volume migration fails with 'VM i-2-3-VM does not exist in VMware datacenter' expection.	2015-02-02 13:51:04 +05:30
test/com/cloud/hypervisor/vmware/mo	Reformatted all of the code.	2013-11-21 06:15:26 -08:00
pom.xml	Update master to 4.5.0-SNAPSHOT	2014-03-14 14:55:26 +01:00