6.0

3 Click the Virtual Hardware tab and click Add network adapter.
4 In the network connection panel, select either a network with a specic label or a legacy network.
5 (Optional) To congure the virtual NIC to connect when the virtual machine is powered on, select
Connect at power on.
6 Click Save.
Virtual Disk Configuration
You can add large-capacity virtual disks to virtual machines and add more space to existing disks, even
when the virtual machine is running. You can set most of the virtual disk parameters during virtual machine
creation or after you install the guest operating system.
You can store virtual machine data in a new virtual disk, an existing virtual disk, or a mapped SAN LUN. A
virtual disk, which appears as a single hard disk to the guest operating system, is composed of one or more
les on the host le system. You can copy or move virtual disks on the same hosts or between hosts.
For virtual machines running on an ESXi host, you can store the virtual machine data directly on a SAN
LUN instead of storing it in a virtual disk le. This ability is useful if you are running applications in your
virtual machines that must detect the physical characteristics of the storage device. Additionally, mapping a
SAN LUN allows you to use existing SAN commands to manage storage for the disk.
To accelerate virtual machine performance, you can congure virtual machines to use vSphere Flash Read
Cache™. For details about Flash Read Cache behavior, see the vSphere Storage documentation.
When you map a LUN to a VMFS volume, vCenter Server or the ESXi host creates a raw device mapping
(RDM) le that points to the raw LUN. Encapsulating disk information in a le allows vCenter Server or the
ESXi host to lock the LUN so that only one virtual machine can write to it. This le has a .vmdk extension,
but the le contains only disk information that describes the mapping to the LUN on the ESXi system. The
actual data is stored on the LUN. You cannot deploy a virtual machine from a template and store its data on
a LUN. You can store only its data in a virtual disk le.
The amount of free space in the datastore is always changing. Ensure that you leave sucient space for
virtual machine creation and other virtual machine operations, such as growth of sparse les, snapshots,
and so on. To review space utilization for the datastore by le type, see the vSphere Monitoring and
Performance documentation.
Thin provisioning lets you create sparse les with blocks that are allocated upon rst access, which allows
the datastore to be over-provisioned. The sparse les can continue growing and ll the datastore. If the
datastore runs out of disk space while the virtual machine is running, it can cause the virtual machine to
stop functioning.
About Virtual Disk Provisioning Policies
When you perform certain virtual machine management operations, such as creating a virtual disk, cloning
a virtual machine to a template, or migrating a virtual machine, you can specify a provisioning policy for the
virtual disk le.
NFS datastores with Hardware Acceleration and VMFS datastores support the following disk provisioning
policies. On NFS datastores that do not support Hardware Acceleration, only thin format is available.
vSphere Single Host Management - VMware Host Client
58 VMware, Inc.