Академический Документы
Профессиональный Документы
Культура Документы
http://technet.microsoft.com/en-us/library/cc732470(v=ws.10).aspx
Tip Hyper-V is enhanced in Windows Server 2012. Explore the Evaluation Guide and download the Windows Server 2012 Trial.
Hyper-V is a role in Windows Server 2008 and Windows Server 2008 R2 that provides you with the tools and services you can use to create a virtualized server computing environment. This type of environment is useful because you can create and manage virtual machines, which allow you to run multiple operating systems on one physical computer and isolate the operating systems from each other. This guide introduces Hyper-V by providing instructions for installing this role and configuring a virtual machine.
Note For a more in-depth introduction to using Hyper-V, see Getting to Know Hyper-V: A Walkthrough from Initial Setup to Common Scenarios. It shows you how to use features that make it easier to create multiple virtual machines and to make temporary changes that you can easily roll back.
In this guide
Requirements for Hyper-V Step 1: Install Hyper-V Step 2: Create and set up a virtual machine Step 3: Install the guest operating system and integration services Step 4: Configure virtual networks
1 of 15
08/03/2013 17:06
http://technet.microsoft.com/en-us/library/cc732470(v=ws.10).aspx
Hyper-V has specific requirements. Hyper-V requires an x64-based processor, hardware-assisted virtualization, and hardware data execution prevention (DEP). Hyper-V is available in x64-based versions of Windows Server 2008specifically, the x64-based versions of Windows Server 2008 Standard, Windows Server 2008 Enterprise, and Windows Server 2008 Datacenter. For more information about the requirements, see the Hyper-V installation prerequisites (http://go.microsoft.com/fwlink/?LinkId=122183).
Known issues
Known issues are described in the release notes. We recommend that you review the release notes before you install Hyper-V. To download the Hyper-V release notes, see http://go.microsoft.com /fwlink/?LinkId=98821. The release notes are also available in the Windows Server 2008 Technical Library (http://go.microsoft.com /fwlink/?LinkId=102060).
Note If your computer is running Windows Server 2008, verify that your computer has been updated with the release version of Hyper-V before you install Hyper-V. If your computer is running Windows Server 2008 R2, skip this step. The release version (RTM) of Windows Server 2008 included the pre-release version of Hyper-V. The release version of Hyper-V is offered through Windows Update as a recommended update, Hyper-V Update for Windows Server 2008 x64 Edition (KB950050). However, you also can obtain the update through the Microsoft Download Center. To download this update, see http://go.microsoft.com/fwlink/?LinkId=123539. To determine whether the update has been applied to your computer, do one of the following: On a full installation of Windows Server 2008, click Start, click Windows Update, click View update history, and then click Installed Updates. On a Server Core installation, at the command prompt, type: wmic qfe list Look for update number kbid=950050, which indicates that the update for Hyper-V has been installed.
2 of 15
08/03/2013 17:06
http://technet.microsoft.com/en-us/library/cc732470(v=ws.10).aspx
You can install Hyper-V on either a full installation or a Server Core installation. You can use Server Manager to install Hyper-V on a full installation, as described in the following procedure. To install on a Server Core installation, you must perform the installation from a command prompt. Run the following command: Start /w ocsetup Microsoft-Hyper-V
Note To manage Hyper-V on a Server Core installation, you can use the Hyper-V management tools to manage the server remotely. The management tools are available for Windows Server 2008 and Windows Vista Service Pack 1. For more information, see article 950050 (http://go.microsoft.com/fwlink/?LinkId=122188) and article 952627 (http://go.microsoft.com/fwlink/?LinkId=122189) in the Microsoft Knowledge Base.
3 of 15
08/03/2013 17:06
http://technet.microsoft.com/en-us/library/cc732470(v=ws.10).aspx
1. Click Start, and then click Server Manager. 2. In the Roles Summary area of the Server Manager main window, click Add Roles. 3. On the Select Server Roles page, click Hyper-V. 4. On the Create Virtual Networks page, click one or more network adapters if you want to make their network connection available to virtual machines.
Note The type of network you can create in this step is called an external virtual network. If you create it now you can connect the virtual machine to it when you create the virtual machine in Step 2. To create virtual networks later or reconfigure existing networks, see Step 4: Configure virtual networks.
5. On the Confirm Installation Selections page, click Install. 6. The computer must be restarted to complete the installation. Click Close to finish the wizard, and then click Yes to restart the computer. 7. After you restart the computer, log on with the same account you used to install the role. After the Resume Configuration Wizard completes the installation, click Close to finish the wizard.
Is the installation media available for the operating system you want to install on the virtual machine? You can use physical media, a remote image server, or an .ISO file. The method you want to use determines how you should configure the virtual machine. How much memory will you allocate to the virtual machine? Where do you want to store the virtual machine and what do
4 of 15
08/03/2013 17:06
http://technet.microsoft.com/en-us/library/cc732470(v=ws.10).aspx
After you create the virtual machine, you can start the virtual machine
5 of 15
08/03/2013 17:06
http://technet.microsoft.com/en-us/library/cc732470(v=ws.10).aspx
You specified the location of the installation media when you created the virtual machine. You are installing an operating system for which integration services are available. For a list of these operating systems, see About Virtual Machines and Guest Operating Systems.
6 of 15
08/03/2013 17:06
http://technet.microsoft.com/en-us/library/cc732470(v=ws.10).aspx
Wizard to start the installation. If Autorun does not start the installation automatically, you can start it manually. Click anywhere in the guest operating system window and navigate to the CD drive. Use the method that is appropriate for the guest operating system to start the installation package from the CD drive.
After you have completed the setup and integration services are installed, you can begin using the virtual machine. You can view or modify the virtual hardware that is configured for the virtual machine by reviewing the settings of the virtual machine. From the Virtual Machines pane, right-click the name of the virtual machine that you created in step 3 and click Settings. From the Settings window, click the name of the hardware to view or change it. For more information, see Configuring Virtual Machines (http://go.microsoft.com/fwlink /?LinkId=122190).
1. An external network, which provides communication between a virtual machine and a physical network by creating an association to a physical network adapter on the virtualization server. 2. An internal network, which provides communication between the virtualization server and virtual machines. 3. A private network, which provides communication between virtual machines only.
The following procedures provide the basic instructions for configuring virtual networks. For more information about designing and deploying virtual networks, see Configuring Virtual Networks.
7 of 15
08/03/2013 17:06
http://technet.microsoft.com/en-us/library/cc732470(v=ws.10).aspx
you want to create. The types of network are External, Internal, and Private. If the network you want to create is an external network, see Additional considerations below. 4. Click Add. The New Virtual Network page appears. 5. Type a name for the new network. Review the other properties and modify them if necessary.
Note You can use virtual LAN identification as a way to isolate network traffic. However, this type of configuration must be supported by the physical network adapter. For information about configuring virtual LAN identification, see Configuring virtual local area networks in Configuring Virtual Networks.
6. Click OK to create the virtual network and close Virtual Network Manager, or click Apply to create the virtual network and continue using Virtual Network Manager.
8 of 15
08/03/2013 17:06
http://technet.microsoft.com/en-us/library/cc732470(v=ws.10).aspx
9. Click OK.
Additional considerations
By default, membership in the local Administrators group, or equivalent, is the minimum required to complete this procedure. However, an administrator can use Authorization Manager to modify the authorization policy so that a user or group of users can complete this procedure. A legacy network adapter works without installing a virtual machine driver because the driver is already available on most operating systems. The legacy network adapter emulates a physical network adapter, multiport DEC 21140 10/100TX 100 MB. A legacy network adapter also supports network-based installations because it includes the ability to boot to the Pre-Boot Execution Environment (PXE). The legacy network adapter is not supported in the 64-bit edition of Windows Server 2003 or the Windows XP Professional x64 Edition. When you create an external virtual network, it affects how networking is configured on the physical network adapter. After installation, the management operating system uses a virtual network adapter to connect to the physical network. (The management operating system runs the Hyper-V role.) When you look at Network Connections in the management operating system, you will see the original network adapter and a new virtual network adapter. The original physical network adapter has nothing bound to it except the Microsoft Virtual Network Switch Protocol, and the virtual network adapter now has all of the standard protocols and services bound to it. The virtual network adapter that appears under Network Connections will have the same name as the virtual network with which it is associated. It is possible to create an internal virtual network, which will expose a virtual network adapter to the parent partition without the need to have a physical network adapter associated with it. Hyper-V only binds the virtual network service to a physical network adapter when an external virtual network is created. However, networking will get disrupted for a short period of time on the network adapter when a virtual network gets created or deleted.
Community Additions
9 of 15
08/03/2013 17:06
http://technet.microsoft.com/en-us/library/cc732470(v=ws.10).aspx
Server Administration Tools: Server Manager Role Administration Tools: Active Directory Certificate Services (AD CS) Tools Active Directory Domain Services (AD DS) Tools Active Directory Lightweight Directory Services (AD LDS) Tools DHCP Server Tools DNS Server Tools File Services Tools Hyper-V Tools Terminal Services Tools Feature Administration Tools: BitLocker Password Recovery Viewer Failover Clustering Tools Group Policy Management Tools Network Load Balancing Tools SMTP Server Tools Storage Explorer Tools Storage Manager for SANs Tools Windows System Resource Manager Tools
10 of 15
08/03/2013 17:06
http://technet.microsoft.com/en-us/library/cc732470(v=ws.10).aspx
http://www.microsoft.com/downloads /details.aspx?FamilyID=f6c62797-791c-48e3-b754-c7c0a09f32f3
Go to http://www.windowsservercatalog.com/ . Select the Certified Servers on the right hand side. Select Windows Server 2008 (x64) on the left hand side. Select Hyper-V on the left hand side.
Joeelway's blog links to a handy Hyper-V RAM Calculator you can use to plan your Hyper-V deployment: http://cid2095eac3772c41db.skydrive.live.com/self.aspx/Public/HyperV%20RAM%20Calculator.xls
The Performance Tuning Guidelines for Windows Server 2008 has been updated to include perf guidelines for virtualization servers: http://www.microsoft.com/whdc/system/sysperf/Perf_tun_srv.mspx
For example:
For better performance, use all logical processors (up to 16) if the number of active virtual processors matches that of logical processors to help reduce the rate of context switching between virtual processors.
11 of 15
08/03/2013 17:06
http://technet.microsoft.com/en-us/library/cc732470(v=ws.10).aspx
Set your processor cache as high as possible for loads that have a large working set in memory and in VM configurations in which the ratio of virtual processors to logical processors is high. More memory is better, usually (no surprise). The "virtualization host" server requires sufficient memory for the root and child partitions. HyperV first allocates the memory for child partitions, which should be sized based on the needs of the expected server load for each VM. The root partition should have sufficient available memory to efficiently perform I/Os on behalf of the VMs and operations such as a VM snapshot. YMV, so use the planning toolkits and pilot testing to find your optimum setting. Multiple network adapters or multiport network adapters are a good idea, both for network-intensive VM workloads, and management. VMs can be distributed among the adapters for better overall performance. To reduce the CPU usage of network I/Os from VMs, HyperV can use hardware offloads such as Large Send Offload (LSOv1) and TCPv4 checksum offload. For details on network hardware considerations, see Performance Tuning for Networking Subsystem earlier in the Performance Tuning Guidelines for Windows Server 2008 guide. Ensure your storage hardware has I/O bandwidth and capacity to meet current and future needs of the VMs. Consider Placing VMs with highly disk-intensive workloads on different physical disks will likely improve overall performance. For example, if four VMs share a single disk and actively use it, each VM can yield only 25 percent of the bandwidth of that disk. For details on storage hardware considerations and discussion on sizing and RAID selection, see Performance Tuning for Storage Subsystem earlier in the Performance Tuning Guidelines for Windows Server 2008 guide.
For some insight into how Microsoft IT uses virtualization (they use SANs for disk storage) listen to the David Lef podcast on How Microsoft IT Uses Hyper-V: http://download.microsoft.com/download/0/c/5 /0c5d7ca4-35d2-45ae-ac47-f83b6d774fa0/DavidLefPodcast.wma
kingpong1 1/6/2011
12 of 15
08/03/2013 17:06
http://technet.microsoft.com/en-us/library/cc732470(v=ws.10).aspx
That being said, the Beta of Microsoft Hyper-V Server 2008 R2 is now available at: http://www.microsoft.com/downloads /details.aspx?FamilyID=e464e255-cdd5-44b2-84e6-3233eae3f356
demartest 11/30/2010
Hyper-V How To: Configure Operations Manager Integration with VMM 2008
This topic explains how to configure integration of System Center Operations Manager 2007 with System Center Virtual Machine Manager 2008 (VMM) to support the following features of VMM:
Health monitoring of virtual machines, hosts, and other VMM components through Operations Manager 2007 Performance and Resource Optimization (PRO) Diagram view in the VMM Administrator Console
http://technet.microsoft.com/en-us/library/cc956099.aspx
venkat2k 4/30/2010
Things to Know About This Release Candidate of Windows Server 2008 R2 include: If you export a virtual machine that is in a saved state and then import it, the original virtual machine will lose network connectivity. To avoid this, ensure that any virtual machine is in the Off state before you export it. After importing the virtual machine, set it to use static MAC addresses, and then reset it to use dynamic MAC addresses before you start the virtual machine. If you have snapshots in the imported virtual machine, turn off the virtual machine after you apply the snapshot, and then repeat the above steps. If this has already occurred, turn off the newly imported virtual machine
13 of 15
08/03/2013 17:06
http://technet.microsoft.com/en-us/library/cc732470(v=ws.10).aspx
and repeat the steps above. And, from marketing: Windows Server 2008 R2 also holds the much-anticipated update to Microsofts virtualization technology, Hyper-V. The new Hyper-V was designed to augment both existing virtual machine management as well as to address specific IT challenges, especially around server migration. Hyper-V is an enabling technology for one of Windows Server 2008 R2s marquee features, Live Migration. With Hyper-V version 1.0, Windows Server 2008 was capable of Quick Migration, which could move VMs between physical hosts with only a few seconds of down-time. Still, those few seconds were enough to cause difficulties in certain scenarios, especially those including client connections to VM-hosted servers. With Live Migration, moves between physical targets happen in milliseconds, which means migration operations become invisible to connected users. Customers employing System Center Virtual Machine Manager for Hyper-V will also enjoy additional management and orchestration scenarios, including a new VM-oriented Performance and Resource Optimization feature and updated support for managing failover clusters. The new Hyper-V also has core performance enhancements, including the previously mentioned ability to take advantage of 32 logical processors on the host and to beef up that CPU performance with host support for Second Level Translation (SLAT). Finally, VMs can also add and remove VHD disks without requiring a reboot and also boot from VHD as well. Aaaand: PowerShell 2.0 also has a deeper reach than its predecessor, with enhanced support available on both Windows 7 and the Server Core role (which previously could not run PowerShell).
jribeauv 4/20/2010
Lynn Lunik Independent Security Consultant Windows(R) Platform IT Pro Secure Corporation and
14 of 15
08/03/2013 17:06
http://technet.microsoft.com/en-us/library/cc732470(v=ws.10).aspx
magyar2 11/19/2009
http://itprosecure.com/blogs/hyper-v_administration/archive/2008/09 /10/introducing-the-basics-of-the-hyper-v-administrative-interface.aspx
Lynn Lunik Independent Security Consultant Windows(R) Platform IT Pro Secure Corporation and exchangesummit.net http://itprosecure.com and http://www.exchangesummit.net blog <at> itprosecure.com
Lynn_Lunik 7/30/2009
15 of 15
08/03/2013 17:06