HP BL680c Implementing Microsoft Windows Server Hyper-V Release Candidate 1 (R - Page 21

Appendix A: Known issues and workarounds

Page 21 highlights

Appendix A: Known issues and workarounds Table A-1 lists the known issues with ProLiant servers and Windows Server 2008 Hyper-V RC1. Table A-1. Known issues on ProLiant servers Issue Details Issue 1 When attempting to enable Windows Server 2008 Hyper-V RC1, the installer reports that the server does not contain the required hardware support. Description: When attempting to enable Windows Server 2008 Hyper-V RC1, the installer reports that the server does not contain the required hardware support. Workaround: Ensure that support for both No-Execute and hardware assisted virtualization have been enabled in the RBSU. Refer to the "Enable support for hardware assisted virtualization in the RBSU" section for instructions on performing this task. Issue 2 During installation, selected network cards for use with Windows Server 2008 Hyper-V RC1 are reported as not configured correctly. Description: A known issue exists with Windows Server 2008 Hyper-V RC1 that causes the installer to report virtual network configuration issues. Workaround: Using the Virtualization Role snap-in, confirm that all NICs selected during installation to be used as virtual networks are configured correctly. Issue 3 The Virtualization snap-in or event log does not correctly report many Windows Server 2008 Hyper-V RC1 errors. Description: In Windows Server 2008, successful events are recorded in the event log, whereas problems are ignored. For example, if a server has not been correctly configured in the RBSU to enable support for hardware assisted virtualization, the user might be unable to start a virtual machine by right clicking the virtual machine and selecting Start. There will be no event recorded in the Virtualization event log to indicate any configuration issues. However, connecting to a virtual machine by right-clicking the virtual machine and selecting Connect and then attempting to start the virtual machine by clicking the Start button in the toolbar will cause an error message to be displayed. The message will indicate that the virtual machine could not be started because the hypervisor is not running. Issue 4 The Windows Server 2008 Hyper-V RC1 folder and components are not found in C:\Windows. Description: Check that Windows Server 2008 x64 Edition has been used to complete the installation of Windows. Windows Server 2008 Hyper-V RC1 only ships with the x64 edition of Windows. If the x86 version of Windows Server 2008 has been installed, reinstall the OS using the x64 edition. Issue 5 Windows Server 2008 Hyper-V RC1 does not support the Network Configuration Utility (NIC Teaming). Deselect this component before beginning the installation of PSP components. Description: Currently, there are no plans to add support for NIC teaming. 21

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23

Appendix A: Known issues and workarounds
Table A-1 lists the known issues with ProLiant servers and Windows Server 2008 Hyper-V RC1.
Table A-1.
Known issues on ProLiant servers
Issue
Details
When attempting to enable Windows Server 2008 Hyper-V RC1, the installer reports that the server
does not contain the required hardware support.
Issue 1
Description:
When attempting to enable Windows Server 2008 Hyper-V RC1, the installer reports
that the server does not contain the required hardware support.
Workaround:
Ensure that support for both No-Execute and hardware assisted virtualization have
been enabled in the RBSU. Refer to the “
Enable support for hardware assisted
virtualization in the RBSU
” section for instructions on performing this task.
Issue 2
During installation, selected network cards for use with Windows Server 2008 Hyper-V RC1 are
reported as not configured correctly.
Description:
A known issue exists with Windows Server 2008 Hyper-V RC1 that causes the
installer to report virtual network configuration issues.
Workaround:
Using the Virtualization Role snap-in, confirm that all NICs selected during installation
to be used as virtual networks are configured correctly.
Issue 3
The Virtualization snap-in or event log does not correctly report many Windows Server 2008 Hyper-V
RC1 errors.
Description:
In Windows Server 2008, successful events are recorded in the event log, whereas
problems are ignored.
For example, if a server has not been correctly configured in the RBSU to enable
support for hardware assisted virtualization, the user might be unable to start a virtual
machine by right clicking the virtual machine and selecting
Start
. There will be no
event recorded in the Virtualization event log to indicate any configuration issues.
However, connecting to a virtual machine by right-clicking the virtual machine and
selecting
Connect
and then attempting to start the virtual machine by clicking the
Start
button in the toolbar will cause an error message to be displayed. The message will
indicate that the virtual machine could not be started because the hypervisor is not
running.
Issue 4
The Windows Server 2008 Hyper-V RC1 folder and components are not found in C:\Windows.
Description:
Check that Windows Server 2008 x64 Edition has been used to complete the
installation of Windows. Windows Server 2008 Hyper-V RC1 only ships with the x64
edition of Windows. If the x86 version of Windows Server 2008 has been installed,
reinstall the OS using the x64 edition.
Issue 5
Windows Server 2008 Hyper-V RC1 does not support the Network Configuration Utility (NIC
Teaming). Deselect this component before beginning the installation of PSP components.
Description:
Currently, there are no plans to add support for NIC teaming.
21