do a VI client to the vCenter, browse the source Datastore, select the VM/folder that you want to move, right click on the VM/folder and select copy/move as per your convinience. A pop will appear, select the destiniation Daatstore. this should do it.
however following could be an issue:
1. VM's are powered on 4.x host and you are trying to move them to VMFS5 Datastore, as 4.x will not be aware of VMFS5 file system Structure.
try doing a VI Client to vSphere 5 host in case of no availability of VC, but vCenter5 Will be of help in this case.
Or try downloading the Vm's to your local machine using VI client to the ESX hosts, in case Datstores are not shared, once downloaded then again do a VI client this time to vSphere5 host and uplaod the Files.
tried the copy using the VI at the host.
Tried a Migrate using v5 Vcenter. Been at 92% for a long time. Believe it will fail. Stay tuned.
I am seeing the i/o latency errors discussed in this thread. I'm grabbing at the Live-lock or something in that vein as my problem.. I mention this because it seems logical the in my scenario- the files are copied and the final 'let go" process or similar cannot 'let go'.
Well..... Worked with VMWare support. Measured performance across the datastores using esxtop. Turns out while my Netgear NAS, which worked fine with 4.1 wasn't compatible, or vise versa, with 5.0.
I have since configured my Netgear NAS as NFS. I guess there's something to be said to using NFS as the default Datastore with VMWare...
Would have rather went VMFS 5 - but - things are running well on NFS..
Moral of this story---Just cause it works fine with one version doesn't mean you don't have to be on the HCL for the next..
Thanks for the help..