Oleg(staff) wrote:Hi Steve,
Sorry, but logs will be included to the new build.

It has been a month since my initial request. Any update on this?

When going through the conversion process and come to the "check settings of the new virtual machine" it gives the option to select the name and datastore. It is pulling the name of the drive from the computer that it is installed on and not of the remote HV system. It actually says the sa...

At the current moment, the version is 9.0.0.75. You can check the version you are running in the properties of V2V_Converter.exe: C:\Program Files\StarWind Software\StarWind V2V Image Converter The new version should be released in the nearest time. We will keep the community updated. Hopefully soo...

The current implementation of repair mode had a set of limitations and we disabled it until the limitations will be removed. Sorry for frustration with the disabled option, we will return it back in upcoming updates! Would it be possible to post when these updates come out and what has changed? I n...

Oleg(staff) wrote:Steve,
There were a lot of functionality and improvements added to this V2V version. The issues you have should be repaired in the next V2V converter build.

When will this version come out? How do we know which version we are running?

I have passed the request about logs for the V2V converter to our R&D team as well. It seems like we have a lot of pending issues. I understand this is a "free" product but it is an important piece for the evaluation of your VSAN software. When do you expect to hear back so we can res...

When going through the converter the option to run repair mode is always greyed out and sometimes does not appear. When following the below steps, the option does appear but is greyed out. Remote VMware ESXi Server>Server parameters>Expand Windows VM>select VMDK (tried one with OS and without)>Micro...

Oleg(staff) wrote:I have passed this information to our R&D team in order to find the reason of this issue.

Do you know if logs are stored anywhere that I could look at? I am sure there is something that is logged that says which parameter is invalid. If I knew the location it could be an easy fix.

I tried with another VM and I see the same message. I am trying find what is common between them. Any ideas? Logs?

The "StarWind @ SpiceWorks" link under "forum" doesn't work. It points to https://community.spiceworks.com/pages/starwindsoftware, when it should be https://community.spiceworks.com/pages/starwind.

Oleg(staff) wrote:Could you please send a screenshot of this error?

It looks like it creates the folders, starts creating the files in HV but when it gets to the large VMDKs it fails.

Oleg(staff) wrote:There are no size limitations for StarWind V2V converter.

Great, but what about the rest of my question. What would cause this error? Where are the logs?

When starting the V2V converter from a remote ESXi 6.0 host to a HV host I get the above error for each of the datastores. It opens the image file, creates a VM in HV and it looks like it completes one VMDK conversion and then fails. Is there a size limit on the VMDK that the V2V Converter can handl...

Can anyone assist with this?

When going through the wizard and you get to the "new virtual machine" portion. It gives you the option to change the name, set the datastore location and select the network. The host is setup with StarWind vSAN and with that there is the C:\ClusterStorage\Volume1 location that I was told ...