One of the reason could be that OEM image of the hyper-v host is too big to be collected in XML file, try removing OEM image from the location and share the results.
Other reason could be that the WS-management (WinRM) service on one of the VM's errored out during the Remove-WSManInstance command in the Wait-VMPSConnection function.
Rerun with the -rerun parameter if you didn't try it already. If that doesn't help then reboot your host, wait a while after all the VM's to came up (Failover Cluster) and restart the installation with the '-rerun' flag and
let us know the outcome.