Beginning of this page.
Jump to main content.

Please note that JavaScript and style sheet are used in this website,
Due to unadaptability of the style sheet with the browser used in your computer, pages may not look as original.
Even in such a case, however, the contents can be used safely.

Site menu starts here.
Skip site menu.
End of site menu.
Displaying present location in the site.
NEC Express5800 Server Series> Download > Windows Support Kits
End of menu.

NEC Express5800 Server Series
Microsoft® Windows Server® 2008 R2 Support Kit

Hyper-V 2.0

Please read this page carefully before you use Hyper-V 2.0 on NEC Express5800 Server. "Microsoft Hyper-V Server 2008 R2" downloadable from Microsoft web site is not the scope of this page.

Supported Models

Category Model
Rack Server NEC Express5800/R120a-1, R120a-2
Fault Tolerant Servers R320a-E4, R320b-M4, R320c-E4, R320c-M4, R320d-M4, R320e-M4,
R320e-E4, R310c-E4, R310d-E4, R310e-E4
Blade Server NEC Express5800/B120a, B120a-d

Supported Guest OS

NEC Express5800 supports following guest OS. Some guest OS require Service Pack. To get better performance and manageability, Integration Services for Hyper-V 2.0 is recommended to be installed on the guest OS.

OS Edition ServicePack
Windows Server 2008 R2 Standard / Enterprise  
Windows Server 2008 (x86/x64) Standard / Enterprise  
Windows Server 2003 R2 (x86/x64) Standard / Enterprise SP2 or later
Windows Server 2003 (x86/x64) Standard / Enterprise SP2 or later
Windows 2000 Server / Advanced Server SP4*
Windows 7 (x86/x64) Professional  
Windows Vista (x86/x64) Business SP1 or later
Windows XP (x86/x64) Professional SP2 or later
SUSE Linux Enterprise Server 10 - SP2


As for Windows 2000, SP4 pre-applied media must be used for installations.

Considerations for installing Service Pack 1

To use Windows Server 2008 R2 SP1, note the following Considerations:

See also Considerations and Restrictions.
For how to install SP1 and the information about our validated models, refer to About Windows Server 2008 R2 and Windows 7 Service Pack 1.

Installation Guide

How to set up Live Migration

Refer to the following guide for how to setup Live Migration.
 Microsoft Hyper-V Server 2008 R2: Using Live Migration

To use Live Migration feature on Hyper-V2.0, you must configure Windows Server Failover Cluster.

How to install Integration Services

