Rename VMware VM Bundle Files: Difference between revisions
Jump to navigation
Jump to search
(Created page with "=Internal= * #Procedures =Overview= {{Warn|This is an experimental procedure. It worked, but it is probably not supported. If not applied, a VM can be cloned but the un...") |
|||
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
=Internal= | =Internal= | ||
* [[# | * [[VMware Fusion Operations#Rename_VM_Bundle_Files|VMware Fusion Operations]] | ||
=Overview= | =Overview= |
Latest revision as of 20:13, 29 April 2018
Internal
Overview
This is an experimental procedure. It worked, but it is probably not supported. If not applied, a VM can be cloned but the underlying bundle files won't be renamed.
Start by renaming the top level directory so its name coincides with the new name of the VM.
Rename bundle files as follows:
old="old-name"; new="new-name"; for i in ${old}*; do mv ${i} ${i/${old}/${new}}; done
Change the sparse disk extent description. Open <new-name>.vmdk, where <new-name>.vmdk is referred from the vmx file, in vi and:
:1,$s/old-name/new-name/g
Update the snapshot file *. vmsd. Use same command in vi.
Update the .vmx and .vmxf configuration files. Use same command in vi.
Remove old logs:
rm vmware*.log