Home > Tintri VMstore™ > Knowledge Base > LOG-VMM-0002 alert generated after a Hyper-V VM migration from one Hyper-V host to another Hyper-V host

LOG-VMM-0002 alert generated after a Hyper-V VM migration from one Hyper-V host to another Hyper-V host

Applies To

 

Product(s)

Version(s)

VMstore

All

Hyper-V All

Description

 

After a Hyper-V VM migration from one Hyper-V host to another Hyper-V host, the following alert "LOG-VMM-0002 Alert Detected instance UUID collision..." can be generated by the VMstore.

 

Symptoms

 

The LOG-VMM-0002 alert is generated after a Hyper-V VM migration from one Hyper-V host to another Hyper-V host.

 

Example of the alert:

 

LOG-VMM-0002 Alert Detected instance UUID collision. VM '<<Name>>' in hypervisor manager '<<Name>>' has the same instanceUuid ('<<ID>>') as VM '<<Name>>' in hypervisor manager '<<Name>>'. This VM will be missing from the VM list. Per-VM features reporting, snapshot, cloning and replication may not work on affected VMs.

Resolution

 

The user alert LOG-VMM-0002 is generated after migrating a Hyper-V VM from one Hyper-V host to another Hyper-V host.

After the alert has been generated, verify the VM has been migrated between hypervisors and if so the Alert can be ignored.

 

 

 

Viewing 3 of 3 comments: view all
Technical review and some minor corrections 2017-01-27
Posted 08:15, 27 Jan 2017
changed the wording in the resolution

"The user alert LOG-VMM-0002 is generated after migrating a Hyper-V VM from one Hyper-V host to another Hyper-V host.

After the alert has been generated, verify the VM has been migrated between hypervisors and if so the Alert can be ignored."

Moved "This is a known issue with Hyper-V. The VMstore talks with each hypervisor individually and not synchronously, so when the VMstore refreshes the VM information from the hypervisors, a race condition can be developed whereby the LOG-VMM-0002 alert is generated." to Internal Tintri only
Posted 08:23, 1 Feb 2017
Bug 54725 was opened with a request to prevent LOG-VMM-0002 getting generated when migrating a Hyper-V VM from one Hyper-V host to another Hyper-V host
Posted 03:30, 16 Mar 2017
Viewing 3 of 3 comments: view all
You must to post a comment.
Last modified
10:54, 22 Apr 2017

Tags

Classifications

This page has no classifications.