The vmware converter helper image did not start
I have a KVM virtualization platform and I would like to migrate my KVM virtual machine to VSphere 8. However, I got stuck at 1% during the Vmware vCenter Converter version 6.4 conversion. So I logged into VCenter to check and found that the virtual machine creation task had actually been executed, but the startup page showed that I couldn't find a bootable system, indicating that the helper did not automatically mount. Is this an error in the VSphere 8 product or 6.4 conversion version? The following is a screenshot of the relevant logs.
I also set the SSL encryption of the configuration file to false, and it is useless to restart and run the creation task as an administrator. In the end, all of this failed. KVM's virtual machine is on the support list of Centos7, with no network restrictions and both firewalls turned off. There is really no other way to solve this problem. Please take a look at how this problem was handled, all experts
Same network segment and cross network segment conversion failed to end
The error you have seen is happening in the initial stages of the conversion process and it does not matter whether the source is a KVM vm or any other running Linux machine. The problem is the helper ISO file cannot be attached to the virtual CD-ROM device and as a result the destination VM cannot boot (as you have already identified).
The helper ISO is attached to the destination VM using the remoteDeviceConnect.exe tool. It accepts as a command-line argument a ticket (generated by vCenter) in order to authenticate to the destination ESX server and proceed later with connecting the ISO image to the virtual CD-ROM.
Looking at the log bundle there is the following line in vmware-converter-worker-2.log:
2023-05-23T13:21:30.661+08:00 info vmware-converter-worker[07464] [Originator@6876 sub=Default] SysCommand invoking command C:\Program Files (x86)\VMware\VMware vCenter Converter Standalone\remoteDeviceConnect.exe -t cd-iso -d ide0:0 -W -u wss://localhost.localdomain:443/ticket/3adcd0329bdc737 -V /vmfs/volumes/vsan:5271497197c4aef5-73578a6868426934/4d4d6c64-900d-5a61-be3e-d47c44d2278f/192.168.1.83.vmx -T 26:6F:69:E0:F5:4A:08:98:92:76:9B:5C:C9:44:5D:7F:51:BC:E0:33 C:\Program Files (x86)\VMware\VMware vCenter Converter Standalone\converter-helper-vm-x64.iso
The ticket used is wss://localhost.localdomain:443/ticket/3adcd0329bdc737. You can see the ESX host name is reported as localhost.localdomain and this obviously prevents the connection to the ESX host and thus successfully attaching the helper ISO.
did you check compatibility of converter with vSphere 8 and KVM
That's not the problem. Version 6.4 supports Centos7
The error you have seen is happening in the initial stages of the conversion process and it does not matter whether the source is a KVM vm or any other running Linux machine. The problem is the helper ISO file cannot be attached to the virtual CD-ROM device and as a result the destination VM cannot boot (as you have already identified).
The helper ISO is attached to the destination VM using the remoteDeviceConnect.exe tool. It accepts as a command-line argument a ticket (generated by vCenter) in order to authenticate to the destination ESX server and proceed later with connecting the ISO image to the virtual CD-ROM.
Looking at the log bundle there is the following line in vmware-converter-worker-2.log:
2023-05-23T13:21:30.661+08:00 info vmware-converter-worker[07464] [Originator@6876 sub=Default] SysCommand invoking command C:\Program Files (x86)\VMware\VMware vCenter Converter Standalone\remoteDeviceConnect.exe -t cd-iso -d ide0:0 -W -u wss://localhost.localdomain:443/ticket/3adcd0329bdc737 -V /vmfs/volumes/vsan:5271497197c4aef5-73578a6868426934/4d4d6c64-900d-5a61-be3e-d47c44d2278f/192.168.1.83.vmx -T 26:6F:69:E0:F5:4A:08:98:92:76:9B:5C:C9:44:5D:7F:51:BC:E0:33 C:\Program Files (x86)\VMware\VMware vCenter Converter Standalone\converter-helper-vm-x64.iso
The ticket used is wss://localhost.localdomain:443/ticket/3adcd0329bdc737. You can see the ESX host name is reported as localhost.localdomain and this obviously prevents the connection to the ESX host and thus successfully attaching the helper ISO.
What is the reason why the system cannot start after changing the file submission conversion task?
What is the reason why the system cannot start after changing the file submission conversion task? The source virtual machine is on the KVM virtualization platform, and the purpose is on the Vsphere virtualization platform. Tasks converted using vcenter connector
The source virtual machine is on the KVM virtualization platform, with the aim of using the Vsphere virtualization platform. For tasks converted using the vcenter connector, after submitting the conversion task by changing the file according to the above method, the helper can automatically load it, but the system cannot start after the task is completed. What is the reason for this?
After trying as above, the virtual machine still cannot start after the conversion task is completed