Running trixbox on Hyper-V 2008 R2

Previously, I’ve never had much success running trixbox within a virtual environment, but I decided to revisit the possibility with the recent release of Windows Server 2008 R2 and the latest version of trixbox (currently 2.8) and this time had much greater success.

The only thing I had to do was install the Microsoft Hyper-V Integration Components for Linux on the machine and set the kernel parameters appropriately (as described below).

You can download the .iso from Microsoft at

Currently, CentOS/RedHat doesn’t appear to be supported by Microsoft, but following the steps below will allow you to install the appropriate drivers (and confirm a successful intallation): –

  • Mount the downloaded .iso on your trixbox machine
  • Install the kernel-devel and gcc (GNU Compiler Collection) packages by running the commands below

yum install kernel-devel

yum install gcc

  •  Now you’ll need to mount the CD ROM using these commands

mkdir -p /mnt/cdrom

mount /dev/cdrom /mnt/cdrom

  • Copy the contents of the CD to the local machine

cp -rp /mnt/cdrom /opt/linux_ic

  • Unmount the CD ROM

umount /mnt/cdrom

  • Run the driver setup

cd /opt/linux_ic

./ drivers

  • Set the kernel boot parameters as per this article
  • You’ll need to restart to initialise the drivers

shutdown -r now

  • When the machine is back up and running, make sure the drivers are loaded by running the command below

lsmod | grep vsc

  • This should give you a result similar to the following






Now you have the integration components installed, configure the rest of the options on your trixbox and test it out. I allocated mine 512MB RAM, and it doesn’t skip a beat while I performed audio streaming tests.

8 thoughts on “Running trixbox on Hyper-V 2008 R2”

  1. i have this error on ./ drivers
    lib/modules/2.6.18-128.1.10.e15/build: no such file……

  2. ok i have solved the problem.
    Verify Symbolic Link is intact (look for build – if it is highlighted in red then the link is broken)
    # ls –l /lib/modules/2.6.18-128.el5/
    See where the link should be pointed
    # ls –l /usr/src/kernels/
    Remove the existing Symbolic Link
    # rm /lib/modules/2.6.18-128.el5/build
    Create a new Symbolic Link
    # ln –s /usr/src/kernels/2.6.18-128.1.16.el5-x86_64/ /lib/modules/2.6.18-128.el5/build

  3. mi piacerebbe proprio capire come fare lo yum install kenel-devel visto che non c’è la connessione lan, la linux ic serve apposta per i driver giusto?

Leave a Reply

Your email address will not be published. Required fields are marked *