VMware Fusion Operations
Internal
Procedures
Changing the Number of CPUs Allocated to a VM
Virtual Machine -> Settings -> System Settings row -> Processors & Memory -> Processors.
Clone a VM
External
Procedure
Power off the VM.
Find the VM bundle.
Copy the VM bundle in a different location.
If you want to change the bundle file names, follow this procedure "Rename VM Bundle Files", at this time, and not later.
Power on the copy.
Fusion will ask if the VM was moved or copied:
Select "Copied" - a new UUID and MAC address will be generated.
Go to Rename a VM. Renaming is unnecessary if "Rename VM Bundle Files" was performed, the machine is already removed.
If the copied VM relies on getting of an IP from the built-in DHCP server and we want a static address, follow this procedure "Configure DHCP to Serve a Static Address"
Then reconfigure the quest OS, as described here:
Rename a VM
External
Procedure
After startup, Virtual Machine -> Settings -> General -> Click the existing name of the VM to edit the text -> Rename and click outside the text box to save.
Shutdown.
Note that renaming the VM does not change the name of any bundle file on disk.
Shrink a Sparse Disk
External
Procedure
TODO: "Clean Up Virtual Machine"
Rename VM Bundle Files
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