Albert Widjaja
asked on
Vmotion error on multiple VMs
Hi Folks,
is there any reason as to why when I migrate multiple VMs into newly upgraded ESXi host failed altogether with this error message ?
very frustrating... when it happens to ESXi 5.1 Update 1
is there any reason as to why when I migrate multiple VMs into newly upgraded ESXi host failed altogether with this error message ?
Failed to write checkpoint data (offset 594009, size 16384): Timeout.
vMotion migration [179830799:1379587402125979] failed: Unable to send remote call to write checkpoint data (16384 bytes @594009) to remote host <10.18.1.18>: Timeout
vMotion migration [179830799:1379587402125979] failed to send message type 4 to the remote host <10.18.1.18>
vMotion migration [179830799:1379587402125979] failed waiting for socket space: Timeout
vMotion migration [179830799:1379587402125979] timed out waiting 20001 ms to transmit 16456 bytes.
Failed to start the virtual machine.
Module Migrate power on failed.
vMotion migration [179830799:1379587402125979] failed to read stream keepalive: Connection reset by peer
The migration transfer failed during the receive operation to socket 71468922720736: received 0/16 bytes: Connection reset by peer
very frustrating... when it happens to ESXi 5.1 Update 1
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I mean check your vMotion network, is connected correctly.
ASKER
yes it is always loaded correctly as no changes in the network settings.
is it because that I selected all VMs in one ESX host (about 15 VMs) to be migrated at once ?
is it because that I selected all VMs in one ESX host (about 15 VMs) to be migrated at once ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes it can, somehow I waited couple of hours trying to find some solution in the Internet, the issue resolved by itself !?!? :-/
network bandwidth/communication issue
ASKER
not a single one successfully migrated.