Implementing Microsoft Windows Server 2008 R2 Hyper-V and Microsoft Hyper-V Server 2008 R2 on HP ProLiant servers

integration note
Abstract.............................................................................................................................................. 2 Terminology .................................................................................................................................... 2 Comparing Microsoft Hyper-V enabled products ..................................................................................... 2 Overview of Hyper-V Server 2008 R2.................................................................................................... 3 Obtaining Hyper-V Server 2008 R2 ................................................................................................... 4 Overview of Windows Server 2008 R2 Hyper-V ..................................................................................... 4 Obtaining Windows Server 2008 R2 Hyper-V .................................................................................... 5 Updating Hyper-V installations .............................................................................................................. 5 Configuration requirements ................................................................................................................... 5 Recommended system configurations.................................................................................................. 5 Microsoft recommendations ........................................................................................................... 5 HP recommendations .................................................................................................................... 6 Processor requirements.................................................................................................................. 7 HP ProLiant support of Hyper-V .......................................................................................................... 7 Supported ProLiant components ....................................................................................................... 10 Software ................................................................................................................................... 10 Storage options.......................................................................................................................... 10 Network interface controllers ....................................................................................................... 12 Deploying Windows Server 2008 R2 Hyper-V on ProLiant servers ........................................................... 13 Enabling support for hardware-assisted virtualization in the RBSU ........................................................ 14 ProLiant servers with Intel processors............................................................................................. 14 ProLiant servers with AMD processors ........................................................................................... 15 Installing Windows Server 2008 R2................................................................................................. 16 HP ProLiant Support Pack (PSP) ........................................................................................................ 17 PSP requirements ........................................................................................................................ 17 Installing the PSP ........................................................................................................................ 17 Installing the Windows Server 2008 R2 Hyper-V server role................................................................ 19 Deploying Hyper-V Server 2008 R2 on ProLiant servers ......................................................................... 19 Enabling support for hardware-assisted virtualization in the RBSU ........................................................ 20 ProLiant servers with Intel Processors ............................................................................................. 20 ProLiant servers with AMD processors ........................................................................................... 21 Installing Microsoft Hyper-V Server 2008 R2 ..................................................................................... 22 Installing the PSP ............................................................................................................................ 23 Appendix A: Known issues and workarounds ....................................................................................... 24 For more information.......................................................................................................................... 25 Call to action .................................................................................................................................... 25

Abstract
The purpose of this integration note is to help customers install the following Microsoft hypervisor (Hyper-V) enabled products: Microsoft Windows Server 2008 R2 Hyper-VTM (The Hyper-V server role within Windows Server 2008 R2) Microsoft Hyper-V Server 2008 R2 This integration note describes the level of support available for these Hyper-V enabled products running multiple guest operating systems on a single server and addresses the following key topics: Introduction to Microsoft products that provide Hyper-V functionality Recommended system configurations Hardware prerequisites Supported configurations of HP ProLiant servers Procedures for new installations Known issues and workarounds

Terminology
Administrators who are looking to deploy Hyper-V enabled products should be familiar with the terminology in Table 1.
Table 1. Virtualization terminology Term Child virtual machine Guest operating system Host operating system Parent virtual machine Partition Virtual hard disk Windows hypervisor Description Guest OS running in a separate partition on the host OS OS running on a virtual machine OS on the physical computer running Windows Server 2008 R2 Hyper-V software Physical computer that hosts one or more child virtual machines A virtual machine VHD file that provides storage for the virtual machines Layer of software that leverages the Windows Server driver support and hardware-assisted virtualization technology

Comparing Microsoft Hyper-V enabled products

Administrators want flexibility in allocating compute resources for specific tasks. Windows Server 2008 R2 Hyper-V and Hyper-V Server 2008 R2 include virtualization technologies that provide this flexibility by decoupling the hardware from the work performed. Figure 1 shows the differences in functionality between Hyper-V Server 2008 R2 and Windows Server 2008 R2 Hyper-V.

Figure 1. Microsoft Hyper-V enabled product comparison

Overview of Hyper-V Server 2008 R2

Hyper-V Server 2008 R2 is a dedicated standalone product and is a virtualization solution designed to improve server utilization and reduce costs. As a server core-based installation, it contains only the Windows Hypervisor, Windows Server driver model, and virtualization components, which leave a small footprint and require minimal overhead. It easily plugs into customers existing IT environments and uses existing patching, provisioning, management, support tools, and processes. Hyper-V Server 2008 R2 is well suited for customers who want a basic virtualization solution to consolidate servers and to develop and test environments. Hyper-V Server 2008 R2 offers the most basic of virtualization features: Test and development

 Basic server or branch office consolidation Hosted desktops by using virtualized desktop infrastructure (VDI)

