cli having issues win to esx - V9 build 242 and 268

VM image converter (VMDK, VHD, VHDX, IMG, RAW, QCOW and QCOW2), P2V migrator

Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)

Post Reply
salgadoj
Posts: 4
Joined: Tue Nov 30, 2021 7:32 pm

Tue Nov 30, 2021 7:51 pm

Using the GUI to convert a VM from Hyper-V to ESXi is working fine for both builds. However, I'm having issues with the CLI. The error messages on both builds are different even though I'm using the same parameters.

Parameters entered as follows:

Code: Select all

V2V_ConverterConsole.exe convert
in_host_type="win"
in_host_address="source.name"
in_host_username="domain\username"
in_host_password="password"
in_file_name="path.vhdx"
out_host_type="esx"
out_host_address="destination.name"
out_host_username="domain\username"
out_host_password="password"
out_vm_name="VMName"
out_file_name="[datastore###] Folder/Disk.vmdk"
out_file_type="ft_vmdk_esx_thin"
Build 242 log has the following two errors:
11/29 14:59:04.945 149c Facility ???ERROR: MicrosoftFile::ParseFile: Time out read
11/29 14:59:04.945 149c Facility ???ERROR: RunConsole: Error create input image - 4
On the command line window, it gives the error message Error opening image 4

Build 268 log has the following errors:
11/30 12:03:56.024 1cb8 Facility ???WARNING: WrapperESXI::IsValidResponse: object id - 0
11/30 12:03:56.024 1cb8 Facility ???ERROR: WrapperESXI::getGuestOS: IsValidResponse m_morComputeResource environmentBrowser false
11/30 12:03:56.024 1cb8 Facility ???WARNING: WrapperESXI::getVMList: getGuestOS fail - -1
11/30 12:03:56.024 1cb8 Facility ???WARNING: WrapperESXI::IsValidResponse: object id - 0
11/30 12:03:56.024 1cb8 Facility ???ERROR: WrapperESXI::getGuestOS: IsValidResponse m_morComputeResource environmentBrowser false
11/30 12:03:56.024 1cb8 Facility ???WARNING: WrapperESXI::getVMList: getGuestOS fail - -1
11/30 12:03:56.227 1cb8 Facility ???WARNING: WrapperESXI::IsValidResponse: object id - 0
11/30 12:03:56.227 1cb8 Facility ???ERROR: WrapperESXI::getGuestOS: IsValidResponse m_morComputeResource environmentBrowser false
11/30 12:03:56.227 1cb8 Facility ???WARNING: WrapperESXI::getVMList: getGuestOS fail - -1
11/30 12:03:56.274 1cb8 Facility ???WARNING: WrapperESXI::IsValidResponse: object id - 0
11/30 12:03:56.274 1cb8 Facility ???ERROR: WrapperESXI::getGuestOS: IsValidResponse m_morComputeResource environmentBrowser false
11/30 12:03:56.274 1cb8 Facility ???WARNING: WrapperESXI::getVMList: getGuestOS fail - -1
11/30 12:03:56.337 1cb8 Facility ???WARNING: WrapperESXI::IsValidResponse: object id - 0
11/30 12:03:56.337 1cb8 Facility ???ERROR: WrapperESXI::getGuestOS: IsValidResponse m_morComputeResource environmentBrowser false
11/30 12:03:56.337 1cb8 Facility ???WARNING: WrapperESXI::getVMList: getGuestOS fail - -1
11/30 12:03:56.352 1cb8 Facility ???WARNING: WrapperESXI::IsValidResponse: object id - 0
11/30 12:03:56.352 1cb8 Facility ???ERROR: WrapperESXI::getGuestOS: IsValidResponse m_morComputeResource environmentBrowser false
11/30 12:03:56.352 1cb8 Facility ???WARNING: WrapperESXI::getVMList: getGuestOS fail - -1
11/30 12:03:57.853 1cb8 Facility ???ERROR: RunConsole: VM VMName not found
In addition, the command line throws the message Invalid parameter.


Any assistance with these errors would be appreciated. I couldn't find any information on these.
yaroslav (staff)
Staff
Posts: 2361
Joined: Mon Nov 18, 2019 11:11 am

Wed Dec 01, 2021 4:36 am

