source has detected error

[fborges555]

Hi gurus

I need some help with the following error while trying to Vmotion/migrate a VM " A general system error occurred: The source detected that the destination failed to resume" I have problem with only two machines, I can VMotion/migrate other with no problem at all, has anyone here encountered this problem before so I can get help.

I have done only datastore migration

create a snapshot and delete all snapshot option

move VM from VLAN

running out of option

Thanks a bunch for any help

[vijayrana968]

Please check the Hardware version of these 2 VMs. If required, upgrade and then retry.

[fborges555]

Big V

Thanks for your time, I have checked all VM are they are Version 9, the ones that I can Vmotion as well as the one that I can't, now I guess I got the right information, the version is the one that accompanies the compatibility

[SureshKumarMuth]

looks like there is a connectivity issue between these hosts on vmotion network

can you run this command on both the source and destination ESXi hosts and check if the connectivity is fine

fine the vmk number of the vmotion network on both the hosts

source host:

===========

vmkping -I <vmk# of vmotion vmkernel portgroup> <destination vmotion port group IP>

Destination host:

vmkping -I <vmotion vmk#> <vmotion IP of other host>

Testing VMkernel network connectivity with the vmkping command (1003728) | VMware KB

[fborges555]

Sure

Thanks a bunch for jumping in also as well, but if that would be the case, should not all VM present the same problem as they all use  the same vmotion traffic pipe, I only have two machines that present this problem.

I so new at this as you can tell.

Thanks again

[SureshKumarMuth]

sorry, I read two machines as two ESXi hosts, now understood that two VMs are facing the issue. This may happen due to more IOs happening. What do you see in the hostd log of both the hosts. Can you check the hostd log

/var/log/hostd.log with the time stamp

or post the hostd and vmware.log of the machines here

[fborges555]

Big S.

I would be more than willing but I have no clue how to get to those files, if you can walk me through the step I will post and learn how to get this info. again you can tell how new I am on this matter of VMware.

Thanks again for jumping in

[SureshKumarMuth]

Try vmotion again

Take ssh session to both ESXi hosts

1. got to /var/log  --> find hostd.log file and copy it

2. Go to vm directory and copy the vmware.log file

give me the time stamp along with the log files

logs will give more details on why the vmotion failing

Regards,

Suresh

[fborges555]

Sure.

I found the Hostd.log but did not find the Vmware.log file

can I before running VMotion again clear this file so it could more legible?

Thanks again

[SureshKumarMuth]

No , you should not clear the file. This file will be auto rotated.

Also, you can find the vmware log on virtual machine folder.

/vmfs/volumes/<vmname>/vmware.log or right click the datastore where the VM resides and go to the vmfolder and download the vmware.log file using vsphere client.