Home
If you have not finish reading previous post please goto following [url=Deploying and confguring virtual machines][/url]Link and download videos if you require video tutorials for Hyper-V Configuration.
After deploying and confguring your Hyper-V hosts, the next step in implementing your
virtualization infrastructure is deploying and confguring the virtual machines that will be
used to virtualize your server workloads This lesson helps you understand the issues and
considerations involved in planning virtual machine deployment and how to create and
confgure virtual machines.
virtualization infrastructure is deploying and confguring the virtual machines that will be
used to virtualize your server workloads This lesson helps you understand the issues and
considerations involved in planning virtual machine deployment and how to create and
confgure virtual machines.
Planning virtual machine deployment
Depending on the scenario being envisioned, deploying a virtual machine can mean different
things, for example:
■ Creating a new virtual machine, and installing a guest operating system and
applications on it
■ Importing an existing virtual machine that already has a guest operating system and
applications installed on it
■ Performing a physical-to-virtual (P2V) conversion of a physical server to migrate the
server’s operating system and applications into a virtual machine
■ Performing a virtual-to-virtual (V2V) conversion by converting a VMware virtual
machine to a Hyper-V virtual machine
The frst two types of virtual-machine deployments can be performed using the in-box
management tools of the Hyper-V role of Windows Server 2012—specifcally, the Hyper-V
Manager and the Hyper-V module for Windows PowerShell Deploying new virtual machines
by performing P2V or V2V conversions requires additional tools, such as System Center
Virtual Machine Manager or third-party utilities
Depending on the scenario being envisioned, deploying a virtual machine can mean different
things, for example:
■ Creating a new virtual machine, and installing a guest operating system and
applications on it
■ Importing an existing virtual machine that already has a guest operating system and
applications installed on it
■ Performing a physical-to-virtual (P2V) conversion of a physical server to migrate the
server’s operating system and applications into a virtual machine
■ Performing a virtual-to-virtual (V2V) conversion by converting a VMware virtual
machine to a Hyper-V virtual machine
The frst two types of virtual-machine deployments can be performed using the in-box
management tools of the Hyper-V role of Windows Server 2012—specifcally, the Hyper-V
Manager and the Hyper-V module for Windows PowerShell Deploying new virtual machines
by performing P2V or V2V conversions requires additional tools, such as System Center
Virtual Machine Manager or third-party utilities
The following issues should be considered when creating new virtual machines on a
Hyper-V host:
■ Location of confguration fles
■ Startup memory
■ Dynamic Memory
■ Virtual processors
■ Virtual networking
■ Virtual hard disks
■ Guest operating system deployment
■ Performing snapshots
Note that these issues apply mainly to the creation of new virtual machines Importing
existing virtual machines entails a different set of conditions that are described separately
later in this section
Hyper-V host:
■ Location of confguration fles
■ Startup memory
■ Dynamic Memory
■ Virtual processors
■ Virtual networking
■ Virtual hard disks
■ Guest operating system deployment
■ Performing snapshots
Note that these issues apply mainly to the creation of new virtual machines Importing
existing virtual machines entails a different set of conditions that are described separately
later in this section
Location of confguration fles
Although the default location where virtual machine confguration fles is confgured at the
host level, you also have the option of overriding this default when you create a new virtual
machine You might do this, for example, if you are creating a virtual machine for high avail-
ability—that is, a clustered virtual machine on a failover cluster of Hyper-V hosts that uses
CSV shared storage In such a scenario, you need to specify the CSV under the ClusterStorage
folder in Failover Cluster Manager as the location where the virtual machine will be stored
Another scenario where you might override the default confguration fle storage location
is when you are creating a virtual machine that will be stored on a SMB 3.0 fle share on a
Scale-Out File Server. In this case, you would specify the client access point that is confgured
in the failover cluster for the Scale-Out File Server as the location where the virtual machine
will be stored For an example of this second scenario, see http://technet.microsoft.com/en-us/library/hh831463.aspx
Although the default location where virtual machine confguration fles is confgured at the
host level, you also have the option of overriding this default when you create a new virtual
machine You might do this, for example, if you are creating a virtual machine for high avail-
ability—that is, a clustered virtual machine on a failover cluster of Hyper-V hosts that uses
CSV shared storage In such a scenario, you need to specify the CSV under the ClusterStorage
folder in Failover Cluster Manager as the location where the virtual machine will be stored
Another scenario where you might override the default confguration fle storage location
is when you are creating a virtual machine that will be stored on a SMB 3.0 fle share on a
Scale-Out File Server. In this case, you would specify the client access point that is confgured
in the failover cluster for the Scale-Out File Server as the location where the virtual machine
will be stored For an example of this second scenario, see http://technet.microsoft.com/en-us/library/hh831463.aspx
Startup memory
The memory that each new virtual machine will need is an important consideration when
planning the creation of new virtual machines. Physical host systems have a fxed amount
of physical memory, and this memory must be shared in an appropriate way between the
The memory that each new virtual machine will need is an important consideration when
planning the creation of new virtual machines. Physical host systems have a fxed amount
of physical memory, and this memory must be shared in an appropriate way between the
different virtual machines that run on the host (The host itself also requires some physical
memory in order to function with optimum performance ) Planning the amount of physical
memory to be allocated to a new virtual machine you will create involves two considerations:
■ Deciding upon the amount of startup memory to be assigned to the virtual machine
The guest operating installed in a virtual machine must have access to suffcient
memory; otherwise, the virtual machine might not be able to start The recommended
startup memory varies with the guest operating system involved and also on whether
Dynamic Memory is enabled on the host Some recommended values for startup
memory include
■ 512 MBs for Windows Server 2008 R2 and Windows 7
■ 128 MBs for Windows Server 2003
■ Deciding whether to enable Dynamic Memory on the virtual machine Dynamic
Memory manages physical memory on the host as a shared resource that can be
automatically reallocated among running virtual machines based on changes in
memory demand and values you can specify Dynamic Memory will be discussed in more
detail in later post.
memory in order to function with optimum performance ) Planning the amount of physical
memory to be allocated to a new virtual machine you will create involves two considerations:
■ Deciding upon the amount of startup memory to be assigned to the virtual machine
The guest operating installed in a virtual machine must have access to suffcient
memory; otherwise, the virtual machine might not be able to start The recommended
startup memory varies with the guest operating system involved and also on whether
Dynamic Memory is enabled on the host Some recommended values for startup
memory include
■ 512 MBs for Windows Server 2008 R2 and Windows 7
■ 128 MBs for Windows Server 2003
■ Deciding whether to enable Dynamic Memory on the virtual machine Dynamic
Memory manages physical memory on the host as a shared resource that can be
automatically reallocated among running virtual machines based on changes in
memory demand and values you can specify Dynamic Memory will be discussed in more
detail in later post.
Virtual processors
Some workloads can require additional processor resources in order to perform optimally
Hyper-V allows you to assign one or more virtual processors to each virtual machine run-
ning on the host, up to the maximum number of logical processors supported by the guest
operating system installed in the virtual machine You can also use Hyper-V to keep a reserve
of the processor resources available to a virtual machine, specify a limit to the amount of pro-
cessor resources the virtual machine can use, and confgure how Hyper-V allocates processor
resources when multiple running virtual machines on a host compete for the host’s processor
resources For more information on resource control settings for virtual processors, see
http://technet.microsoft.com/en-us/library/cc742470.aspx
Some workloads can require additional processor resources in order to perform optimally
Hyper-V allows you to assign one or more virtual processors to each virtual machine run-
ning on the host, up to the maximum number of logical processors supported by the guest
operating system installed in the virtual machine You can also use Hyper-V to keep a reserve
of the processor resources available to a virtual machine, specify a limit to the amount of pro-
cessor resources the virtual machine can use, and confgure how Hyper-V allocates processor
resources when multiple running virtual machines on a host compete for the host’s processor
resources For more information on resource control settings for virtual processors, see
http://technet.microsoft.com/en-us/library/cc742470.aspx
Virtual networking
Virtual networking involves creating virtual network adapters in virtual machines and
assigning these adapters to virtual switches on the host The following considerations apply
when planning virtual networking for virtual machines:
■ Each virtual machine can have up to 12 virtual network adapters installed in it Of
these 12 virtual network adapters, up to 8 can be the network adapter type and up
to the 4 can be the legacy network adapter type These two types of virtual network
adapters are discussed in more detail later in this lesson
■ Each virtual network adapter can be confgured with either a static MAC address or a
dynamic MAC address that is automatically assigned from the confgured MAC address
range on the host
Virtual networking involves creating virtual network adapters in virtual machines and
assigning these adapters to virtual switches on the host The following considerations apply
when planning virtual networking for virtual machines:
■ Each virtual machine can have up to 12 virtual network adapters installed in it Of
these 12 virtual network adapters, up to 8 can be the network adapter type and up
to the 4 can be the legacy network adapter type These two types of virtual network
adapters are discussed in more detail later in this lesson
■ Each virtual network adapter can be confgured with either a static MAC address or a
dynamic MAC address that is automatically assigned from the confgured MAC address
range on the host
■ Each virtual network can be assigned a unique VLAN channel to segment or isolate
network traffc.
■ Up to 512 virtual machines can be assigned to each virtual switch on the host
network traffc.
■ Up to 512 virtual machines can be assigned to each virtual switch on the host
Virtual hard disks
When you create a new virtual machine, you have three options concerning the virtual hard
disks associated with the new virtual machines:
■ You can create a new virtual hard disk when you create the new virtual machine
■ You can assign an existing virtual hard disk to the new virtual machine you are
creating
■ You can create a new virtual machine with no virtual hard disk and then assign a virtual
hard disk to it afterwards
Another planning consideration concerning virtual hard disks is the type of storage con-
troller used for the disk Virtual machines include both IDE and SCSI controllers, and you can
add virtual hard disks to either type of controller And while the startup (boot) disk of a virtual
machine must be connected to the IDE controller, the underlying physical storage used for
the virtual IDE device can be any of the storage types described in the section titled “Storage”
Another planning consideration is the type of virtual disk to use—namely, one of the
following types:
■ Fixed-size This type of virtual hard disk has its image fle pre-allocated on the
physical storage device for the maximum size requested when the disk is created For
example, a 250-GB, fxed-size virtual hard disk will occupy 250 GBs of space on the
host’s storage device
■ Dynamically expanding This type of virtual hard disk uses only as much physical
storage space as it needs to store the actual data that the disk currently contains
The size of the virtual disk’s image fle then grows as additional data is written to it.
For example, the image fle for a dynamic virtual hard disk of a newly created vir-
tual machine that has no operating system installed on it has a size of only 4 MBs
even though its maximum size is confgured with the default value of 127 GBs. Once
Windows Server 2012 has been installed as the guest operating system, however,
the size of the virtual disk’s image fle will grow to more than 8 GBs. See Lesson 3
in this chapter for information on how to expand, compact, or shrink dynamically
expanding disks
Read MoreWhen you create a new virtual machine, you have three options concerning the virtual hard
disks associated with the new virtual machines:
■ You can create a new virtual hard disk when you create the new virtual machine
■ You can assign an existing virtual hard disk to the new virtual machine you are
creating
■ You can create a new virtual machine with no virtual hard disk and then assign a virtual
hard disk to it afterwards
Another planning consideration concerning virtual hard disks is the type of storage con-
troller used for the disk Virtual machines include both IDE and SCSI controllers, and you can
add virtual hard disks to either type of controller And while the startup (boot) disk of a virtual
machine must be connected to the IDE controller, the underlying physical storage used for
the virtual IDE device can be any of the storage types described in the section titled “Storage”
Another planning consideration is the type of virtual disk to use—namely, one of the
following types:
■ Fixed-size This type of virtual hard disk has its image fle pre-allocated on the
physical storage device for the maximum size requested when the disk is created For
example, a 250-GB, fxed-size virtual hard disk will occupy 250 GBs of space on the
host’s storage device
■ Dynamically expanding This type of virtual hard disk uses only as much physical
storage space as it needs to store the actual data that the disk currently contains
The size of the virtual disk’s image fle then grows as additional data is written to it.
For example, the image fle for a dynamic virtual hard disk of a newly created vir-
tual machine that has no operating system installed on it has a size of only 4 MBs
even though its maximum size is confgured with the default value of 127 GBs. Once
Windows Server 2012 has been installed as the guest operating system, however,
the size of the virtual disk’s image fle will grow to more than 8 GBs. See Lesson 3
in this chapter for information on how to expand, compact, or shrink dynamically
expanding disks
Last edited by Formatted on 20th October 2013, 9:27 pm; edited 1 time in total
