Trixbox under VMWare Server 2.0 hosted on Linux
I had Trixbox running fine under VMWare on an older machine. When I moved to a new, fast, dual core, 64-bit server, all audio playback became choppy. I just spent an entire day getting it working, and I'd like to share the details with the trixbox community at large. All of this information came from various places on the web, but none of it was collected together in one nice place.
I can't claim this will work for everyone, but it worked for me:
First, copy the vmware tools rpm to the trixbox host.
- select "Install VMWare Tools" from the VMWare monitor
- login to trixbox as root and run these commands:
mkdir mnt mount /dev/cdrom mnt cp mnt/*.rpm .
Now, let's grab a new kernel:
wget dev.centos.org/~tru/kernel-vm/5/RPMS/i386/kernel-vm-2.6.18-92.1.13.el5.i686.rpm wget dev.centos.org/~tru/kernel-vm/5/RPMS/i386/kernel-vm-devel-2.6.18-92.1.13.el5.i686.rpm
This kernel is optimized specifically for running under VMWare. Without it, I had no luck getting rid of choppy audio.
Since we're upgrading the kernel, we also need to grab the zaptel source:
wget www.voicetronix.com.au/Downloads/asterisk/zaptel-wcopenpci-1.4.9vt1.tar.gz
Finally, we need the gcc compiler:
yum install gcc
Now we have all the pieces, so let's put them together. First, install the new kernel:
rpm -ivh kernel-vm-*
Edit the kernel options in /boot/grub/menu.lst:
vi /boot/grub/menu.lst
Make sure "default=0" is set at the top so the new kernel boots. Add the "acpi=off" and "clock=pit" options to the kernel you just installed. It should now look like this:
kernel /vmlinuz-2.6.18-92.1.13.el5vm ro root=LABEL=/ acpi=off clock=pitThe first option disables ACPI (Advanced Configuration and Power Interface) for the kernel, which seems to interfere with timing, and the second forces the kernel to use a more accurate technique for synchronizing the vm time with the host time. (Another thread recommended also putting "nosmp noapic nolapic". That actually made it worse for me. YMMV.)
We're ready to boot the new kernel:
init 6
When trixbox is back up, log in again as root. Now we can install the VMWare tools:
vmware-config-tools.pl
Pick the default on every question by hitting enter.
Now, we'll rebuild the zaptel drivers:
tar xzf zaptel-wcopenpci-1.4.9vt1.tar.gz cd zaptel-wcopenpci-1.4.9vt1 ./configure make && make install && make config
Now edit /etc/sysconfig/zaptel and comment out all of the "MODULES=..." lines, EXCEPT the "ztdummy" driver. It will be commented out by default, so you'll need to uncomment it:
vi /etc/sysconfig/zaptel
Reboot one last time and you should have a stutter-free trixbox running under VMWare!
init 6
Sources:
http://pbxinaflash.net/vm/
http://www.trixbox.org/forums/trixbox-forums/help/crappy-sound-pl...
@squiggly,
Thank you for taking the time to put up your instructions. These steps remove dependency errors and some of the 'broken trixbox' issues after updating from a fresh vm install. Few things to mention...
When following these steps, be sure to note:
- the address from dev.centos.org for the kernel is: ..el5.xxx not a 1 but an L as in Larry.
- make sure to install the kernel and the kernel-devel like squiggly indicates
- you could alternately run the command: rpm -Uvh dev.centos.org/the-rest-of-the-address for the file targeted for download and install.
- for those like me that hate to edit with vi, you can use the command: nano -w filename-to-edit
When installing the vmware tools, note the following:
- trixbox core doesn't include 'make' so install it with yum install make
- you have to go to the folder where you copied the installer to run the rpm install command, use locate VMwareT* to find the vmware-tools rpm file, then enter: rpm -ivh VMwareTools* to install vmware tools. Once done, run the vmware-config-tools.pl script as instructed by squiggly.
When running the .pl script the first time, note the following:
- if you run into trouble with your kernel header location, run this to point to your headers: ls -d /usr/src/kernels/$(uname -r)*/include
Lastly:
- make sure you note that trixbox updates STILL break the box by changing all your customized passwords back to the original; therefore, make note of your orginal install passwords and keep them with your records for the current passwords. Maybe one day the 'developers' will allow for the upgrade to process without changing current passwords. (maybe by- ripping the customized passwords, storing in a temporary hash, performing current upgrade changing to original passwords, retrieving customized passwords from hash, then placing passwords back in place, complete checks and upgrade).
oh, and..
Bubba: ever think people might run vmserver on a linux/unix host? (rhetorical, don't reply)
Squiggly,
I do not think I that I can thank you enough for posting this info here... It took me days to gather it from different places, but when I found it already posted here by you I was reassured that I am on the right track thanks.
Virtualization is the wave of the present, those who resist it are stuck in the past.


Member Since:
2008-10-04