Refer to the following guide for how to install Integration Services.
  • Windows OS
  • 1.Connecting VM
    Connect the VM in which you will install Integration Services from the Hyper-V Manager console.
    2.Inserting Setup Disk
    Select "Insert Integration Services Setup Disk" option from the "Action" menu. This will attach a setup disk to the VM DVD drive.
    3.Installing Integration Services
    The installer of Integration Services will begin automatically, so follow the instructions displayed on the screen. You will need to restart the VM when the installation completes.

    (Note) If the installation does not begin automatically, start is manually by running the following files in the VM DVD drive.

      - x64 OS
      - x86 OS
  • Linux OS
  • Integration Services for Linux is not included in Hyper-V. You have to download this (version 2.1 or 3.1) on Microsoft Download Center. For how to install Integration Services on Linux OS, refer to "Read Me" file found on the same website.

    Considerations and Restrictions

    Stop Error issues of Hyper-V2.0

    MS posted the information about Hyper-V 2.0 Stop Error on Microsoft Knowledge Base.
    The following two issues will be resolved by applying this hotfix for Hyper-V2.0 (KB2264080).
    Refer to Microsoft Knowledge Base for more details of this hotfix.
    This hotfix is included in Windows Server 2008 R2 SP1. If you install SP1 to the host OS, you do not have to apply this hotfix.
    1. Stop Error (0x101) may occur on a server with the Intel® Xeon® processor 5500 series.(KB975530)
    This issue can be resolved by disabling C3-state by setting a registry key.

    2. Stop Error (0x0000001a) may occur on a server with Intel Westmere processor.(KB981791)

    VM Start Failure issue of Hyper-V2.0 (KB2517374)

    MS posted the information about VM start failure issue that may occur on a server with a processor that supports Intel AVX and CPU instructions. This issue can be resolved by applying the hotfix provided by Microsoft or SP1 of Windows Server 2008 R2.
    This hotfix disables the AVX feature on the guest OS, so we recommend applying SP1.
    Refer to Microsoft Knowledge Base for more details of this issue.

    Performance decrease issue of Hyper-V2.0 (KB2517329)

    MS posted the information about performance decrease issue that may occur on a server with Intel Westmere or Sandy Bridge processors and with a large amount of physical memory.
    This issue can be resolved by applying the hotfix provided by Microsoft.
    Refer to Microsoft Knowledge Base for more details of this issue.

    Restrictions on using Legacy Network Adapter on guest OS

    1. Guest OSes with no Legacy Network Adapter support

    In Hyper-V2.0 environment, Legacy Network Adapter is not supported on the following guest OSes
        - Windows Server 2003 (x64) SP2
        - Windows Server 2003 R2 (x64) SP2
        - Windows XP (x64) SP2

    2. 'Enable MAC Address Spoofing'

    When Legacy Network Adapter is used, the MAC address of this adapter can be changed on the guest OS even though "Enable MAC Address Spoofing" item is deactivated (default). If the MAC address is changed, network communications around this adapter will become unavailable. Thus, please note that you do not change MAC address of the adapter on guest OS when "Enable MAC Address Spoofing" item is deactivated.

    Restrictions to use SCSI controller on guest OS

    In Hyper-V2.0 environment, SCSI controller is not supported on the following OSes.

        - Windows 2000 SP4
        - Windows XP (x86) SP2/SP3

    Considerations for configuring cluster between VMs

    When you configure a cluster between VMs using Windows Server Failover Cluster, only iSCS storage is supported as the shared storage.(Microsoft by design).
    If you desire more proven connection topology such as Fiber Channel, use EXPRESSCLUSTER.

    Considerations for using optical drive on guest OS (KB2005143)

    • When you install OS or applications, or apply Service Pack on the guest OS, if an optical drive is allocated to the VM, the guest OS may not recognize a disk change in the optical drive.
      In this case, unallocate the optical drive on VM settings after changing the disks, and reallocate the drive to the VM afterward.
    • On a ft server, do not let a physical CD/DVD drive remain allocated to a virtual machine. The guest operating system may stall if the PCI module is detached and the primary module is switched while the physical CD/DVD drive remain allocated to the virtual machine.

    Considerations for using Windows 2000 Server SP4 as guest OS (KB976488)

    If you use Windows 2000 Server SP4 as the guest OS with Integration Services being installed, running Windows Update may cause blue screen.
    On Windows2000 Server SP4 running as the guest OS, run Windows Update before installing Integration Services. You should use Legacy Network Adapter in the VM environment before installing Integration Services.

    Considerations for exporting VM

    If you export a VM with the optical drive being allocated to it, you will get an error event as follows on importing the exported data, and then the optical drive will be unallocated. (Import itself will be done successfully.)

    Failed to import correctly the device "Microsoft Virtual CD/DVD Disk". Error: Invalid parameter (0x80041008).

    When you export a VM to which the optical drive is allocated, unallocate the drive beforehand.

    Considerations for inputting text from clipboard

    If you copy double-byte characters on the host OS and paste them on the guest OS by selecting "clipboard" - "Type clipboard text" menu, those characters will be garbled. There is no solution for this, so avoid doing this operation.

    Considerations for using Windows 7/Windows Server 2008 R2 Hyper-V Manager

    If you create a VM using Hyper-V Manager added on Windows 7/Windows Server 2008 R2, SCSI controller will be installed on the VM by default.
    There are some restrictions on using SCSI controller on Hyper-V2.0, so you may have to delete the SCSI controller from VM Setting as needed.

    Intel® PROSet

    To use the teaming features by the Intel® PROSet in the Hyper-V 2.0 environment, refer to the supported models/LAN adapters and important notice provided in About Support for Intel LAN Teaming Features on Hyper-V.
    For a configurable combination of LAN adapters within a team, refer to System Configuration Guide of the supported models.

    Top of this page