1 of 9 4/27/ :45 AM

Transcription

1 1 of 9 4/27/ :45 AM 2010 Microsoft Corporation. All rights reserved. Updated: July 1, 2009 Applies To: Windows Server 2008 Hyper-V is a role in Windows Server 2008 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 allows 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. 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 operating system and integration services Step 4: Configuring virtual networks Requirements for Hyper-V 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 2008 specifically, 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 ( [ /?LinkId= ] ). 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 [ /fwlink/?linkid=98821 ]. The release notes are also available in the Windows Server 2008 Technical Library ( [ ] ). Step 1: Install Hyper-V Before you install Hyper-V, verify that your computer has been updated with the release version of Hyper-V. 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 [ /fwlink/?linkid= ]. 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

2 2 of 9 4/27/ :45 AM Look for update number kbid=950050, which indicates that the update for Hyper-V has been installed. 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 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 For more information, see article ( [ ] ) and article ( /?LinkId= [ ] ) in the Microsoft Knowledge Base. To install Hyper-V on a full installation of Windows Server 2008 Click Start, and then click Server Manager. In the Roles Summary area of the Server Manager main window, click Add Roles. 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. 5. On the Confirm Installation Selections page, click Install The computer must be restarted to complete the installation. Click Close to finish the wizard, and then click Yes to restart the computer. 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. Step 2: Create and set up a virtual machine After you have installed Hyper-V, you can create a virtual machine and set up an operating system on the virtual machine. Before you create the virtual machine, you may find it helpful to consider the following questions. You can provide answers to the questions when you use the New Virtual Machine Wizard to create the virtual machine. 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 you want to name it? To create and set up a virtual machine 4. Open Hyper-V Manager. Click Start, point to Administrative Tools, and then click Hyper-V Manager. From the Action pane, click New, and then click Virtual Machine. From the New Virtual Machine Wizard, click Next. On the Specify Name and Location page, specify what you want to name the virtual machine and where you

3 3 of 9 4/27/ :45 AM want to store it. On the Memory page, specify enough memory to run the guest operating system you want to use on the virtual machine. On the Networking page, connect the network adapter to an existing virtual network if you want to establish network connectivity at this point. If you want to use a remote image server to install an operating system on your test virtual machine, select the external network. On the Connect Virtual Hard Disk page, specify a name, location, and size to create a virtual hard disk so you can install an operating system on it. 8. On the Installation Options page, choose the method you want to use to install the operating system: Install an operating system from a boot CD/DVD-ROM. You can use either physical media or an image file (.iso file). Install an operating system from a boot floppy disk. Install an operating system from a network-based installation server. To use this option, you must configure the virtual machine with a legacy network adapter connected to an external virtual network. The external virtual network must have access to the same network as the image server. 9. Click Finish. After you create the virtual machine, you can start the virtual machine and install the operating system. Step 3: Install the operating system and integration services In the final step of this process, you connect to the virtual machine to set up the operating system. As part of the setup, you install a software package that improves integration between the virtualization server and the virtual machine. The instructions in this step assume that you specified the location of the installation media when you created the virtual machine. The instructions also assume that you are installing an operating system for which integration services are available. To install the operating system and integration services From the Virtual Machines section of the results pane, right-click the name of the virtual machine you created in step 2 and click Connect. The Virtual Machine Connection tool will open. From the Action menu in the Virtual Machine Connection window, click Start. Proceed through the installation. s When you are at the point where you need to provide input to complete the process, move the mouse cursor over the image of the setup window. After the mouse pointer changes to a small dot, click anywhere in the virtual machine window. This action "captures" the mouse so that keyboard and mouse input is sent to the virtual machine. To return the input to the physical computer, press Ctrl+Alt+Left arrow and then move the mouse pointer outside of the virtual machine window. After the operating system is set up, you are ready to install the integration services. From the Action menu of Virtual Machine Connection, click Insert Integration Services Setup Disk. On

4 4 of 9 4/27/ :45 AM Windows operating systems, you must close the New Hardware 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 ( [ ] ). Step 4: Configuring virtual networks You can create virtual networks on the server running Hyper-V to define various networking topologies for virtual machines and the virtualization server. There are three types of virtual networks: a private network, which provides communication between virtual machines only, an internal network, which provides communication between the virtualization server and virtual machines, and 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. The following procedures provide the basic instructions for configuring virtual networks. For more information about designing and deploying virtual networks, see the deployment content for Hyper-V at the Windows Server 2008 TechCenter ( [ ] ). To create a virtual network Open Hyper-V Manager. From the Actions menu, click Virtual Network Manager. Under Create virtual network, select the type of network 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 Click Add. The New Virtual Network page appears. Type a name for the new network. Review the other properties and modify them if necessary. 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 the Hyper-V deployment content at the Windows Server 2008 TechCenter ( [ ] ). 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. To add a network adapter to a virtual machine 4. Open Hyper-V Manager. Click Start, point to Administrative Tools, and then click Hyper-V Manager. In the results pane, under Virtual Machines, select the virtual machine that you want to configure. In the Action pane, under the virtual machine name, click Settings. In the navigation pane, click Add Hardware. 5. On the Add Hardware page, choose a network adapter or a legacy network adapter. Network adapters can only be added to a virtual machine when the machine is turned off. For more information about each type of adapter, see "Additional considerations" below Click Add. The Network Adapter or Legacy Network Adapter page appears. Under Network, select the virtual network you want to connect to.

