P2V encounters problem and quits

[CatDaddy63]

I just downloaded this software today in order to do some P2V testing.

I want to convert a Windows 10 PC to VM on a VMware 7.x cluster.

I get as far as selecting the required disks from the PC and getting to the dialog for logging into the cluster. I give it the IP address of the vCentre VM, user name, and password. When I click Next, it appears to start attempting a connection then stops, stating -

StarWind V2V Converter has stopped working - A problem caused the program to stop working.

The only option is to close out.

Am I missing something here?

Thanks

[yaroslav (staff)]

Hi,

It's a known issue. Please use older version. https://drive.google.com/file/d/1hDP4gl ... Ea_5p/view

[CatDaddy63]

Thanks for that.

It got slightly further with the older version but then failed with no useful info as to why. Are there any logs I can look at that might show me a clue?

It started the conversion then reported "Creating virtual machine.....Error create (sic) virtual machine...Conversion failed"

[CatDaddy63]

Tle log file that I found doesn't provide much further info -

The log file name: 'logs\V2V_Log-20250813-093443.log' (PID 1812)
8/13 9:34:43.720 4cb0 Facility ???INFO: CV2V_ConverterApp::InitInstance: SetDllDirectory: C:\Program Files\StarWind Software\StarWind V2V Converter\lib
8/13 9:34:43.720 4cb0 Facility ???INFO: CV2V_ConverterApp::InitInstance: File Version: 9.0.1.268
8/13 9:34:43.725 4cb0 Facility ???INFO: CV2V_ConverterApp::InitInstance: Load language IDR_XML_ENGLISH
8/13 9:34:43.725 4cb0 Facility ???INFO: CV2V_ConverterApp::InitInstance: Set current language English
8/13 9:34:43.729 4cb0 Facility ???INFO: CPS_V2V_Converter::CPS_V2V_Converter: Version MajorVersion 10, MinorVersion 0, BuildNumber 19045
8/13 9:34:43.736 4cb0 Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\WINDOWS\system32\wbem\wmiutils.dll - 284f0000
8/13 9:34:43.737 4cb0 Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\WINDOWS\system32\wbem\wmiutils.dll - 284f0000
8/13 9:34:50.049 4cb0 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eTypeP2V
8/13 9:34:55.291 4cb0 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eVolumeSelectVM
8/13 9:35:01.002 4cb0 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eLocationTo
8/13 9:35:03.698 4cb0 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eESXConnectionTo
8/13 9:35:49.723 4cb0 Facility ???INFO: WrapperESXI::connect: m_url - https://REMOVED/sdk
8/13 9:35:49.767 4cb0 Facility ???INFO: WrapperESXI::connect: fullName - REMOVED, key - 522456b2-ffcd-b2b8-580c-63604858d15c
8/13 9:35:49.767 4cb0 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eVMSettingsESX
8/13 9:35:49.830 4cb0 Facility ???INFO: VMConverter::ESXIConverter::GetHostListInfo: ESX version: 7.0.3
8/13 9:35:49.830 4cb0 Facility ???INFO: VMConverter::ESXIConverter::GetHostListInfo: ESX version: 7.0.3
8/13 9:35:49.830 4cb0 Facility ???INFO: VMConverter::ESXIConverter::GetHostListInfo: ESX version: 7.0.3
8/13 9:37:35.267 4cb0 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eConverting
8/13 9:37:35.286 4c98 Facility ???INFO: CPPConverting::Convert: InConvertType: 3, OutConvertType: 6
8/13 9:37:36.986 4c98 Facility ???INFO: VMConverter::ESXIConverter::CreateVM: createVM is false,
8/13 9:37:36.986 4c98 Facility ???ERROR: CPPConverting::ConverterESX: Create VM error
8/13 9:37:36.986 4c98 Facility ???ERROR: CPPConverting::Convert: FAILED

[CatDaddy63]

The text I just posted was the complete contents of the lone log file in that directory.

[CatDaddy63]

OK, some progress....

In the failed attempt, when selecting the destination, I chose a folder (call it TestVM) that was already on the datastore, and when prompted to supply the name, I chose TestVM. The converter didn't seem to like that and created a new folder called TestVM_1 before it then fell over.

On my next attempt, I just chose the root of the target datastore instead of an existing folder. It seems happier with that and is converting as we speak. However, I have 3 datastores on the cluster to choose from - Vol1-3. I chose to put it on Vol2, but it appears to have ignored that and is dumping it on Vol1.....

[yaroslav (staff)]

Hi,

Glad to know that the conversion has run. Name conflicts and non-ASCII symbols can be a pain.
I am thinking of some sort of misclick, as the converter does allow selecting the datastore from my experience.

[CatDaddy63]

I finally got the VM on the cluster, but on the face of it, something strange happened during the conversion process.

The first thing is that when the VM is powered up, there is no mouse available. This makes navigation pretty impossible.

I thought the solution would be to install VMware Tools into the VM. However, no matter what ISO I load as the VM's CD drive, I get an error stating that "the 32-bit installer can't be run on a 64-bit operating system." I think this is a false error as that ISO has been used elsewhere on native VMs without complaint.

I have no idea how to resolve the problem.

[yaroslav (staff)]

Thanks for your update. I am glad it is working now.
This one does not seem to be related to StarWind's software.
As you have already pointed out, you need to install VMware tools. Try using the default option "install VMware tools".

[CatDaddy63]

It 'worked' in the sense that I got a VM put on a cluster, but somehow the conversion process made it unusable.

It may work 100% OK for other people, but unfortunately, it hasn't for me.

[yaroslav (staff)]

This issue relates to the drivers, not V2V converter.
V2V converter did its bit: it virtualized the source. Now, the source needs the corresponding software to run well at destination; none of those was on the original machine.