Closed thorstenkampe closed 6 years ago
rejected as no issue. the vmxname is derived from the state of runnig vm´s from vmrun list if you want to have detailed Information, you can Always use pipe ( eg get-vmx | get-vmxinfo ]
there is no way to search avm by it´s displayname, other to open ALL vmx files.
If VMXName
is derived from vmrun list
then you can derive the display name from vmrun readVariable runtimeConfig displayName
...
this is a runtime config variable. run time means, machine must run. not very helpful for powered of vm´s. if you issue is the cloning, chsnge the file(Name) during cloning. the only uniqueness, as you stated correctly, is the uuid. as there is no Registration of vm´s in Workstation. use cloning correctly, and then you do not have that issue
clone Path to vmx file Create a copy of the VM
Path to destination vmx file
full|linked
[-snapshot=Snapshot Name]
[-cloneName=Name] ```
vmxtoolkit
uses in multiple placesVMXName
- which is the name of the config file without the ending - although that name is neither unique nor meaningful. Consider the following configuration where a virtual machine was cloned twice:Suggestion:
vmxtoolkit
should use the VMs DisplayName instead of the file name of the configuration file for input and output. The display name is still not unique but at least meaningful to the user. If there is a need to specify one particular VM the user can use the-config
or-UUID
parameters.