Why is a running machine not being migrated?

Question

VMware

ESXi 5.1. Two completely identical old HP ML350G5 servers. Both have two setevukha, vSwitch-and are called the same - Provider and Internal. When performing a powered-on machine migration (simultaneous change of host and datastore), one of the host machines migrates normally, but all the others do not! The following message appears:

A general system error occurred: Storage vMotion failed to copy one or more of the virtual machine's disks. Consult the virtual machine's log for more details, looking for lines starting with "SVMotion".
Failed to load one or more destination disks. Canceling Storage vMotion.
Failed to start the virtual machine.
Module Migrate power on failed.

vMotion migration [ 173474057 :1466140341164140] failed to read stream keepalive: Connection closed by remote host, possibly due to timeout There is no common store, the disks of the machines lie on the local disks of each host. On both hosts, vmKernel is connected to vSwitch Internal, IP addresses are configured.

Answer 1

The message already describes what you should do - Refer to the virtual machine log for more details, look for lines starting with "SVMotion". If there is nothing worthwhile in the logs, then check the entire infrastructure - server disks, a switch connecting these two servers, whether VMWare Tolls are in virtuals - maybe they should be updated. In general, it is better to upgrade ESXi to at least version 5.5

Answer 2

At the same time, switched off machines between the same hosts migrate normally. There is no common store, the disks of the machines lie on the local disks of each host. On both hosts, vmKernel is connected to vSwitch Internal, IP addresses are configured.

how do you do it? I only have this (there is a common storage):
in essence: check the vmotion interface