VMware vCenter Converter Standalone converts Linux troubleshooting

VMware vCenter Converter Standalone is an important tool for P2V. Migration Windows
will generally be smoother, and Linux migration is relatively strict.

When there is a problem with the migration, you can roughly eliminate the error according to the following process

(1) Confirm that the OS of the source conversion Linux machine is in the official support list; (2) Have root privileges; (3) Check if there is any problem with the DNS settings. Note: Both Linux and Windows should be added at the same time; (4) Verify that the source Linux can ping the same ESX or vCenter IP. If it fails at 2%, the biggest possibility is the permission problem or the firewall blocking problem; (5) Confirm that Linux allows SSH to log in. This can help us log in to the Linux system during the conversion; (6) Confirm that the IP is set to the helper virtual machine, instead of DHCP (if there is no DHCP server in the network), if not configured, it will lead to Linux. The migration card is at 1%; (7) confirm that both the source and target are on the same subnet. If different subnets are routed through the route, errors may occur; (8) Note that the converter does not support Linux systems that do soft arrays. It can be done with a cold clone disc, which sets the soft array to /dev/md0. (9) VMware Converter Standalone's log directory: C:\\Documents and Settings\\All Users\\Application Data\\VMware\\VMware vCenter Converter Standalone for troubleshooting purposes.