I am running 18.104.22.168 version of the SVMotion plugin. I am seeing a strange negative value for my source datastore within the plugin. I have not attempted a svmotion. For example: I have a Windows VM running on a fiber SAN (EMC CX3-20) LUN. The size of the LUN is 39GB. This Windows VM has two vdisks, 1 - 10 GB, 2 - 25 GB.
In the "Migrate Storage..." window, The Datastore Properties has the following values: Capacit - GB: 39, Free Space - GB: -13, Used-GB: 52, Number of Disks: 2.
Under "Virtual Machine Properties" Total size - GB: 25, Number of Disks: 2.
Under "Virutal Disk Properties" Total Size-GB: 10
I am running VMware Infrastructure Cient version 2.5.0 build 84767. I am running the newest VMWare Tools for this OS.
The Virtual Machine seems to be running fine. I have vmotioned this vm many times without issue.
Thanks for your comments.
I am also running 22.214.171.124 version of the SVMotion plugin and seeing the same problem with a negative value for the capacity value
I have a Windows VM running on a fiber SAN (EVA 4100) LUN. The size of the LUN is 60GB and I have 10 GB free space
When I click on the datastore in the svmotion plugin window I see the folowing:
Capacity - GB: 60
Free space - GB: -35
Used - GB: 95
Number of disks: 5
I am running VMware Infrastructure Cient version 2.5.0 build 46192. I am running the newest VMWare Tools for this OS.
Hope this helps
First off let me say what an awesome tool!
I have the same problem here running svmotion version 1.0 on a ESX 3.5 cluster
all but one ESX servers in the cluster are running 3.5 UA2, one still running UA1.
If I try and svmotion at the Cluster level it incorrectly reports free space on several VMFS (e.g. reporting -345GB free when in reality there is 600GB+free)
To get around this bug I have been clicking on the ESX server that hosts the VM I want to svmotion, and running it from there and it shows the free space correctly and works fine.
Anyone found a fix for this? I wonder if it will go away when I upgrade that last ESX server to UA2?