Welcome to StarWind Forum.
Based on the errors you are getting, V2V Converter cannot access the target disk.
salgadoj
Posts: 4
Joined: Tue Nov 30, 2021 7:32 pm

Wed Dec 01, 2021 9:55 pm

Should the VM already be created in VMWare prior to using the CLI?

If so, where is that documented? Using the gui, it created the vm, converted the disk, and attached it.

I created a vm to be sure without a disk. This time the result is a bit different.

console message:
Error attach
Response is incorrect.



Log entries:
12/1 15:58:17.064 17a4 Facility ???INFO: WrapperESXI::connect: fullName - , key - 52228394-8a2b-8c50-ed1a-7a2df4b5a714
12/1 15:58:17.079 17a4 Facility ???WARNING: WrapperESXI::IsValidResponse: object id - 0
12/1 15:58:17.079 17a4 Facility ???ERROR: WrapperESXI::getGuestOS: IsValidResponse m_morComputeResource environmentBrowser false
12/1 15:58:17.079 17a4 Facility ???WARNING: WrapperESXI::getVMList: getGuestOS fail - -1
12/1 15:58:17.470 17a4 Facility ???WARNING: WrapperESXI::IsValidResponse: object id - 0
12/1 15:58:17.470 17a4 Facility ???ERROR: WrapperESXI::getGuestOS: IsValidResponse m_morComputeResource environmentBrowser false
12/1 15:58:17.470 17a4 Facility ???WARNING: WrapperESXI::getVMList: getGuestOS fail - -1
12/1 15:58:17.642 17a4 Facility ???WARNING: WrapperESXI::IsValidResponse: object id - 0
12/1 15:58:17.642 17a4 Facility ???ERROR: WrapperESXI::getGuestOS: IsValidResponse m_morComputeResource environmentBrowser false
12/1 15:58:17.642 17a4 Facility ???WARNING: WrapperESXI::getVMList: getGuestOS fail - -1
12/1 15:58:17.689 17a4 Facility ???WARNING: WrapperESXI::IsValidResponse: object id - 0
12/1 15:58:17.689 17a4 Facility ???ERROR: WrapperESXI::getGuestOS: IsValidResponse m_morComputeResource environmentBrowser false
12/1 15:58:17.689 17a4 Facility ???WARNING: WrapperESXI::getVMList: getGuestOS fail - -1
12/1 15:58:17.736 17a4 Facility ???WARNING: WrapperESXI::IsValidResponse: object id - 0
12/1 15:58:17.736 17a4 Facility ???ERROR: WrapperESXI::getGuestOS: IsValidResponse m_morComputeResource environmentBrowser false
12/1 15:58:17.736 17a4 Facility ???WARNING: WrapperESXI::getVMList: getGuestOS fail - -1
12/1 15:58:17.751 17a4 Facility ???WARNING: WrapperESXI::IsValidResponse: object id - 0
12/1 15:58:17.751 17a4 Facility ???ERROR: WrapperESXI::getGuestOS: IsValidResponse m_morComputeResource environmentBrowser false
12/1 15:58:17.751 17a4 Facility ???WARNING: WrapperESXI::getVMList: getGuestOS fail - -1
12/1 15:58:19.032 17a4 Facility ???INFO: VMConverter::ESXIConverter::AddVirtualDisk: Attach random
12/1 15:58:19.032 17a4 Facility ???WARNING: WrapperESXI::IsValidResponse: object id - 0
12/1 15:58:19.032 17a4 Facility ???ERROR: WrapperESXI::getGuestOS: IsValidResponse m_morComputeResource environmentBrowser false
12/1 15:58:19.032 17a4 Facility ???WARNING: WrapperESXI::getVMList: getGuestOS fail - -1
12/1 15:58:19.079 17a4 Facility ???WARNING: WrapperESXI::IsValidResponse: object id - 0
12/1 15:58:19.079 17a4 Facility ???ERROR: WrapperESXI::getGuestOS: IsValidResponse m_morComputeResource environmentBrowser false
12/1 15:58:19.079 17a4 Facility ???WARNING: WrapperESXI::getVMList: getGuestOS fail - -1
12/1 15:58:19.236 17a4 Facility ???WARNING: WrapperESXI::IsValidResponse: object id - 0
12/1 15:58:19.236 17a4 Facility ???ERROR: WrapperESXI::getGuestOS: IsValidResponse m_morComputeResource environmentBrowser false
12/1 15:58:19.236 17a4 Facility ???WARNING: WrapperESXI::getVMList: getGuestOS fail - -1
12/1 15:58:19.282 17a4 Facility ???WARNING: WrapperESXI::IsValidResponse: object id - 0
12/1 15:58:19.282 17a4 Facility ???ERROR: WrapperESXI::getGuestOS: IsValidResponse m_morComputeResource environmentBrowser false
12/1 15:58:19.282 17a4 Facility ???WARNING: WrapperESXI::getVMList: getGuestOS fail - -1
12/1 15:58:19.345 17a4 Facility ???WARNING: WrapperESXI::IsValidResponse: object id - 0
12/1 15:58:19.345 17a4 Facility ???ERROR: WrapperESXI::getGuestOS: IsValidResponse m_morComputeResource environmentBrowser false
12/1 15:58:19.345 17a4 Facility ???WARNING: WrapperESXI::getVMList: getGuestOS fail - -1
12/1 15:58:19.345 17a4 Facility ???WARNING: WrapperESXI::IsValidResponse: object id - 0
12/1 15:58:19.345 17a4 Facility ???ERROR: WrapperESXI::getGuestOS: IsValidResponse m_morComputeResource environmentBrowser false
12/1 15:58:19.345 17a4 Facility ???WARNING: WrapperESXI::getVMList: getGuestOS fail - -1
12/1 15:58:20.611 17a4 Facility ???INFO: VMConverter::ESXIConverter::AddVirtualDisk: Finded SCSI_0 numLoc - 0
12/1 15:58:20.626 17a4 Facility ???INFO: VMConverter::ESXIConverter::AddVirtualDisk: attachDisk is 0
12/1 15:58:20.642 17a4 Facility ???ERROR: RunConsole: Add disk error. Response is incorrect.
yaroslav (staff)
Staff
Posts: 2361
Joined: Mon Nov 18, 2019 11:11 am

