CP5092 – UNIT 2

UNIT 2

VIRTUALIZATION INFRASTRUCTURE

Comprehensive Analysis – Resource Pool – Testing Environment –Server Virtualization –

Virtual Workloads – Provision Virtual Machines – Desktop Virtualization – Application
Virtualization - Implementation levels of virtualization – virtualization structure – virtualization
of CPU, Memory and I/O devices – virtual clusters and Resource Management – Virtualization
for data center automation.

2.2 Resource Pool:

Resource pooling is an IT term used in cloud computing environments to describe a situation in

which providers serve multiple clients, customers or "tenants" with provisional and scalable
services. These services can be adjusted to suit each client's needs without any changes being
apparent to the client or end user. A VMware resource pool is the aggregated physical compute
hardware -- CPU and memory, as well as other components -- allocated to virtual machines
(VMs) in a VMware virtual infrastructure. A VMware administrator can choose how much of
each physical resource to allocate to each new VM and allocate portions of these logical resource
groups to various users, add and remove compute resources, or reorganize pools as required. 

The VMware resource pool manages and optimizes these physical resources for virtual systems
within a VMware Distributed Resource Scheduler (DRS) cluster. With memory over commit,
more resources can be allocated to VMs than are physically available. Changes that occur in one
resource pool will not affect other, unrelated resource pools VMware administrators create. 

Administrators use VMware vCenter, third-party tools, or command-line interfaces (CLI) like
esxtop to monitor resource pools, gathering detailed CPU and memory statistics. End users
should not make changes to the resource pools. The kinds of services that can apply to a resource
pooling strategy include data storage services, processing services and bandwidth provided
services. Other related terms include rapid elasticity, which also involves the dynamic
provisioning of services, and on-demand self-service, where customers could change their levels
of service without actually contacting a service provider. All of this automated service
provisioning is a lot like other kinds of business process automation, which replaced more
traditional, labor-intensive strategies with new innovations that rely on increasingly powerful

1
 CP5092 – UNIT 2

virtual networks and data handling resources. In these cases, the goal is to separate the client
experience from the actual administration of assets, so that the process of delivery is opaque and
the services seem to be automatically and infinitely available.

2.4 SERVER VIRTUALIZATION:

Server virtualization is the masking of server resources, including the number and
identity of individual physical servers, processors, and operating systems, from server users. The
server administrator uses a software application to divide one physical server into multiple
isolated virtual environments. The virtual environments are sometimes called virtual private
servers, but they are also known as guests, instances, containers or emulations. There are three
popular approaches to server virtualization: the virtual machine model, the paravirtual machine
model, and virtualization at the operating system (OS) layer.

Virtual machines are based on the host/guest paradigm. Each guest runs on a virtual imitation of
the hardware layer. This approach allows the guest operating system to run without
modifications. It also allows the administrator to create guests that use different operating
systems. The guest has no knowledge of the host's operating system because it is not aware that
it's not running on real hardware. It does, however, require real computing resources from the
host -- so it uses a hypervisor to coordinate instructions to the CPU. The hypervisor is called a
virtual machine monitor (VMM). It validates all the guest-issued CPU instructions and manages
any executed code that requires addition privileges. VMware and Microsoft Virtual Server both
use the virtual machine model.

The paravirtual machine (PVM) model is also based on the host/guest paradigm -- and it uses a
virtual machine monitor too. In the paravirtual machine model, however, The VMM actually
modifies the guest operating system's code. This modification is called porting. Porting supports
the VMM so it can utilize privileged systems calls sparingly. Like virtual machines, paravirtual
machines are capable of running multiple operating systems. Xen and UML both use the
paravirtual machine model. Virtualization at the OS level works a little differently. It isn't based
on the host/guest paradigm. In the OS level model, the host runs a single OS kernel as its core
and exports operating system functionality to each of the guests. Guests must use the same

2
 CP5092 – UNIT 2

operating system as the host, although different distributions of the same system are allowed.
This distributed architecture eliminates system calls between layers, which reduces CPU usage
overhead. It also requires that each partition remain strictly isolated from its neighbors so that a
failure or security breach in one partition isn't able to affect any of the other partitions. In this
model, common binaries and libraries on the same physical machine can be shared, allowing an
OS level virtual server to host thousands of guests at the same time. Virtuozzo and Solaris Zones
both use OS-level virtualization.

Server virtualization can be viewed as part of an overall virtualization trend in enterprise IT that
includes storage virtualization, network virtualization, and workload management. This trend is
one component in the development of autonomic computing, in which the server environment
will be able to manage itself based on perceived activity. Server virtualization can be used to
eliminate server sprawl, to make more efficient use of server resources, to improve server
availability, to assist in disaster recovery, testing and development, and to centralize server
administration.

2.6 PROVISION VIRTUAL MACHINES:

VMware provides several methods to provision vSphere virtual machines. The optimal method
for your environment depends on factors such as the size and type of your infrastructure and the
goals you are trying to achieve.

Create a single virtual machine if no other virtual machines in your environment have the
requirements you are looking for, such as a particular operating system or hardware
configuration. For example, you might need a virtual machine that is configured only for testing
purposes. You can also create a single virtual machine and install an operating system on it, then
use that virtual machine as a template to clone other virtual machines from. See Creating a
Virtual Machine.

