Vmotion logs

[pt073]

Hello,

I'm looking for logs that show when DRS Vmotions VMs from HOSTA to HOSTB. Would there be a central location for a file that has this information?

Thanks

[f10 · Accepted solution]

You would find this information in three logs but primarily only two i.e. the /var/log/vmware/hostd.log and the /vmfs/volumes/datastore/vm/vmware.log

There would be a task ID in the hostd.log which will tell what is the source and destination ESX hosts for the VM, and to confirm the same information would be available in the vmware.log file.

Apart from the logs you can also check the Task and Events tab for the vCenter server and ESX host.

If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".

f-10

VCP3, VCP4, HPCP, HP UX CSA

[pt073]

Thanks, quick question the hostd.log has alot of data how can I find vmotioned specific items in the log?

[f10]

I would use the keyword "migrate" so if when you do open the hostd.log file search or grep for "migrate".

If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".

f-10.

VCP3, VCP4, HPCP, HP UX CSA

[pt073]

Thanks Much, I did a search for migrate nothing yet, I'll keep looking on the other hosts.

Would it write to the log if the migrate was successful?

thanks again!

[f10]

Every task is logged irrespective of the result, I had vMotioned one of the VM's and here is the extract from the hostd.log

The logs below indicate the start of vMotion:

2010-10-24 08:54:00.614 F63DD900 info 'VMotionSrc (1287890634401199)' opID=3C63A19B-0000010E-87 VMotionEntry: migrateType = 1

2010-10-24 08:54:00.780 F63DD900 info 'vm:/vmfs/volumes/4cb43e93-555bbef5-0f61-0024817ebebb/apandey-vc/apandey-vc.vmx' opID=3C63A19B-0000010E-87 State Transition (VM_STATE_ON -> VM_STATE_EMIGRATIN

G)

2010-10-24 08:54:00.785 F63DD900 info 'vm:/vmfs/volumes/4cb43e93-555bbef5-0f61-0024817ebebb/apandey-vc/apandey-vc.vmx' opID=3C63A19B-0000010E-87 VMotionPrepare (1287890634401199): Sending 'to' src

Ip=10.112.98.17 dstIp=10.112.98.18, type=1, encrypted=false, remoteThumbprint=

2010-10-24 08:54:00.786 F63DD900 info 'vm:/vmfs/volumes/4cb43e93-555bbef5-0f61-0024817ebebb/apandey-vc/apandey-vc.vmx' opID=3C63A19B-0000010E-87 VMotionPrepare: srcMgmtIp=10.112.96.17

2010-10-24 08:54:00.786 F63DD900 info 'vm:/vmfs/volumes/4cb43e93-555bbef5-0f61-0024817ebebb/apandey-vc/apandey-vc.vmx' opID=3C63A19B-0000010E-87 VMotionPrepare: dstMgmtIp=10.112.96.18

2010-10-24 08:54:00.787 F63DD900 verbose 'VMotionSrc (1287890634401199)' opID=3C63A19B-0000010E-87 Migration changed state from NONE to BEGIN

Logs from vmware.log:

Oct 24 03:11:00.477: vmx| Received migrate 'from' request for mid id 1287890634401199, src ip <10.112.98.17>.

Oct 24 03:11:00.478: vmx| MigrateSetInfo: state=7 srcIp=<10.112.98.17> dstIp=<10.112.98.18> mid=1287890634401199 uuid=34393433-3239-5347-4839-323534364d54 priority=high

I found the above logs from vSphere 4.1 and it seems that the logging has been changed when compared to ESX 3.5, but here's what it would look like. Once you get to know the start time for vMotion continue to check the logs and the status of vMotion would be reported as

successfully or unsuccessfully.

Hope this helps

If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".

f-10

VCP3, VCP4, HPCP, HP UX CSA

[Troy_Clavell]

nevermind... already mentioned.