The frst step in implementing a virtualization infrastructure is deploying and confguring
the servers that will host your virtualized workloads  For the Windows Server platform, this
means being able to plan, install, and confgure Hyper-V hosts  This lesson helps you under-
stand the issues and considerations involved in planning host deployment  The lesson also
demonstrates how to confgure storage and networking for Hyper-V hosts.  

Planning Hyper-V deployment
Successful deployment requires careful planning ahead of time to ensure problems don’t
arise during or after the deployment process  The following issues should be considered when
planning the deployment of Hyper-V hosts within your datacenter:
  ■ Hardware
  ■ Editions
  ■ Networking
  ■ Storage
  ■ Management
  ■ Security
  ■ Scalability
  ■ Availability
  ■ Mobility
  ■ Disaster recovery

In addition, each of these issues should be considered from both the host and virtual
machine perspective before you begin to deploy Hyper-V hosts within your datacenter  While
the sections that follow focus mainly on considerations relating to planning host machines,
some mention of planning for virtual machines is also included where appropriate, especially
when it directly relates to host-planning issues 
Hardware
A key hardware requirement for a Hyper-V host is that the underlying host system sup-
port hardware-assisted virtualization such as Intel Virtualization Technology (Intel VT) or
AMD   Virtualization (AMD-V) technologies  In addition, hardware-enforced Data Execution
  Prevention (DEP) must be available and enabled on the host system. Specifcally, this means
that the Intel XD bit (the execute disable bit) or AMD NX bit (the no execute bit) must be
enabled 
Although you can install the Hyper-V role on a Windows Server 2012 server that meets
the minimum system requirements of a single-core, 1 4-GHz CPU and 512 MBs of RAM,
you probably won’t be able to run any virtual machines on that host machine  This is mainly
because each virtual machine you run on a host requires a minimum amount of RAM that
depends on the guest operating system installed in the virtual machine  In other words, the
number of virtual machines and types of virtualized workloads you can run on Hyper-V hosts
directly relate to the available hardware resources of the host 
To plan your host hardware, you therefore should start with the maximum supported
  processor and memory capabilities of Windows Server 2012, which are as follows:

  ■ Up to 64 physical processors (sockets) per host
  ■ Up to 320 logical processors (cores) per host
  ■ Up to 4 TBs of physical memory per host
Next, you should consider the maximum supported processor and memory capabilities for
virtual machines running on Windows Server 2012 Hyper-V hosts  These are as follows:
  ■ Up to 64 virtual processors per virtual machine (up to a total of 2048 virtual processors
per host)
  ■ Up to 1 TB of physical memory per virtual machine
  ■ Up to 1024 active virtual machines running on the host
Finally, you must decide how many virtual machines you want to run on each host  In
  deciding this, you must consider the following:
  ■ How many cores you can afford when you purchase your host systems
  ■ How much physical memory you can afford for your host systems
  ■ How much processing power and physical memory your virtualized workloads will
need for them to meet the performance requirements of your service level agreement
(SLA)

Videos :