Deploy and export virtual machines, virtual appliances, and vApps stored in Open Virtual
Machine Format (OVF) to use a preconfigured virtual machine. A virtual appliance is a prebuilt
virtual machine that typically has an operating system and other software already installed. You
can deploy virtual machines from local file systems, such as local disks (such as C:), removable
media (such as CDs or USB keychain drives), and shared network drives. See Deploying OVF
Templates.

Create a template to deploy multiple virtual machines from. A template is a master copy of a
virtual machine that you can use to create and provision virtual machines. Templates can be a

3
 CP5092 – UNIT 2

real time saver. If you have a virtual machine that you want to clone frequently, make that virtual
machine a template. See Working with Templates and Clones.

Cloning a virtual machine can save time if you are deploying many similar virtual machines.
You can create, configure, and install software on a single virtual machine and clone it multiple
times, rather than creating and configuring each virtual machine individually. See Working with
Templates and Clones.

2.7 DESKTOP VIRTUALIZATION:

Desktop virtualization is the concept of isolating a logical operating system (OS) instance from

the client that is used to access it.

There are several different conceptual models of desktop virtualization, which can broadly be
divided into two categories based on whether or not the operating system instance is executed
locally or remotely. It is important to note that not all forms of desktop virtualization technology
involve the use of virtual machines (VMs).

Types of desktop virtualization technologies

Host-based forms of desktop virtualization require that users view and interact with their virtual
desktops over a network by using a remote display protocol. Because processing takes place in
a data center, client devices can be traditional PCs, but also thin clients, zero
clients, smartphones and tablets. Examples of host-based desktop virtualization technology
include:

Host-based virtual machines: Each user connects to an individual VM that is hosted in a data
center. The user may connect to the same VM every time, allowing for personalization (known
as a persistent desktop), or be given a fresh VM at each login (a nonpersistent desktop).

Shared hosted: Users connect to a shared desktop that runs on a server. Microsoft Remote
Desktop Services, formerly Terminal Services, takes this client-server approach. Users may also

4
 CP5092 – UNIT 2

connect to individual applications running on a server; this technology is an example

of application virtualization.

Host-based physical machines: The operating system runs directly on another device's physical
hardware.

Client virtualization requires processing to occur on local hardware; the use of thin clients, zero
clients and mobile devices is not possible. These types of desktop virtualization include:

OS image streaming: The operating system runs on local hardware, but it boots to a remote disk
image across the network. This is useful for groups of desktops that use the same disk image. OS
image streaming, also known as remote desktop virtualization, requires a constant network
connection in order to function.

Client-based virtual machines: A VM runs on a fully functional PC, with a hypervisor in place.
Client-based virtual machines can be managed by regularly syncing the disk image with a server,
but a constant network connection is not necessary in order for them to function.

Desktop virtualization vs. virtual desktop infrastructure

The terms desktop virtualization and virtual desktop infrastructure (VDI) are often used

interchangeably, but they are not the same. While VDI is a type of desktop virtualization, not all
desktop virtualization uses VDI.

5
 CP5092 – UNIT 2

2.8 APPLICATION VIRTUALIZATION:

App virtualization (application virtualization) is the separation of an installation of

an application from the client computer accessing it.

From the user's perspective, the application works just like it would if it lived on the user's
device. The user can move or resize the application window, as well as carry out keyboard and

6
 CP5092 – UNIT 2

mouse operations. There might be subtle differences at times, but for the most part, the user
should have a seamless experience.

How application virtualization works

Although there are multiple ways to virtualize applications, IT teams often take a server-based
approach, delivering the applications without having to install them on individual desktops.
Instead, administrators implement remote applications on a server in the company's data center
or with a hosting service, and then deliver them to the users' desktops.

To make this possible, IT must use an application virtualization product. Application

virtualization vendors and their products include Microsoft App-V, Citrix XenApp, Parallels
Remote Application Server, and VMware ThinApp or App Volumes -- both of which are
included with VMware Horizon View. VMware also offers Horizon Apps to further support app
virtualization.

The virtualization software essentially transmits the application as individual pixels from the
hosting server to the desktops using a remote display protocol such as Microsoft
RemoteFX, Citrix HDX, or VMware View PCoIP or Blast Extreme. The user can then access
and use the app as though it were installed locally. Any user actions are transmitted back to the
server, which carries them out.

Benefits of app virtualization

App virtualization can be an effective way for organizations to implement and maintain
their desktop applications. One of the benefits of application virtualization is that administrators
only need to install an application once to a centralized server rather than to multiple desktops.
This also makes it simpler to update applications and roll out patches.

In addition, administrators have an easier time controlling application access. For example, if a
user should no longer be able to access an application, the administrator can deny access
permissions to the application without having to uninstall it from the user's desktop. App

7
 CP5092 – UNIT 2

virtualization makes it possible to run applications that might conflict with a user's desktop
applications or with other virtualized applications.

Users can also access virtualized applications from thin clientsor non-Windows computers. The
applications are immediately available, without having to wait for long install or load operations.
If a computer is lost or stolen, sensitive application data stays on the server and does not get
compromised.

Drawbacks of app virtualization

Application virtualization does have its challenges, however. Not all applications are suited to
virtualization. Graphics-intensive applications, for example, can get bogged down in the

8
 CP5092 – UNIT 2

rendering process. In addition, users require a steady and reliable connection to the server to use
the applications.

The use of peripheral devices can get more complicated with app virtualization, especially when
it comes to printing. System monitoring products can also have trouble with virtualized
applications, making it difficult to troubleshoot and isolate performance issues.