Obtaining Hyper-V Server 2008 R2

Hyper-V Server 2008 R2 is available as a free download from the Microsoft web site at www.microsoft.com/downloads/details.aspx?FamilyID=48359dd2-1c3d-4506-ae0a232d0314ccf6&displaylang=en.

Overview of Windows Server 2008 R2 Hyper-V

Windows Server 2008 R2 Hyper-V will install as a server role on Standard, Enterprise, and Datacenter edition installations (both full and server core installations). The following editions of Windows Server 2008 R2 do not support the Hyper-V server role: Microsoft Windows Web Server 2008 R2 Foundation Microsoft Windows Server 2008 R2 for Itanium-Based Systems Windows Server 2008 R2 Hyper-V is a robust, scalable hypervisor-based virtualization platform for provisioning and managing virtual server workloads. It includes the following features: Live Migration: Support for transparently moving running virtual machines from one node of a failover cluster to another node in the same cluster without a dropped network connection or downtime. Installation of failover clustering role and Cluster Shared Volumes for storage is required. Dynamic Virtual Machine Storage: Support for the following: Hot removal and hot pluggable storage for Virtual Machines Dynamic (automatic) reallocation of storage resources, which provides administrators flexibility in storage configurations Adding (removing) virtual or physical hard disks to (from) the shared storage

Boot from .VHD support: Allows a physical instance of Windows to boot from a virtual hard drive. Enhanced Processor Support: Support for 32 physical processor cores (64 logical processor cores), second-Level Address Translation (SLAT), and CPU core parking as follows: Second-Level Address Translation (SLAT): SLAT uses a processor capability of newer processors (EPT or NPT) to optimize the second-level address translation that is necessary in a virtual environment; therefore, improving system performance. CPU Core Parking: Enables Windows and Hyper-V to consolidate processing on to the fewest number of possible processor cores, suspending inactive processor cores.

NOTE
Support for a maximum of 64 logical processors in the host processor pool and can be any combination of processors and processor cores.

Enhanced Networking Support: Support for jumbo frames within a virtual environment. This feature enables virtual machines to use jumbo frames up to 9,014 bytes in size if the underlying physical network supports it. Support for VM Chimney (TCP Offloading) is available with Windows Server 2008 R2 HyperV providing overall network throughput performance.

Linux Integration Components: Support for VM configured with one virtual processor and Red Hat Enterprise Linux (RHEL) 5.2 or 5.3 (x86/x64) for emulated devices only, SUSE Linux Enterprise Server (SLES) 10 (x86/x64) with service pack 1 or 2 and SLES 11 (x86/x64). The Linux Integration

components for Hyper-V included with Windows Server 2008 R2 are available from Microsoft: www.microsoft.com/downloads/details.aspx?FamilyID=C299D675-BB9F-41CF-B5EB74D0595CCC5C&displaylang=en. Guest Operating System Support: Support for guest OSs in a Windows Server 2008 R2 Hyper-V or Hyper-V Server 2008 R2 virtual environment is available from Microsoft: www.microsoft.com/windowsserver2008/en/us/hyperv-supported-guest-os.aspx.

Obtaining Windows Server 2008 R2 Hyper-V

Windows Server 2008 R2 Hyper-V is included with the Windows Server 2008 R2 media as a server role that can be installed in both full and server core based installations. Standard, Enterprise, and Datacenter editions of Windows Server 2008 R2 available from HP include support for Hyper-V. For information on Windows Server 2008 R2, refer to the URLs provided in the For more information section at the end of this document.

Updating Hyper-V installations

Microsoft recommends several updates and hot fixes for Hyper-V installations. Download and installation information for software updates is available at http://technet.microsoft.com/enus/library/dd430893.aspx.

Configuration requirements
Hyper-V uses a hardware-assisted feature built into Intel and AMD processors. On Intel-based ProLiant servers, this feature is called Intel Virtualization Technology (Intel-VT). On Advanced Micro Devices (AMD)-based ProLiant servers, this feature is called AMD Virtualization (AMD-V) Technology. On ProLiant servers, the user must enable this feature before installing Hyper-V. Refer to the section Enabling support for hardware-assisted virtualization in the ROM-Based Setup Utility (RBSU) in this document.

Recommended system configurations

