VMware Fusion Operations: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
 
(31 intermediate revisions by the same user not shown)
Line 3: Line 3:
* [[VMware Fusion#Subjects|VMware Fusion]]
* [[VMware Fusion#Subjects|VMware Fusion]]


=Changing the Number of CPUs Allocated to a VM=
=New VMware Virtual Machine Provisioning=


Virtual Machine -> Settings -> System Settings row -> Processors & Memory -> Processors.
{{Internal|VMware Fusion Virtual Machine Provisioning#Procedure|VMware Fusion Virtual Machine Provisioning}}


=Clone a VM=
=VMware Virtual Machine Cloning=


==External==
{{Internal|Clone a VMware Fusion Virtual Machine#Procedure|Clone a VMware Fusion Virtual Machine}}


* https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001524
=Rename VM Bundle Files=


==Procedure==
{{Internal|Rename VMware VM Bundle Files|Rename VM Bundle Files}}


Power off the VM.
=Changing the Number of CPUs Allocated to a VM=


Find the [[VMware_Fusion_Concepts#VM_Bundle|VM bundle]].
Virtual Machine -> Settings -> System Settings row -> Processors & Memory -> Processors.
 
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=
Line 52: Line 32:


Note that renaming the VM does not change the name of any bundle file on disk.
Note that renaming the VM does not change the name of any bundle file on disk.
=Add Block Storage to Guest=
Shut down the guest.
Then Virtual Machine Library -> Guest in question -> Settings -> Hard Disk -> Add Device -> New Hard Disk -> Add -> Adjust disk size.
Optionally - Pre-allocate disk space and don't split into multiple files, we we want performance.
The new disk will be available as a block device under OS. On Linux, use [[lsblk]] to list it.
<syntaxhighlight lang='bash'>
[root@vmware-docker ~]# lsblk
NAME  MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda      8:0    0  10G  0 disk
├─sda1  8:1    0  156M  0 part /boot/efi
├─sda2  8:2    0  512M  0 part /boot
└─sda3  8:3    0  9.4G  0 part /
sdb      8:16  0  50G  0 disk
sr0    11:0    1 55.2M  0 rom
</syntaxhighlight>


=Shrink a Sparse Disk=
=Shrink a Sparse Disk=
Line 63: Line 64:
<font color=red>TODO: "Clean Up Virtual Machine"</font>
<font color=red>TODO: "Clean Up Virtual Machine"</font>


=Rename VM Bundle Files=
=Snapshot Consolidation=
 
{{Warn|This is an experimental procedure. It worked, but it is probably not supported. If not applied, a VM can be cloned but the underlying [[VMware_Fusion_Concepts#VM_Bundle|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:


<pre>
{{External|https://kb.vmware.com/kb/1020000}}
old="old-name"; new="new-name"; for i in ${old}*; do mv ${i} ${i/${old}/${new}}; done
</pre>


Change the sparse disk extent description. Open <new-name>.vmdk, where <new-name>.vmdk is referred from the vmx file, in vi and:
=Command-Line Virtual Machine Operations=


<pre>
{{Internal|VMware Fusion Command Line Virtual Machine Operations|Command-Line Virtual Machine Operations}}
:1,$s/old-name/new-name/g
</pre>


Update the snapshot file *. vmsd. Use same command in vi.
=Set Up Direct Access to Virtualization Host Storage=


Update the .vmx and .vmxf configuration files. Use same command in vi.
A pre-requisite for accessing shared host storage in the VM is to install VMWare Tools in the VM. This is the procedure to install VMWare Tools for Linux and [[Windows_Installation#Install_VMware_Tools_in_a_Windows_Virtual_Machine|this is the procedure to install VMware Tools for Windows]].


Remove old logs:
Settings for the VMware VM -> Sharing -> Enable Shared Folders -> + -> Select the local folder to share.


<pre>
The folder will be available after reboot as "Shared Folders (\\wmware-host)".
rm vmware*.log
</pre>

Latest revision as of 02:41, 5 August 2018

Internal

New VMware Virtual Machine Provisioning

VMware Fusion Virtual Machine Provisioning

VMware Virtual Machine Cloning

Clone a VMware Fusion Virtual Machine

Rename VM Bundle Files

Rename VM Bundle Files

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.

Add Block Storage to Guest

Shut down the guest.

Then Virtual Machine Library -> Guest in question -> Settings -> Hard Disk -> Add Device -> New Hard Disk -> Add -> Adjust disk size.

Optionally - Pre-allocate disk space and don't split into multiple files, we we want performance.

The new disk will be available as a block device under OS. On Linux, use lsblk to list it. 

[root@vmware-docker ~]# lsblk
NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda      8:0    0   10G  0 disk
├─sda1   8:1    0  156M  0 part /boot/efi
├─sda2   8:2    0  512M  0 part /boot
└─sda3   8:3    0  9.4G  0 part /
sdb      8:16   0   50G  0 disk
sr0     11:0    1 55.2M  0 rom

Shrink a Sparse Disk

External

Procedure

TODO: "Clean Up Virtual Machine"

Snapshot Consolidation

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

Command-Line Virtual Machine Operations

Command-Line Virtual Machine Operations

Set Up Direct Access to Virtualization Host Storage

A pre-requisite for accessing shared host storage in the VM is to install VMWare Tools in the VM. This is the procedure to install VMWare Tools for Linux and this is the procedure to install VMware Tools for Windows.

Settings for the VMware VM -> Sharing -> Enable Shared Folders -> + -> Select the local folder to share.

The folder will be available after reboot as "Shared Folders (\\wmware-host)".

Retrieved from "https://kb.novaordis.com/index.php?title=VMware_Fusion_Operations&oldid=47335"