SymptomsP2V migration fails as shown below:
# vzp2v --ctid 180 firstname.lastname@example.org
* distribute server on 10.30.98.180...
* start server
Error: connect to 10.30.98.180: No route to host
Error: connect to 10.30.98.180: No route to hos
CauseDuring P2V migration, network connections to the two ports on the source server are established:
22 -- command connection
12345 -- data connection
In the above example, a command connection was successfully established, and the vzp2v utility was able to start up the transporter agent successfully. However, it was not able to establish a data connection and, thus, threw the error.
Resolution1. Use the strace utility to determine the last few system calls completed before the error was thrown.
2. Make sure port 12345 is not blocked for incoming connections, either on the source server, or on the network connecting the destination and source servers, as the common (but not complete) solution stops iptables on the source node with the command /etc/init.d/iptables stop.
3. Retry migration.