Trixbox in VMWare cause time not in sync

thanks.

after a lot of search on the web I have finally found the procedure.
my ommit part was the grub file change...

thanks!

now at a regular basis the system resync the clock.

* Add the clock=pit boot option to your guest's kernel command line in the /etc/lilo.conf or /boot/grub/grub.conf file.

The following example shows the syntax for LILO:
image=/boot/vmlinuz
label="linux"
root=/dev/hda1
initrd=/boot/initrd.img
append="resume=/dev/hda6 splash=silent clock=pit"
read-only

(Remember to run /sbin/lilo after editing lilo.conf, so that your edits take effect.)

Here is an example of the syntax for GRUB:
title Fedora Core (2.6.9-1.667)
root (hd0,0)
kernel /vmlinuz-2.6.9-1.667 ro root=/dev/hda2 clock=pit

Adding this boot option disables the kernel's correction for lost ticks, so be sure to also install VMware Tools and turn on
time synchronization. The latter prevents the guest clock from losing time over the long term due to lost ticks.

For additional information about working with boot loaders, see your Linux distribution's documentation.
* As an alternative, especially if you are unable to use VMware Tools, you can instead give the kernel command line option

clock=pmtmr

With this option, the kernel corrects more properly for lost ticks, but occasionally overcorrects and ends up gaining time slowly. This option is the default for most 2.6 kernels, but some distributions may patch their kernels to change the default. In SuSE SLES 9 kernels, the default is clock=tsc. The code enabled by the tsc setting severely overcorrects for lost ticks when used in a virtual machine and tends to gain time rapidly.