Microsoft and HP established the recommended system configurations for Windows Server 2008 OS installations listed in this section. Microsoft recommendations Microsoft recommends the configurations in Table 2 for running Windows Server 2008 R2 Hyper-V or Hyper-V Server 2008 R2.
Table 2. Host OS configuration recommended by Microsoft Component Processor speed Requirement Minimum 1.4 GHz RAM per processor Minimum Recommended 2 GHz Recommended Optimum 3 GHz (or greater) Optimum

Table 2. Host OS configuration recommended by Microsoft Component Requirement 512 MB 2 GB 2 GB (full) -Or1 GB (core) Maximum RAM 64-bit systems* Hyper-V Server 2008 R2 Standard Enterprise -OrDatacenter 32 GB Monitor Optical storage Available disk space** 32 GB 2 TB

SVGA resolution (800x600) or higher DVD drive Minimum 10 GB Recommended 40 GB (or greater)

*Computers with more than 16 GB of RAM will require more disk space for paging and dump files. **Available disk space refers to the free disk space on the partition to contain the system files. Additional space is required if the Windows Server 2008 R2 CD contents are copied to the hard disk during installation.

HP recommendations HP recommends the configurations in Table 3 for running Windows Server 2008 Hyper-V as the parent virtual machine.
Table 3. HP configuration recommendations for running the parent virtual machine Component Requirement Minimum Processor dual-core, 1.6 GHz Recommended dual-core, 2.66 GHz 2 GB Optimum two quad-core, 3 GHz (or faster) 3 GB

RAM per processor core 512 MB Disk subsystem

One physical disk

for host OS

One redundant disk

for host OS

One redundant disk for host

OS

One additional

disk per guest OS

One additional

redundant disk per two guest OSs

One additional redundant

disk for snapshots

One additional redundant

disk per two guest OSs

NICs

One NIC for host OS One NIC for host OS Not applicable Management management and guest virtual One NIC for guest networking virtual networking

Processor requirements Microsoft provides virtualization functionality in Windows Server 2008 R2 x64 Standard, Enterprise, or Datacenter Edition for systems with the following processors: Intel Xeon processors with Intel Extended Memory 64 Technology (EM64T) AMD64 Opteron Series processors Table 4 lists the processor requirements for Hyper-V.
Table 4. Processor requirements for Hyper-V Component Processor Requirement AMD-V technology processors Intel-VT processors RAM per processor Minimum 1 GB Hardware Data Execution Prevention Enabled Recommended 2 GB Optimal 4 GB

Hyper-V R2 supports 64 logical processor cores. A maximum of four virtual processors can be assigned to a single guest OS. For steps on how to enable hardware data execution prevention and virtualization in the HP ROM, refer to the installation instruction section of this integration note.

HP ProLiant support of Hyper-V

Due to hardware requirements, not every ProLiant server platform supports Hyper-V. Windows Server 2008 R2 Hyper-V and Hyper-V Server 2008 R2 should successfully install and run on any correctly configured ProLiant server listed in Table 5. Carefully review this document for the recommended system configuration and possible issues, but do not use this document as your sole source of information. Table 5 lists the ProLiant servers with processors that support hardware-assisted virtualization and the minimum ROM revision required to support Hyper-V. HP highly recommends that administrators review the information in Table 5 before attempting to install Windows Server 2008 R2 Hyper-V or Hyper-V Server 2008 R2.
Table 5. ProLiant server platforms that support Hyper-V Server platform ProLiant BL servers: BL2x220c G5 BL260c G5 BL280c G6 BL460c BL460c G5 I19 I20 I22 I15 I23 05/12/09 07/10/09 07/24/09 08/21/07 05/12/09 ROM family ROM date (minimum)

Table 5. ProLiant server platforms that support Hyper-V Server platform BL460c G6 BL465c BL465c G5 BL465c G6 BL480c BL490c G6 BL495c G5 BL495c G6 BL680c G5 BL685c BL685c G5 BL685c G6 ProLiant DL servers: DL120 G5 DL160 G5 DL160 G6 DL160se G6 DL165 G5 DL165 G6 DL170h G6 DL180 G5 DL180 G6 DL320 G6 DL360 G5 DL360 G6 DL365 G5 O22 DL160G5 O33 O20 O13 2009.05.18 O34 DL180G5 O20 W07 P58 P64 A10 07/22/09 1/13/09 07/24/09 07/24/09 07/02/09 05/18/09 07/13/09 03/13/09 07/23/09 07/24/09 07/10/09 07/24/09 07/17/09 ROM family I24 A13 A13 A13 I14 I21 A14 A14 I17 A08 A08 A17 ROM date (minimum) 07/24/09 07/27/09 07/27/09 05/27/09 07/10/09 07/24/09 07/27/09 05/07/09 05/10/09 07/20/09 07/20/09 07/29/09

