Hyper-V Overview


This topic describes the Hyper-V role in Windows Server® 2012 -- practical uses for the role, the most significant new or updated functionality in this version compared to previous versions of Hyper-V, hardware requirements, and a list of operating systems (known as guest operating systems) supported for use in a Hyper-V virtual machine.

Did you mean…
Role and technology description
The Hyper-V role enables you to create and manage a virtualized computing environment by using virtualization technology that is built in to Windows Server 2012. Installing the Hyper-V role installs the required components and optionally installs management tools. The required components include Windows hypervisor, Hyper-V Virtual Machine Management Service, the virtualization WMI provider, and other virtualization components such as the virtual machine bus (VMbus), virtualization service provider (VSP) and virtual infrastructure driver (VID).
The management tools for the Hyper-V role consist of:
  • GUI-based management tools: Hyper-V Manager, a Microsoft Management Console (MMC) snap-in, and Virtual Machine Connection, which provides access to the video output of a virtual machine so you can interact with the virtual machine.
  • Hyper-V-specific cmdlets for Windows PowerShell. Windows Server 2012 includes a Hyper-V module, which provides command-line access to all the functionality available in the GUI, as well functionality not available through the GUI. For more information about the Hyper-V module, see Hyper-V Module for Windows PowerShell.
If you use Server Manager to install the Hyper-V role, the management tools are included unless you specifically exclude them. If you use Windows PowerShell to install the Hyper-V role, the management tools are not included by default. To install the tools, use the parameter –IncludeManagementTools. For instructions about installing the Hyper-V role, see Install the Hyper-V Role and Configure a Virtual Machine.
noteNote
Hyper-V management tools in Windows Server 2012 are designed to manage this version of Hyper-V only. The tools cannot be used to manage earlier versions of Hyper-V.
The Hyper-V technology virtualizes hardware to provide an environment in which you can run multiple operating systems at the same time on one physical computer. Hyper-V enables you to create and manage virtual machines and their resources. Each virtual machine is an isolated, virtualized computer system that can run its own operating system. The operating system that runs within a virtual machine is called a guest operating system.
For more information about the architecture of Hyper-V, see the Windows Server 2012 Hyper-V Component Architecture Poster.
Practical applications
Hyper-V provides infrastructure so you can virtualize applications and workloads to support a variety of business goals aimed at improving efficiency and reducing costs, such as:
  • Establish or expand a private cloud environment. Hyper-V can help you move to or expand use of shared resources and adjust utilization as demand changes, to provide more flexible, on-demand IT services.
  • Increase hardware utilization. By consolidating servers and workloads onto fewer, more powerful physical computers, you can reduce consumption of resources such as power and physical space.
  • Improve business continuity. Hyper-V can help you minimize the impact of both scheduled and unscheduled downtime of your workloads.
  • Establish or expand a virtual desktop infrastructure (VDI). A centralized desktop strategy with VDI can help you increase business agility and data security, as well as simplify regulatory compliance and management of the desktop operating system and applications. Deploy Hyper-V and Remote Desktop Virtualization Host (RD Virtualization Host) on the same physical computer to make personal virtual desktops or virtual desktop pools available to your users.
  • Increase efficiency in development and test activities. You can use virtual machines to reproduce different computing environments without the need for acquiring or maintaining all the hardware you would otherwise need.
New and changed functionality
Hyper-V in Windows Server 2012 includes improvements in many areas. The following table lists the most significant functionality changes in this version of Hyper-V. For more details about these changes, as well as additional changes in functionality that are not listed here, see What's New in Hyper-V.

 

Feature/functionalityNew or updatedSummary
Client Hyper-V (Hyper-V in Windows® 8 Pro)
New
Create and run Hyper-V virtual machines using a Windows desktop operating system.
Hyper-V module for Windows PowerShell
New
Use Windows PowerShell cmdlets to create and manage your Hyper-V environment.
Hyper-V Replica
New
Replicate virtual machines between storage systems, clusters, and data centers to provide business continuity and disaster recovery.
Live migration
Updated
Perform live migrations on non-clustered as well as clustered virtual machines, and perform more than one live migration at the same time.
Significantly increased scale and improved resiliency
Updated
Use significantly larger compute and storage resources than was previously possible. Improved handling of hardware errors increases the resiliency and stability of the virtualization environment.
For more information, see Hyper-V Scalability in Windows Server 2012.
Storage migration
New
Move the virtual hard disks of running virtual machines to different storage locations without downtime.
Virtual Fibre Channel
New
Connect to Fibre Channel storage from within a guest operating system.
Virtual hard disk format
Updated
Create stable, high-performance virtual hard disks up to 64 terabytes.
Virtual switch
Updated
New capabilities such as network virtualization, support for multi-tenancy, and extensions that Microsoft partners can provide to add functionality for monitoring, forwarding, and filtering packets.
Hardware requirements
Hyper-V requires a 64-bit processor that includes the following:
  • Hardware-assisted virtualization. This is available in processors that include a virtualization option—specifically processors with Intel Virtualization Technology (Intel VT) or AMD Virtualization (AMD-V) technology.
  • Hardware-enforced Data Execution Prevention (DEP) must be available and enabled. Specifically, you must enable Intel XD bit (execute disable bit) or AMD NX bit (no execute bit).
