vSphere Virtual Machine Administration - VMware Documentation
vSphere Virtual Machine Administration - VMware Documentation
vSphere Virtual Machine Administration - VMware Documentation
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>vSphere</strong> <strong>Virtual</strong> <strong>Machine</strong> <strong>Administration</strong><br />
Select a Resource for a <strong>Virtual</strong> <strong>Machine</strong> Template<br />
When you deploy a virtual machine template, select a host or cluster resource for the template. The template<br />
must be registered with an ESXi host. The host handles all requests for the template and must be running<br />
when you create a virtual machine from the template.<br />
Procedure<br />
1 Search or browse for the host or cluster and select it.<br />
Any Compatibility problems appear at the bottom of the window.<br />
2 Click Next.<br />
Select a Datastore for the <strong>Virtual</strong> <strong>Machine</strong> Template<br />
Each virtual machine or virtual machine template requires a folder or directory for its virtual disks and files.<br />
When you create a virtual machine or template to deploy to the vCenter Server inventory, select a datastore<br />
or datastore cluster for the virtual machine's configuration and other files and all of the virtual disks. Each<br />
datastore can have a different size, speed, availability, and other properties.<br />
The amount of free space in the datastore is always changing. Ensure that you leave sufficient space for<br />
virtual machine creation and other virtual machine operations, such as growth of sparse files, snapshots,<br />
and so on. To review space utilization for the datastore by file type, see the <strong>vSphere</strong> Monitoring and<br />
Performance documentation.<br />
Thin provisioning lets you create sparse files with blocks that are allocated upon first access, which allows<br />
the datastore to be over-provisioned. The sparse files can continue growing and fill the datastore. If the<br />
datastore runs out of disk space while the virtual machine is running, it can cause the virtual machine to<br />
stop functioning.<br />
Procedure<br />
1 Select the format for the virtual machine's disks.<br />
Option<br />
Same format as source<br />
Thick Provision Lazy Zeroed<br />
Thick Provision Eager Zeroed<br />
Thin Provision<br />
Action<br />
Use the same format as the source virtual machine.<br />
Create a virtual disk in a default thick format. Space required for the<br />
virtual disk is allocated during creation. Any data remaining on the<br />
physical device is not erased during creation, but is zeroed out on demand<br />
at a later time on first write from the virtual machine.<br />
Create a thick disk that supports clustering features such as Fault<br />
Tolerance. Space required for the virtual disk is allocated at creation time.<br />
In contrast to the thick provision lazy zeroed format, the data remaining<br />
on the physical device is zeroed out during creation. It might take longer<br />
to create disks in this format than to create other types of disks.<br />
Use the thin provisioned format. At first, a thin provisioned disk uses only<br />
as much datastore space as the disk initially needs. If the thin disk needs<br />
more space later, it can grow to the maximum capacity allocated to it.<br />
2 (Optional) Select a storage policy from the VM Storage Policy drop-down menu.<br />
Storage policies specify storage requirements for applications that run on the virtual machine.<br />
40 <strong>VMware</strong>, Inc.