VMware Fusion Operations: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 32: Line 32:


Go to [[#Rename_a_VM|Rename a VM]].
Go to [[#Rename_a_VM|Rename a VM]].
Then reconfigure the quest OS, as described here:
{{Internal|Reconfigure Linux VM Guest Image|Reconfigure Linux VM Guest Image}}


=Rename a VM=
=Rename a VM=

Revision as of 20:40, 3 May 2017

Internal

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:

VMware Fusion Operations Moved or Copied.png

Select "Copied" - a new UUID and MAC address will be generated.

Go to Rename a VM.

Then reconfigure the quest OS, as described here:

Reconfigure Linux VM Guest Image

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.

old="forge-1.0"; new="jdg-app1"; for i in ${old}*; do mv ${i} ${i/${old}/${new}}; done

Change the sparse disk extent description. In vi:

:1,$s/forge-1.0/jdg-app1/g

Update the snapshot file *. vmsd. Use same command in vi.

Update the .vmx and .vmxf configuration files. Use same command in vi.

Remove logs.