VMs are a special condition for an actual running copy of an operating system. Provided that the GUIDs (unique identifiers) of the VMs are unique and remain constant as they move from one hypervisor host to another, they will also move in Hyperview as well. vMotion is not monitored and thus the movement is not captured by monitoring cycles, but a discovery does recognize those updates and will capture the changes in Hyperview. The changes to VM locations are logged in the asset change log and the history of the VM is maintained.

To Summarize:
1. Hyperview discovery does capture VM switching from server to server.
2. Hyperview monitoring does not capture VM switching from server to server.
3. The unique identifiers for the VM must remain constant in order for Hyperview to recognize the changes.