This repository has been archived by the owner on Nov 9, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 95
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Try to use VC UUID first for locating VMs, then fall back to BIOS UUID
When communication from VMCI vSocket is established n vmdk_ops.py, we find out VM ID from the socket, and then locate VM ManagedObject by this ID. There are 2 IDs - VC UUID and BIOS UUID. When .vmx file is copied (e.g. VCD or other products), BIOS UUID can be duplicate thus failures like #1373 . However, VC UUID is unique on creation of VM, and unique as long as ESXi is a part of a VC. So it is a much better candidate for using as a unique ID. This change tries to use VC UUID first, and fails back to BIOS UUID next. The change also checks that the VM name (for a found VM by ID) matches the one we see from vSocket, and does a few other minor prints.
- Loading branch information
Mark Sterin
committed
Jun 30, 2017
1 parent
ec3e93e
commit 2d12fbc
Showing
1 changed file
with
14 additions
and
20 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters