Вы находитесь на странице: 1из 15

P&G Training Institute

Virtual machine creation is very easy task. But

selecting the right configuration require
knowledge on each and every component
which includes
NIC Card
Flexible (Vlance)
With new operating system we will not able to
see flexible adapter option while creating VMs
Its an old adapter of 10 mbps also known as
vlance adapter
This adapter is said as flexible adapter as its
change its adapter once the VM guest tools are
When you power on a vm its identifies itself as
Vlance adapter and once the guest tools are
installed it convert itself to VMXnet adapter
An software version of the Intel 82545EM
Gigabit Ethernet NIC
Almost all current OS has the Intel E1000
Drivers. And it is coon driver which is used in
The VMXNET virtual network adapter has no
physical counterpart.
VMXNET is optimized for performance in a
virtual machine.
Because operating system vendors do not
provide built-in drivers for this card, you
must install VMware Tools to have a driver for
the VMXNET network adapter available
Raw device mapping (RDM) is an option in
the VMware environment that enables a storage
logical unit number (LUM) to be directly connected to
a virtual machine (VM) from the storage area network

If you want to assign more than 2TB of LUN you can

assign through RDM as there was limitation in earlier
version of ESXi that datastore could be exceed more
than 2TB

There are two type of RDM

When RDM is allocated in Physical compatibility
mode all the host passes all I/O related
operation and SCSI command directly to the
storage device

The disadvantage of this type of disk is that it

will not able to utilize VMware features such as
snapshot , cloning , svMotion

Physical RDM is used in the scenario where you

want a create a VM to monitor storage devices in
that scenario we need to create Physical RDM as
its directly communicate with storage.
As the name state is virtual , it virtualizes all
SCSI commands at the VM level and then its
passes to storage

In virtual RDM features such as snapshot,

cloning, svMotion
Thick Provision Lazy Zeroed
Thick Provision Eager Zeroed
Thin Provision
A thick provisioned lazy zeroed VMDK is similar to the eager
zeroed except that instead the zeroing is written to the disk just
before a write operation and not at creation.

The space is fully allocated to a VM but its zeroed

In this process if you assign a 80 GB LUN to a VM it will be

allocated immediately as disk is getting zeroed @ the writing
time. So if you are using 10 GB from an 80 GB of allocated disk
only 10 GB will be zeroed and rest 70 GB will not.

Performance of the lazy zeroed is not as good as eager zeroed

but is better than thin provisioned. Because data writing and
zeroing is done @ the same time so there could a minimal
performance impact when using this type of disk.
When a thick provisioned eager zeroed disk is created the
maximum size of the disk is allocated to the VMDK and all
of that space is zeroed out

Zeroing means erasing the previous data which was

present on the LUN.

While creation this type of disk it takes a time to provision

the VMDK to a VM, Because its writing zero after creation.

This type of disk is required for FT, HA , Microsoft cluster

(Microsoft recommend to use eager zero disk) as this type
of disk has better performance than lazy zeroed and thin
Persistent Disk
Non-Persistent Disk

Persistent Disk
In this type VMDK is configured in Independent
Persistent Mode. You cant take snapshot means you
cant revert snapshot if you want to move your
machine to earlier state
Mostly Domain Controller Disk are persistent disk
In this type a VMDK is configured as
Independent Non-Persistent Mode, if the
changes done on this type of disk and you
power off your machine changes will not be

Changes are saved if you restart or shutdown

your machine. And again it is lost when you
power off your machine.
END Of Session