Table 5. ProLiant server platforms that support Hyper-V Server platform DL370 G6 DL380 G5 DL380 G6 DL385 G2 DL385 G5 DL385 G5p DL580 G5 DL585 G2 DL585 G5 DL785 G5 DL785 G6 ProLiant ML servers: ML110 G5 ML115 G5 ML150 G5 ML150 G6 ML310G5p ML330 G6 ML350 G5 ML350 G6 ML370 G5 ML370 G6 SL160z G6 SL170z G6 ZL2x170z G6 O15 O18 O17 O21 W08 W07 D21 D22 P57 P63 O33 O34 O34 07/13/09 07/06/09 07/06/09 07/06/09 07/10/09 07/24/09 07/10/09 07/24/09 07/10/09 07/24/09 07/24/09 07/13/09 07/13/09 ROM family P63 P56 P62 A09 A09 A22 P61 A07 A07 A15 A15 ROM date (minimum) 07/24/09 07/10/09 07/24/09 07/10/09 07/10/09 07/10/09 05/09/09 07/27/09 07/27/09 08/14/09 08/14/09

NOTE
The ROM versions indicated in Table 5 are the minimum required for support. HP recommends downloading the current ROM release and applying the latest updates to the ProLiant server. HP continually adds support for new servers. To see the most current list of supported servers, visit www.hp.com/go/windowscert.

Supported ProLiant components

Software HP recommends using the drivers on the Windows Server 2008 R2 media for Windows Server 2008 R2 Hyper-V. Before installing the Windows Server 2008 R2 Hyper-V server role, install the HP ProLiant Support Pack for Windows Server 2008 R2 that is included with SmartStart 8.30 (or later). HP does not support installing the Support Pack on a Windows Server 2008 R2 server running as a guest OS within Windows Server 2008 R2 Hyper-V.
NOTE
ProLiant 100 series servers do not use the ProLiant Support Pack. For supported 100 series servers, please use the Driver Support CD that came with the server or the HP website to install and update drivers.

Storage options Table 6 lists supported ProLiant storage options and recommended driver revisions needed to interface with Windows Server 2008 R2. HP has updated the ProLiant Support Pack 8.30 for Windows Server 2008 R2 with the latest drivers.
Table 6. Supported ProLiant storage controller options Option Driver Location Web Download Windows Media PSP 8.30 Management drivers: SAS/SATA Notification Service StorageWorks Fibre Channel Array Notification Driver for Windows 2000/Server 2003 6-Port SATA RAID Controller Internal 4/8 Port SAS HBA Smart Array: E200 E200I HPSAMD.SYS (basic) CISSESRV.EXE CPQFCAC.SYS

AAC.SYS LSI_SAS.SYS

10

Table 6. Supported ProLiant storage controller options Option Driver Location Web Download Windows Media PSP 8.30 E500 P212 P400 P400i P410 P410I P411 P600 P700M P800 Ultra 320 SCSI: Integrated Dual Channel Ultra320 SCSI Controller 64-bit/13-MHz Single Channel Ultra320 SCSI Host Bus Adapter 64-bit/13-MHz Dual Channel Ultra320 SCSI Host Bus Adapter Broadcom Serial ATA Controller Driver: HT1000 Fibre Channel Host Bus Adapters: Qlogic: 81Q PCI-e 82Q PCI-e Dual Port FC1142SR / FC1242SR FC1143 / FC1243 QMH2462 4Gb QMH2562 8Gb Emulex: 81E PCI-e 82E PCI-e FC2143 / FC2243 FC2142SR / FC2242SR Lpe1105 c-Class mezz Lpe1205 c-Class mezz ELXSTOR.SYS QL2300.SYS BCHTSW64.SYS SYMMPI.SYS HPCISSS2.SYS (full featured)

11

Table 6. Supported ProLiant storage controller options Option Driver Location Web Download Windows Media PSP 8.30 StorageWorks: DAT Autoloader 72x6 DAT Autoloader 72x10
HPDAT.SYS HPDATCHG.SYS

NOTE: Some devices have firmware upgrades available through variations of the Options ROMPaq. The latest version of each Options ROMPaq is available on the software and drivers website: http://h20000.www2.hp.com/bizsupport/TechSupport/ProductRoot.jsp?lang=en&cc=us&taskId=135.

NOTE
For detailed information about Storage Array Network (SAN) components, supported host bus adapters, switches, and other components, go to the Single Point Of Connectivity Knowledge (SPOCK) website at http://www.hp.com/storage/spock.

