Conversion error from azure to vCenter 7.0.3

[kaiman79]

I am converting a Azure to vCenter, and the VM gets created in vCenter but when creating the image it failed due to "m_VixDiskLib_Open is fail - 4, A file was not found". Error is below. Any help would be appreciated.

10/5 15:14:27.378 38f0 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eConverting
10/5 15:14:27.386 6e34 Facility ???INFO: CPPConverting::Convert: InConvertType: 10, OutConvertType: 6
10/5 15:14:31.131 6e34 Facility ???INFO: VMConverter::ESXIConverter::CreateVM: createVM is true, vm-5424
10/5 15:14:31.131 6e34 Facility ???INFO: CPPConverting::ConverterESX: Create VM vm-5424
10/5 15:14:33.216 6e34 Facility ???INFO: CPPConverting::ConvertImage: pathInput: /subscriptions/XXXXXXXXX/resourceGroups/XXXXX/providers/Microsoft.Compute/disks/azure-OSdisk-00, pathOutput: [vsanDatastore] azure/azure-OSdisk-00.vmdk
10/5 15:14:33.780 6e34 Facility ???INFO: CPPConverting::ConvertImage: CreateInputImage: 0
10/5 15:14:34.001 6e34 Facility ???INFO: ESXVmdk::ParseFile: sFilename - [vsanDatastore] azure/azure-OSdisk-00.vmdk
10/5 15:14:34.001 6e34 Facility ???INFO: ESXVmdk::ParseFile: m_cvmxSpec - moref=vm-5424
10/5 15:14:34.015 6e34 Facility ???INFO: ESXVmdk::ParseFile: sslThumbprint - 76:C0:3A:46:B6:D9:53:CA:A6:9C:51:C9:F1:C1:E7:0F:6B:75:3B:0B
10/5 15:14:34.261 6e34 Facility ???ERROR: ESXVmdk::ParseFile: m_VixDiskLib_Open is fail - 4, A file was not found
10/5 15:14:34.261 6e34 Facility ???ERROR: ESXIDisk::CreateOutputImage: ParseFile is fail
0/5 15:14:34.261 6e34 Facility ???INFO: CPPConverting::ConvertImage: CreateOutputImage: 1
10/5 15:14:34.261 6e34 Facility ???INFO: CPPConverting::ConvertImage: pathInput: /subscriptions/XXXXXXXXX/resourceGroups/XXXXX/providers/Microsoft.Compute/disks/azure-datadisk-02, pathOutput: [vsanDatastore] azure/azure-datadisk-02.vmdk
10/5 15:14:34.649 6e34 Facility ???INFO: CPPConverting::ConvertImage: CreateInputImage: 0
10/5 15:14:34.649 6e34 Facility ???INFO: ESXVmdk::ParseFile: sFilename - [vsanDatastore] azure/azure-datadisk-02.vmdk
10/5 15:14:34.649 6e34 Facility ???INFO: ESXVmdk::ParseFile: m_cvmxSpec - moref=vm-5424
10/5 15:14:34.665 6e34 Facility ???INFO: ESXVmdk::ParseFile: sslThumbprint - 76:C0:3A:46:B6:D9:53:CA:A6:9C:51:C9:F1:C1:E7:0F:6B:75:3B:0B
10/5 15:14:34.818 6e34 Facility ???ERROR: ESXVmdk::ParseFile: m_VixDiskLib_Open is fail - 4, A file was not found
10/5 15:14:34.818 6e34 Facility ???ERROR: ESXIDisk::CreateOutputImage: ParseFile is fail

Thank you!

[yaroslav (staff)]

Hi,

Does converting an individual disk work?

[kaiman79]

All individual disk conversions have failed.
The problem may be that the vCetner to which I am converting is not on the Internet.
When converting from Azure to vCenter, do you know what IP Azure will use to access it?

[yaroslav (staff)]

Is it possible to convert that disk as a local file on the ESXi VMFS?

[kaiman79]

It is not possible to convert them as local files on ESXi VMFS.
The above error occurs during conversion.
It is possible to convert as a VMDK to a local file, but I don't know how to restore it in that case.

[yaroslav (staff)]

Could you kindly elaborate on what you mean by

but I don't know how to restore it in that case.

Will be waiting for your reply.

[kaiman79]

What I meant when I wrote that I don't know how to restore is that I can convert the VMDK file format from Azure to the local machine, but I don't know how to restore the VMDK file afterwards on VSphere.
I look forward to working with you.

[yaroslav (staff)]

According to the log, I see there is a problem connecting to Azure. Could you please download the file to Windows host and convert it as a local file and copy it later to the ESXi?

[kaiman79]

Could you please download the file to Windows host and convert it as a local file and copy it later to the ESXi?

I copied the VMDK file converted to the local machine in the above manner onto ESXi, but could not start the VM, perhaps because there are multiple VMDK files.
Please tell me how to start a VM on ESXi from a VMDK file.

[yaroslav (staff)]

Try a different boot option (e.g., EFI or BIOS).
It might be a driver conflict.