After migrating a couple VMs, I'm seeing messages similar to this in the vpxa log repeatedly....[VpxaMoVm::CheckMoVm] did not find a VM with ID 16 in the vmList

[adgross]

After a vmotion, I'm see this message in the vpxa log repeatedly.

Sep 20 10:15:29 testhost13 2013-09-20T14:15:29.520Z testhost13.mydomain.com Vpxa: [681CBB90 verbose 'vpxavpxaAlarm' opID=SWI-3ee3b83a] [VpxaAlarm] VM with vmid = 14 not found

Sep 20 10:15:29 testhost13 2013-09-20T14:15:29.520Z testhost13.mydomain.com Vpxa: [681CBB90 verbose 'vpxavpxaMoVm' opID=SWI-3ee3b83a] [VpxaMoVm::CheckMoVm] did not find a VM with ID 16 in the vmList

Sep 20 10:15:29 testhost13 2013-09-20T14:15:29.520Z testhost13.mydomain.com Vpxa: [681CBB90 verbose 'vpxavpxaAlarm' opID=SWI-3ee3b83a] [VpxaAlarm] VM with vmid = 16 not found

Sep 20 10:15:39 testhost13 2013-09-20T14:15:39.521Z testhost13.mydomain.com Vpxa: [681CBB90 verbose 'vpxavpxaMoVm' opID=SWI-3ee3b83a] [VpxaMoVm::CheckMoVm] did not find a VM with ID 8 in the vmList

Sep 20 10:15:39 testhost13 2013-09-20T14:15:39.521Z testhost13.mydomain.com Vpxa: [681CBB90 verbose 'vpxavpxaAlarm' opID=SWI-3ee3b83a] [VpxaAlarm] VM with vmid = 8 not found

Sep 20 10:15:39 testhost13 2013-09-20T14:15:39.521Z testhost13.mydomain.com Vpxa: [681CBB90 verbose 'vpxavpxaMoVm' opID=SWI-3ee3b83a] [VpxaMoVm::CheckMoVm] did not find a VM with ID 14 in the vmList

Sep 20 10:15:39 testhost13 2013-09-20T14:15:39.521Z testhost13.mydomain.com Vpxa: [681CBB90 verbose 'vpxavpxaAlarm' opID=SWI-3ee3b83a] [VpxaAlarm] VM with vmid = 14 not found

Sep 20 10:15:39 testhost13 2013-09-20T14:15:39.521Z testhost13.mydomain.com Vpxa: [681CBB90 verbose 'vpxavpxaMoVm' opID=SWI-3ee3b83a] [VpxaMoVm::CheckMoVm] did not find a VM with ID 16 in the vmList

Sep 20 10:15:39 testhost13 2013-09-20T14:15:39.521Z testhost13.mydomain.com Vpxa: [681CBB90 verbose 'vpxavpxaAlarm' opID=SWI-3ee3b83a] [VpxaAlarm] VM with vmid = 16 not found

I'm not having any problems associated with this, I just don't understand why.

[abhilashhb]

It usually happens when ESXi loses connectivity to the storage which leaves the VM's dangling. Do you see any other problems in vpxa log?

Anything related to storage? can you upload the whole log file?

[adgross]

We have had no storage issues today. I noticed that this was happening on host 13 after a VM migrated off it.  Then, a VM migrated later in the day off host 10 to host 13, and the issue went away on 13 but started on 10.

I'm thinking that when a VM is migrated, it causes a query of the vmList on the receiving host but not on the sending host.  Thus, vpxa on the host that is sending the VM doesn't know yet that the VM isn't running there until some other VM is moved onto it and it queries the vmList to find out.

[abhilashhb]

Might be. Or maybe the storage connection is going off and then the machines disks are losing connection too. So the log says the VM's are not found. One thing i can say is its definately something related to storage. Keep a track of the log and see if you find any issue regarding the connectivity.

If you think its coz of migration then manually migrate and check if the issue shows up again.

[adgross]

I'm sending all the logs to syslog and there have been no storage issues reported.

I was receiving the messages from host 10.  I migrated a VM from host 11 to host 12, then migrated it from host 12 to host 10.  the messages stopped on host 10 and started on both hosts 11 and 12.

Now I know what's causing it, how do I make it stop?  I'm trying not to filter too many of the syslog messages so that I don't miss something important in the future, but this message is happening ever 10 seconds, so it's too much to ignore.

[EXPRESS]

HI I am seeing the exact same msg's what was your corrective action for this if any??

Thanks