Network interface controllers Table 7 lists ProLiant NICs supported by Windows Server 2008. All NIC drivers are available on the Windows Server 2008 ProLiant Support Pack and have a digital signature. HP-branded drivers are not available on the Windows Server 2008 R2 media. NIC drivers from Intel and Broadcom install by default during Windows Server 2008 R2 installation.
Table 7. Supported ProLiant network interface controller options Gigabit NIC Driver Download NC1020 NC105T NC107T NC150T NC320T NC320M NC324 M NC325 M NC326 M NC7761 NC7771 NC7781 NC7782 NC6170 NC7170 NC310F NC340T n1g6032e. sys b57nd60a. sys Location Windows Media PSP 8.30

12

Table 7. Supported ProLiant network interface controller options Gigabit NIC Driver Download NC110T NC360M NC360T NC364T NC364M NC112T NC362I NC370T/F/I NC371I NC373T/F/M/I NC374M NC380T NC382I/T NC375I NC522 NC524 hpnd6x64. sys bxvbda.sys e1q62x64.sys e1e6232e. sys Location Windows Media PSP 8.30

NOTE
HP ProLiant Network Teaming Software (HP Network Configuration Utility (NCU) version 9.35 [or greater]) supports NIC teaming for Hyper-V. It is included with HP ProLiant Support Pack (PSP) 8.30 on the HP SmartStart CD. It is also available as a download from the following URL: http://www.hp.com. For more information on HP ProLiant Network Adapter Teaming, refer to the For More Information section at the end of this document.

Deploying Windows Server 2008 R2 Hyper-V on ProLiant servers

Windows Server 2008 R2 Hyper-V requires manual installation after successfully installing Windows Server 2008 R2.
IMPORTANT
The procedures in this integration note are for installing Windows Server 2008 R2 Hyper-V with a full Windows Server 2008 R2 installation. For instructions on performing an installation using server core, go to http://technet.microsoft.com/en-us/library/cc753802.aspx.

13

To install Windows Server 2008 R2 Hyper-V on a ProLiant server, do the following: Make sure that the server selected for installation is listed in Table 5 and has the necessary support for hardware-assisted virtualization. Make sure that any additional storage options added to the server are supported ProLiant storage options. Make sure that NICs added to the server are supported ProLiant Gigabit Ethernet NICs. Go to the support and drivers page at www.hp.com/support to obtain the supported ROM for Windows Server 2008 R2 installations for the server. Make sure that Microsoft Windows Server 2008 R2 has been installed using the procedure outlined in the document Implementing Microsoft Windows Server 2008 on HP ProLiant servers. 1 If necessary, enable support for No-Execute and hardware-assisted virtualization in the RBSU. Use the RBSU to set date and time and to configure the boot controller order (if necessary). Use the Online RAID Configuration Utility (ORCA) to configure the RAID settings for the server. If installing HP Systems Insight Manager and agents, make sure that SNMP is loaded and the service is started.

Enabling support for hardware-assisted virtualization in the RBSU

Windows Server 2008 R2 Hyper-V uses an advanced processor feature known as hardware-assisted virtualization. In most ProLiant servers, this feature is disabled by default and must be enabled prior to installing Windows Server 2008 R2 Hyper-V. Enable hardware-assisted virtualization by following the appropriate procedure in the following sections. ProLiant servers with Intel processors To enable support for hardware-assisted virtualization in the RBSU, complete the following steps:
1. Restart or power-on the server. 2. Access the RBSU by pressing F9 when prompted. 3. From the RBSU Menu, select Advanced Options.

4. From the Advanced Options menu, select Processor Options.

The Implementing Microsoft Windows Server 2008 Service Pack 2 Beta on HP ProLiant servers integration note is available at http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00710606/c00710606.pdf.
1

14

5. Select No-Execute Memory Protection, press Enter, and then select Enabled.

6. Select Intel(R) Virtualization Technology, press Enter, and then select Enabled.

7. Press the Esc key until you receive a prompt to press F10 to confirm exiting the RBSU. The server

will perform a restart. ProLiant servers with AMD processors To enable support for hardware-assisted virtualization in the RBSU, complete the following steps:
8. Restart or power-on the server. 9. Access the RBSU by pressing F9 when prompted. 10. From the RBSU Menu, select Advanced Options.

11. From the Advanced Options menu, select Processor Options.

15

12. Select No-Execute Page-Protection, press Enter, and then select Enabled.

13. Select AMD Virtualization, press Enter, and then select Enabled.

14. Press the Esc key until you receive a prompt to press F10 to confirm exiting the RBSU. The server

will perform a restart.

Installing Windows Server 2008 R2

To install Windows Server 2008 R2 edition, complete the following steps:
1. Make sure that the server has a DVD drive (either installed in the server or attached to the server).

