ID #1123

How do I run Bright under MS Windows Server Hyper-V (Windows Server 2008/R2)?

How do I run Bright under MS Windows Server Hyper-V (Windows Server 2008/R2)?

This article walks you through an install of Bright under Microsoft Hyper-V (Windows Server 2008/R2). It assumes you are picking up and installing Bright with RHEL6u3 as a base distribution. But it should work pretty much the same for other Red Hat derivatives, such as Cenan class="highlight">tOan>S.


Install Bright Under Hyper-V


1. Open Hyper-V Manager: Click Start, point an class="highlight">toan> Administrative an class="highlight">Toan>ols, and then click Hyper-V Manager.

2. Create a new virtual machine where you will install Bright: In the Actions menu, click New, and then click Virtual Machine.

3. Specify the Bright installation media like this: Right-click the virtual machine that you created, and then click Settings. In IDE Controller, select one of the following:

  • An image file in ISO format that contains the files required for installation
  • A physical CD/DVD drive that contains the installation media

4. Turn on the virtual machine: Right-click the virtual machine that you created, and then click Connect.

5. Begin installing Bright as described in section 2.3 "Head Node Installation: Bare Metal Method" in the Administraan class="highlight">toan>r Manual.

6. When prompted, restart the virtual machine and complete any first-boot configuration tasks.

Important Considerations


1. Networking
There are two type of network adapters, "Legacy Network Adapter" and (non-legacy) "Network Adapter". The legacy network adapter works without installing a virtual machine driver because the driver is already available on most operating systems. It emulates a physical network adapter, multiport DEC 21140 10/100TX 100 MB. Also, it supports network-based installations via PXE. The legacy network adapter is an class="highlight">notan> supported in the 64-bit edition of Windows Server 2003 or the Windows XP Professional x64 Edition.

an class="highlight">Notan>e
Unless a legacy network adapter was added during the virtual machine’s initial configuration, the virtual machine will an class="highlight">notan> have any network support. 

2. Supporting new hardware

If the "Linux Integration Services for Hyper-V" drivers, freely available from Microsoft, are built and installed, then you can user the Hyper-V manager an class="highlight">toan>:

  • add a non-legacy network adapter
  • add the IDE san class="highlight">toan>rage controllers
  • add the SCSI san class="highlight">toan>rage controllers.

The integration services can improve speed and functionality. However, this procedure is non-trivial because Microsoft only supports certain guest operating systems.


Install Linux Integration Services Version 3.4

1. Log on an class="highlight">toan> the virtual machine.

2. In Hyper-V Manager, configure LinuxICv34.ISO as a virtual CD/DVD drive on the virtual machine. The exact name will depend on the version of the Linux Integration Services.

3. Once configured, the LinuxICv34.ISO should appear mounted under /media/CDROM if auan class="highlight">toan>mount is enabled. If auan class="highlight">toan>mount is an class="highlight">notan> enabled, use the following command an class="highlight">toan> mount the ISO file:


# mount /dev/cdrom /media

4. Change an class="highlight">toan> the direcan class="highlight">toan>ry relevant an class="highlight">toan> your distribution:
For RHEL / Cenan class="highlight">tOan>S 6.0, 6.1, 6.2:
# cd /media/CDROM/RHEL6012

For RHEL / Cenan class="highlight">tOan>S 6.3:
# cd /media/CDROM/RHEL63

5. Run the following command an class="highlight">toan> install the Hyper-V-specific (or “synthetic”) drivers. A reboot is required after installation.

For RHEL / Cenan class="highlight">tOan>S 6.0, 6.1, 6.2, 6.3:
# ./




Issue: an>the installer doesn't recognize any hard drivesan>


Switch an class="highlight">toan> console using Alt+Ctrl+F2 and load the following kernel modules:

an>hv_san class="highlight">toan>rvscan>

an>an>an>When you reach the layout selection page for the disks you might still an>an>see an undefined message but you can ignore it. The disks will be an>an>detected properly and you can specify a cusan class="highlight">toan>m layout XML schema an class="highlight">toan> an>an>match your>an>


1. Readme of Linux Integration Services 3.4 for Hyper-V

Linux Integration Services for Hyper-V:
<a href="" target="_blank">>

Supported Linux operating systems:

<a href="">>

Windows server 2008/R2 drivers:

<a href="">


Tags: -

Related entries:

You cannot comment on this entry