5 5 of 9 4/27/ :45 AM 8. If you want to configure a static MAC address or virtual LAN identifier, specify the address or identifier you want to use. 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 /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. After you install Hyper-V and create an external virtual network, your computer will operate differently. After installation, the parent partition uses a virtual network adapter to connect to the physical network. When you look at Network Connections on the parent partition, 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 switch 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. Tags: Community Content The RC of the next version of Hyper-V is available to download Last Edit 12:02 PM by jribeauv [ /windowsserver2008/en/us/r2-download.aspx ] 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 and repeat the steps above. And, from marketing: Windows Server 2008 R2 also holds the much-anticipated update to Microsoft s 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 R2 s marquee features, Live Migration. With Hyper-V version 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

6 6 of 9 4/27/ :45 AM 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 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). Tags: powershell virtualization hyper-v hyperv r2 Free Microsoft Hyper-V Server 2008 R2 Beta Last Edit 4:45 AM by Brian Rosales Microsoft Hyper-V Server 2008 is the free virtualization server OS from Microsoft. It is NOT Windows Server 2008 Hyper-V. To understand the (important) differences, see /default.mspx [ ]. That being said, the Beta of Microsoft Hyper-V Server 2008 R2 is now available at: /downloads/details.aspx?familyid=e464e255-cdd5-44b2-84e6-3233eae3f356 [ /downloads/details.aspx?familyid=e464e255-cdd5-44b2-84e6-3233eae3f356 ] Tags: virtualization hyper-v hyperv hyper-vserver Getting to Know Hyper-V Video Last Edit 1:17 AM by N9064L In this 12 minute video Windows Server UA Technical Writer Felipe Ayora shares his experiences getting to know Hyper-V while setting up HPC clusters for his technical writing assignments: /en/us/details/806bb329-55a0-4be2-89d2-bb5e8d7dd808 [ /806bb329-55a0-4be2-89d2-bb5e8d7dd808 ] Tags: virtualization Hyper-V: Configuration Steps - Exporting a Guest Partition Last Edit 10:15 PM by magyar Hyper-V: Configuration Steps - Exporting a Guest Partition- for SCREEN CAPTURES go to IT Pro Secure Corporation blog - [ /archive/2009/01/19/hyper-v-configuration-steps-exporting-a-guest-partition.aspx ] Lynn Lunik Independent Security Consultant Windows(R) Platform IT Pro Secure Corporation and exchangesummit.net and blog <at> itprosecure.com Tags: contentbug hyper-v

7 7 of 9 4/27/ :45 AM Reviewing the Basics of the Hyper-V Administrative Interface Last Edit 12:31 PM by Lynn_Lunik Reviewing the Basics of the Hyper-V Administrative Interface - for SCREEN CAPTURES go to IT Pro Secure Corporation blog - [ /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 and blog <at> itprosecure.com Tags: contentbug interface hyper-v administrative Microsoft Server Virtualization Resources Last Edit 11:42 AM by Thomas Lee Adam's blog post has an excellent up-to-date compliation of virtualization planning resources for WinServ and Hyper-V. [ ] Tags: virtualization hyper-v hyperv Hyper-V How To: Configue Operations Manager Integration with VMM 2008 Last Edit 11:42 AM by Thomas Lee 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 [ /cc aspx ] Tags: virtualization hyper-v scom hyperv vmm RSAT for Windows 7 RC released Last Edit 11:41 AM by Thomas Lee [ ] Server Administration Tools: Server Manager Role Administration Tools: Active Directory Certificate Services (AD CS) Tools Active Directory Domain Services (AD DS) Tools

8 8 of 9 4/27/ :45 AM 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 [ ] Tags: contentbug virtualization hyper-v hyperv r2 rsat Performance Tuning Guidelines for Windows Server 2008: Hyper-V Last Edit 4:32 PM by tonysoper To find the list of supported server configs: Go to 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: [ eac3772c41db.skydrive.live.com/self.aspx/Public/Hyper-V%20RAM%20Calculator.xls ] The Performance Tuning Guidelines for Windows Server 2008 has been updated to include perf guidelines for virtualization servers: [ ] 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. 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. Hyper V 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, Hyper V 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

9 9 of 9 4/27/ :45 AM 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: [ ] Tags: contentbug deployment windows virtualization server performance tuning hyper-v