- Or Boot the server into Microsoft Windows Preinstall Environment (Windows PE or WINPE) from a USB key. This is possible from across a network using Windows Deployment Services. For details on Booting WINPE, refer to the Windows Automated Installation Kit.

NOTE
iLO virtual media requires a license key with ProLiant ML and DL servers and in certain circumstances with ProLiant BL servers.

2. Place the Windows Server 2008 R2 media into the DVD drive and boot the server from the DVD

to begin the installation.

3. Follow the on-screen instructions to complete the installation.

16

IMPORTANT
The F6 option for updating drivers is not available during the Windows Server 2008 R2 installation. Microsoft has added the option to inject a driver during installation through the Update Driver button if a boot controller driver is not found. The driver may reside on USB media, floppy drive, or CD-ROM drive.

HP ProLiant Support Pack (PSP)

The HP Smart Update Manager (HPSUM) utility lets users deploy PSP software and firmware components from a single, easy-to-use graphical interface. Users can also maintain ProLiant Support Packs and Smart Components on a local server or on one or more remote servers accessible over a network connection. This utility provides legacy support for existing software and firmware components and simplifies the overall deployment process. The utility also checks installation logic and version control for dependencies, and installs only the correct updates for optimal configuration. HPSUM includes the following functions: Detects hardware and software on the server Automatically checks component dependency Detects components that have available updates Allows remote deployment of PSP components Supports command line entry PSP requirements To use Windows Server 2008 PSP Version 8.30 with Windows Server 2008 R2 Hyper-V, the following requirements must be met: Use only with HP ProLiant servers. Use only on the host server for Windows Server 2008 R2 Hyper-V. Do not install the PSP on a guest OS because it is not required or supported. Install the PSP before installing the Windows Server 2008 R2 Hyper-V role to verify proper functionality.
NOTE
ProLiant 100 series servers do not use the ProLiant Support Pack. For ProLiant 100 series drivers go to the associated Support and drivers page at www.hp.com.

To download the PSP Version 8.30 from the HP website, complete the following steps :
1. Go to the HP website at www.hp.com. 2. Select Support & Driver Downloads. 3. Enter the ProLiant server model (for example, ProLiant DL380 G6). 4. Select the appropriate server model from the Product Search List. 5. Select the Microsoft Windows Server 2008 R2 operating system 6. Select Software - Support Pack for the quick jump selection. 7. Select ProLiant Support Pack for Microsoft Windows Server 2008.

Installing the PSP To download the PSP self-extracting executable, complete the following steps:

17

8. Go to the directory that contains the PSP executable. 9. Invoke the executable and extract the PSP to a desired location.

NOTE
When installing the PSP on a system running Server Core, run the executables rather than double-clicking on them. In addition, on server core systems, you cannot specify the location for extracting the PSP files. The files will extract to the same location as the PSP self-extracting executable. You may also use the procedure outlined in the section titled Installing the ProLiant Support Pack in this integration note.

10. Go to the directory where the extracted PSP is located. 11. Invoke setup.exe to start the PSP deployment. 12. As the PSP deployment starts, the Source Selection screen displays and allows you to enter a

directory where the components to be installed are located. You can also specify that you want to get the latest components from ftp.hp.com. Selecting the Start Inventory button performs an inventory of the available updates. local host, a remote host, or multiple hosts for PSP deployment. checked for installed hardware, software, and services.

13. After the inventory process finishes, the Select Installation Hosts screen displays. Select either the 14. After you select the host(s), the discovery process for each selected host occurs. Each system is 15. Once the discovery process has completed, the Select Bundle Filter screen displays information

about the PSP bundle that requires installation. Select the bundle and the appropriate filter options. For remote deployments, additional screens allow you to update information on a per-host basis: Select the components for installation Configure the components, if necessary. Review and address failed dependencies before installation. Review the revision history of the components.

16. After selecting the components to install, click Install to proceed with the installation. Once the

installation completes, the Installation Results screen displays. If the PSP installs successfully, the process is complete.
17. If any components did not install successfully, complete the following steps:

Exit HPSUM. Make corrections to your environment. Restart the application to install the components that had problems.

18

Installing the Windows Server 2008 R2 Hyper-V server role

To install the Windows Server 2008 R2 Hyper-V server role, complete the following steps:
1. Click Add Roles. If this is the first role being added to the server, you may see a page describing

the process for adding roles. Click Next. overview and then click Next.

2. Check the box for Hyper-V and click Next. Review the Windows Server 2008 R2 Hyper-V 3. Choose the NICs to configure as virtual networks for use by guest OSs. Click Next.

