VMware Fusion Operations: Difference between revisions

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


Virtual Machine -> Settings -> System Settings row -> Processors & Memory -> Processors.
Virtual Machine -> Settings -> System Settings row -> Processors & Memory -> Processors.
=Clone a VM=
==External==
* https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001524
==Procedure==
Power off the VM.
Find the [[VMware_Fusion_Concepts#VM_Bundle|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|Rename VM Bundle Files]]", '''at this time, and not later'''.
Power on the copy.
Fusion will ask if the VM was moved or copied:
:[[Image:VMware_Fusion_Operations_Moved_or_Copied.png]]
Select "Copied" - a new UUID and MAC address will be generated.
Go to [[#Rename_a_VM|Rename a VM]]. Renaming is unnecessary if "[[#Rename_VM_Bundle_Files|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 "[[VMware_Fusion_Configuration#Configure_DHCP_to_Serve_a_Static_Address|Configure DHCP to Serve a Static Address]]"
Then reconfigure the quest OS, as described here:
<span id="Reconfigure_Linux_VM_Guest_Image"></span>{{Internal|Reconfigure Linux VM Guest Image|Reconfigure Linux VM Guest Image}}


=Rename a VM=
=Rename a VM=

Revision as of 03:21, 1 June 2017

Internal

Procedures

Changing the Number of CPUs Allocated to a VM

Virtual Machine -> Settings -> System Settings row -> Processors & Memory -> Processors.

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

Snapshot Consolidation

https://kb.vmware.com/kb/1020000