StarWind Software

Trying to do a V2V converseion from a VMWare vCenter. Launch the program, select 'Remote VMWare ESXi Server or vCenter'. At the next page, I put in the IP address of my vCenter and put in my credentials and then click 'Next'. Where is says 'Select a virtual machine or image file to convert' there is nothing there. No machines or templates listed. Am I doing something wrong?

I have the same question, anyone can help us, please?
thanks in advancesnow rider 3d

HI,

Sorry for the delay! Try using the IP of the individual ESXi hosts.

I don't believe I have access to individual ESX hosts, just the vcenter. I can see about getting that access and try it again.

Yes, please keep me posted. you will need credentials for the user with the administrative privileges.

Hello,
I'm having this issue as well. If the Starwind V2V Converter does not support vCenter, why does it say "Enter VMware ESXi Server or vCenter connection parameters" ?

V2V does support vCenter.
Could you please share the sceenshots?

Sure I can add a screenshot if I had an easy location to put one , but the problem is clear, the lists are just empty, nothing is displayed. You select you want to convert from ESXi or vcenter, you enter the credentials and on the next page, where you are supposed to select what you want to convert, both the left and right box are completely empty. It's not a permission issue (attempted with the local admin account of vSphere), it's not a firewall or DNS issue either (in the same subnet and both on IP and hostname). I'm already glad to see I'm not the only one with this issue.

Please share the screenshot. I need some sort of log or any other evidence to log a call with R&D.

I have just encountered this same issue with version 9.0.1.755.

Can you please try root credentials for the ESXi host where the VM is running?
Please tell me more about ESXi, vCenter, and Hyper-V versions in use.

Using a root credential for a single ESXi host seems to allow me to select a source VM from that host. Obviously that is not ideal, as we will be doing a migration of more than 2000 VMs spread across 70 hosts.

vCenter version 7.0.3 build 24322018
ESXi version 7.0.3 build 24585291
Hyper-V is on Windows Server 2022

Please stick with this workaround for now. I will try to get hold of the dev team.
Do you use administrator credentials?

Same issue here—vCenter connection succeeds but no VMs show up in the selection screen. Using ESXi root works, but that's not scalable for larger environments. Would love to hear if a fix is on the roadmap.

GUI itself is not quite scalable for large deployments. Please consider using CLI.