IMPORTANT
When the virtual network switch is bound to the NIC, all protocols are removed. Instead of the TCP/IP protocol, the Microsoft Virtual Network Switch Protocol is installed; therefore, all possible open Terminal Server sessions will close. To re-enable the old TCP/IP settings, login to the server locally or through IRC, and then configure the newly created network adapter while using the old TCP/IP configuration.

NOTE
Microsoft recommends keeping one NIC reserved to manage the host operating environment. In scenarios where this is not possible, be advised that network connectivity to the host can be temporarily interrupted during configuration changes to the virtual network.

4. Review the summary installation. Make a note of which NICs require configuration as virtual

networks.
5. When prompted, choose to reboot the server to complete the installation. After the server reboots,

log in as Administrator to finish the installation process.

After adding the Windows Server 2008 R2 Hyper-V role, you can create and configure virtual machines.

Deploying Hyper-V Server 2008 R2 on ProLiant servers

Microsoft Hyper-V Server 2008 R2 is a standalone component. It is not necessary to install Windows Server 2008 R2 before installing Microsoft Hyper-V Server 2008 R2. To prepare for installation, do the following: Make sure that the server selected for installation is included in Table 5 and has the necessary support for hardware-assisted virtualization. Make sure that storage options added to the server are included as supported ProLiant storage options in Table 6. Make sure that any NICs added to the server are included as supported ProLiant Gigabit Ethernet NICs in Table 7. Go to the support and drivers page at www.hp.com/support to obtain the supported ROM for Windows Server 2008 installations for the server. If necessary, enable support for No-Execute and hardware-assisted virtualization in the RBSU. Use the RBSU to set date/time and configure the boot controller order (if necessary). Use the Online RAID Configuration Utility (ORCA) to configure the RAID settings for the server.

19

 If installing HP Systems Insight Manager and agents, make sure the SNMP service is loaded and started.

Enabling support for hardware-assisted virtualization in the RBSU

Hyper-V Server 2008 R2 uses an advanced processor feature known as hardware-assisted virtualization. On most ProLiant servers, this feature is enabled by default. Enable hardware-assisted virtualization by following the appropriate procedure in the following sections. ProLiant servers with Intel Processors To enable support for hardware-assisted virtualization in the RBSU, complete the following steps:
1. Restart or power-on the server. 2. Access the RBSU by pressing F9 when prompted. 3. From the RBSU Menu, select Advanced Options.

4. From the Advanced Options menu, select Processor Options. 5. If the server supports Hyper-Threading, select Processor Hyper-Threading, press Enter, and then

select Disabled.

20

6. Select No-Execute Memory Protection, press Enter, and then select Enabled.

7. Select Intel(R) Virtualization Technology, press Enter, and then select Enabled.

8. Press the Esc key until you receive a prompt to press F10 to confirm exiting the RBSU. The server

will restart.

ProLiant servers with AMD processors To enable support for hardware-assisted virtualization in the RBSU, complete the following steps:
1. Restart or power-on the server. 2. Access the RBSU by pressing F9 when prompted. 3. From the RBSU Menu, select Advanced Options.

4. From the Advanced Options menu, select Processor Options.

21

5. Select No-Execute Page-Protection, press Enter, and then select Enabled.

6. Select AMD Virtualization, press Enter, and then select Enabled.

7. Press the Esc key until you receive a prompt to press F10 to confirm exiting the RBSU. The server

will perform a restart.

Installing Microsoft Hyper-V Server 2008 R2

To install Microsoft Hyper-V Server 2008 R2, complete the following steps:
1. Make sure that the server has a DVD drive (either installed in the server or attached to the server)

- Or Boot the server into Microsoft Windows Preinstall Environment (Windows PE or WINPE) from a USB key. It is possible to boot the target server from across a network using Windows Deployment Services. For details on Booting WINPE, refer to the Windows Automated Installation Kit (WAIK).

NOTE
iLO virtual media requires a license key with ProLiant ML and DL servers and, in certain circumstances, with ProLiant BL servers.

2. Place the Hyper-V Server 2008 R2 media into the DVD drive and boot the server from the DVD to

begin the installation.

3. Follow the on-screen instructions to complete the installation.

22

IMPORTANT
The F6 option for updating drivers is not available during the Hyper-V Server 2008 R2 installation. Microsoft has added the option to inject a driver during install (through the Update Driver button), if a boot controller driver is not found. The driver may reside on USB media, floppy drive, or CD-ROM drive.

Installing the PSP