Software requirements (for supported guest operating systems)
Hyper-V includes a software package for supported guest operating systems that improves integration between the physical computer and the virtual machine. This package is referred to as integration services. In general, you install this package in the guest operating system as a separate procedure after you set up the operating system in the virtual machine. However, some operating systems have the integration systems built-in and do not require a separate installation. For instruction on installing integration services, see Install the Hyper-V Role and Configure a Virtual Machine.
The following table lists the operating systems supported in Windows Server 2012 for use as guest operating systems in Hyper-V virtual machines, as well as provides information about integration services. This includes information about certain Linux distributions for which integration services are available. Microsoft provides support for issues found in the integration services.

 

Guest operating system (server)Maximum number of virtual processorsNotes
Windows Server 2012
64
Integration services do not require a separate installation because they are built-in.
Windows Server 2008 R2 with Service Pack 1 (SP 1)
64
Datacenter, Enterprise, Standard and Web editions. Install the integration services after you set up the operating system in the virtual machine.
Windows Server 2008 R2
64
Datacenter, Enterprise, Standard and Web editions. Upgrade the integration services after you set up the operating system in the virtual machine.
Windows Server 2008 with Service Pack 2 (SP 2)
8
Datacenter, Enterprise, Standard and Web editions (32-bit and 64-bit). Install the integration services after you set up the operating system in the virtual machine.
Windows Home Server 2011
4
Edition information is not applicable. Install the integration services after you set up the operating system in the virtual machine.
Windows Small Business Server 2011
Essentials edition - 2
Standard edition - 4
Essentials and Standard editions. Install the integration services after you set up the operating system in the virtual machine.
Windows Server 2003 R2 with Service Pack 2 (SP2)
2
Standard, Web, Enterprise, and Datacenter editions (32-bit and 64-bit). Install the integration services after you set up the operating system in the virtual machine.
Windows Server 2003 with Service Pack 2
2
Standard, Web, Enterprise, and Datacenter editions (32-bit and 64-bit). Install the integration services after you set up the operating system in the virtual machine.
CentOS 5.7 and 5.8
64
CentOS 6.0 – 6.3
64
Red Hat Enterprise Linux 5.7 and 5.8
64
Red Hat Enterprise Linux 6.0 – 6.3
64
SUSE Linux Enterprise Server 11 SP2
64
Integration services do not require a separate installation because they are built-in.
Open SUSE 12.1
64
Integration services are built-in and do not require a separate download and installation.
Ubuntu 12.04
64
Integration services are built-in and do not require a separate download and installation.

 

Guest operating system (client)Maximum number of virtual processorsNotes
Windows 8
32
Integration services do not require a separate installation because they are built-in.
Windows 7 with Service Pack 1 (SP 1)
4
Ultimate, Enterprise, and Professional editions (32-bit and 64-bit). Upgrade the integration services after you set up the operating system in the virtual machine.
Windows 7
4
Ultimate, Enterprise, and Professional editions (32-bit and 64-bit). Upgrade the integration services after you set up the operating system in the virtual machine.
Windows Vista with Service Pack 2 (SP2)
2
Business, Enterprise, and Ultimate, including N and KN editions. Install the integration services after you set up the operating system in the virtual machine.
Windows XP with Service Pack 3 (SP3)
2
Professional. Install the integration services after you set up the operating system in the virtual machine.
Windows XP x64 Edition with Service Pack 2 (SP 2)
2
Professional. Install the integration services after you set up the operating system in the virtual machine.
CentOS 5.7 and 5.8
64
CentOS 6.0 – 6.3
64
Red Hat Enterprise Linux 5.7 and 5.8
64
Red Hat Enterprise Linux 6.0 – 6.3
64
SUSE Linux Enterprise Server 11 SP2
64
Integration services do not require a separate installation because they are built-in.
Open SUSE 12.1
64
Integration services do not require a separate installation because they are built-in.
Ubuntu 12.04
64
Integration services do not require a separate installation because they are built-in.
See also
The following table provides links to related articles and technologies.

 

Content typeReferences
Product evaluation
Troubleshooting
Tools and settings
Community resources
Related technologies
Posted by
Labels:

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)