Thu Dec 02, 2021 4:52 am

Should the VM already be created in VMWare prior to using the CLI?
No.
See the commands here https://www.starwindsoftware.com/v2v-he ... rface.html.
out_host_address="destination.name"
out_host_username="domain\username"
out_host_password="password"

Try local user credentials here.
salgadoj
Posts: 4
Joined: Tue Nov 30, 2021 7:32 pm

Thu Dec 02, 2021 4:14 pm

One thing I noticed, with the vm already created, it created the drive in the datastore supplied. So it is authenticating successfully. It just fails immediately after creating it. Only when the VM doesn't exist previously does it give the error: VM VMName not found.

Attempting to use a local account gives the same error messages as with the domain account.

Using the GUI, we've also been using domain credentials successfully to convert all VMs.
salgadoj
Posts: 4
Joined: Tue Nov 30, 2021 7:32 pm

Thu Dec 02, 2021 5:11 pm

I have figured out the issues. CLI documentation is not correct and either needs to be updated or CLI fixed.

out_host_address must have ip address. Documentation example shows a hostname. Hostnames will not work for this parameter. Nowhere is it mentioned an IP address must be used.

If using CLI, you must first create the VM in EXSI. CLI will not create the VM. I tested this multiple time. When the VM is created first, CLI will convert a hyper-v vhdx to vmdk and attach it to the VM. If the VM is not created first, the log shows it cannot find the VM.


Entering the parameters as stated here will work provided the VM is already created. No HDD needs to be attached. Just make sure the VM is already present first.

Code: Select all

V2V_ConverterConsole.exe convert
in_host_type="win"
in_host_address="source.name"
in_host_username="domain\username"
in_host_password="password"
in_file_name="path.vhdx"
out_host_type="esx"
out_host_address="IPAddress"
out_host_username="domain\username"
out_host_password="password"
out_vm_name="VMName"
out_file_name="[datastore###] Folder/Disk.vmdk"
out_file_type="ft_vmdk_esx_thin"

There are other problems with the documentation. For the purposes of the issue I was having, only the two things listed above need to be addresses.
yaroslav (staff)
Staff
Posts: 2361
Joined: Mon Nov 18, 2019 11:11 am

Tue Jan 04, 2022 2:44 pm

Thank you for your update. We are working on fixing the docummentation.
Post Reply