To download the PSP self-extracting executable, complete the following steps:
1. Go to the directory that contains the PSP executable. 2. Invoke the executable and extract the PSP to a desired location.

NOTE
When installing the PSP on a system running Server Core, run the executables rather than double-clicking on them. In addition, on server core systems, you cannot specify the location for extracting the PSP files. The files will extract to the same location as the PSP self-extracting executable. You may also use the procedure outlined in the section titled Installing the ProLiant Support Pack in this integration note.

3. Go to the directory where the extracted PSP is located. 4. Invoke setup.exe to start the PSP deployment. 5. As the PSP deployment starts, the Source Selection screen displays and allows you to enter a

directory where the components to be installed are located. You can also specify that you want to get the latest components from ftp.hp.com. Selecting the Start Inventory button performs an inventory of the available updates. local host, a remote host, or multiple hosts for PSP deployment.

6. After the inventory process finishes, the Select Installation Hosts screen displays. Select either the 7. After you select the host(s), the discovery process for each selected host occurs. Each system is

checked for installed hardware, software, and services.

8. Once the discovery process has completed, the Select Bundle Filter screen displays information

about the PSP bundle that requires installation. Select the bundle and the appropriate filter options. For remote deployments, additional screens allow you to update information on a per-host basis: Select the components for installation Configure the components, if necessary. Review and address failed dependencies before installation. Review the revision history of the components.

9. After selecting the components to install, click Install to proceed with the installation. Once the

installation completes, the Installation Results screen displays. If the PSP installs successfully, the process is complete. Exit HPSUM. Make corrections to your environment.

10. If any components did not install successfully, complete the following steps:

Restart the application to install the components that had problems.

23

Appendix A: Known issues and workarounds

Table A-1 lists the known issues with ProLiant servers and Hyper-V.
Table A-1. Known issues on ProLiant servers Issue 1 Details Description: Solution: Stop 0x0000007E blue screen displays after initial reboot when Hyper-V is installed on Windows Server 2008 R2. Microsoft has published a KB Article and a Hot Fix to prevent the issue from occurring; Article ID: 974598 - You receive a "Stop 0x0000007E" error on the first restart after you enable Hyper-V on a Windows Server 2008 R2-based computer. Refer to the instructions provided in the KB Article and apply the Hot Fix that is available on the Microsoft website at http://support.microsoft.com/kb/974598. After enabling the Hyper-V server role on an HP ProLiant DL785 G5 Server, a black screen displays after the system reboots. Upgrade the ProLiant DL785 G5 server to version A15 of the System ROM dated 08/14/2009 (or later). The virtual machine network is not working when the external virtual network is connected to 1-Gbps NC375i NIC Port 3 or 4 on an HP ProLiant ML370 G6 Server. To workaround this issue onnect the the external virtual network to NC375i NIC Port 1 or 2.

Description: Solution:

Description: Workaround:

24

For more information

For additional information, refer to the resources listed below.
Resource HP website for Hyper-V HP and Microsoft Frontline Partnership website HP website for Windows Server 2008 R2 HP website for management tools HP OS Support Matrix Information on HP ProLiant Network Adapter Teaming for Hyper-V Technical overview on HP ProLiant Network Adapter Teaming Microsoft website (general) Microsoft Hyper-V website Microsoft Hyper-V Server website Microsoft general virtualization website Microsoft website for Windows Server 2008 Home page Microsoft website for additional virtualization information HP Single Point Of Connectivity Knowledge (SPOCK) website with information on HP Storage Array Network (SAN) components, supported host bus adapters, and switches Hyperlink

www.hp.com/go/hyper-v
www.hp.com/go/microsoft www.hp.com/go/ws2008r2 www.hp.com/go/insight www.hp.com/go/osssupport http://h20000.www2.hp.com/bc/docs/support/SupportManual /c01663264/c01663264.pdf http://h20000.www2.hp.com/bc/docs/support/SupportManual /c01415139/c01415139.pdf?jumpid=reg_R1002_USEN www.microsoft.com www.microsoft.com/hyper-v www.microsoft.com/hvs www.microsoft.com/virtualization www.microsoft.com/windowsserver2008/default.mspx http://technet2.microsoft.com/windowsserver2008/en/serverma nager/virtualization.mspx http://www.hp.com/storage/spock

Call to action
Send comments about this paper to: TechCom@HP.com.
2009 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. AMD, AMD Opteron, and AMD-V are a trademark of Advanced Micro Devices, Inc. Intel and Itanium is a or registered trademark of Intel Corporation or its subsidiaries in the United States and other countries Microsoft, Windows Server, and Hyper-V are US registered trademarks of Microsoft Corporation. TC091102IN, November 2009