vmwarez.com
           -Where Virtualization is a Reality!

5 Comments:

• and click here for FREE VMware Server http://www.vmware.com/products/server/

  By  osde.info, at March 07, 2006 5:31 AM  

• Tried the VMWare player version of asterisk@home 2.7,
  the clock is running a lot faster than it should, about 30min in a couple of hours.
  
  Anyone seen this, or even better anyone who have found a fix, or even have a temporary auto script that updates the clock regulary?
  
  This test is run on a budget Win2003 Server, celeron 2,8Ghz.

  By  Anonymous, at March 19, 2006 12:21 PM  

• See http://hollingum.blogspot.com/ for a fix.
  
  Regards
  
  Neil Hollingum

  By  NeilHollingum, at March 26, 2006 9:26 AM  

• Make sure VMwareTools is installed and turn on time synchronization to prevent the vm clock from losing time over the long term due to lost ticks. To do this we will have to edit the .vmx and set:
  
  tools.syncTime = "TRUE"
  
  
  
  Add the boot parameter clock=pit on the vm to disable the kernel's correction for lost ticks to prevent the clock from running too quickly.
  
  *In the x86_64 Linux kernel, use the boot option notsc instead of clock=pit.
  
  Here is an example of the syntax for GRUB:
  
  title Red Hat Enterprise Linux ES (2.6.9-22.EL)
  
  root (hd0,0)
  kernel /vmlinuz-2.6.9-22.EL ro root=LABEL=/ clock=pit
  
  initrd /initrd-2.6.9-22.EL.img
  
  
  In a one-CPU virtual machine, add the following kernel command line parameters to the vm server to keep the clock from running too slowly and too quickly:
  
  clock=pit nosmp noapic nolapic
  
  Here is an example for GRUB:
  
  title Red Hat Enterprise Linux ES (2.6.9-22.EL)
  root (hd0,0)
  kernel /vmlinuz-2.6.9-22.EL ro root=LABEL=/ clock=pit nosmp noapic nolapic
  
  initrd /initrd-2.6.9-22.EL.img
  
  
  
  You will need to reboot the server after making these updates.

  By  jay, at June 22, 2007 1:49 AM  

• if your clock runs *faster* you might also want to check this: https://help.ubuntu.com/community/VMware/Workstation
  
  i.e.:
  
  #
  
  Add the following line to /etc/vmware/config
  
  host.cpukHz = x
  host.noTSC = TRUE
  ptsc.noTSC = TRUE
  
  x = Max CPU speed in kHz (i.e. 2GHz CPU = 2000000)

  By  Anonymous, at April 12, 2008 4:01 AM  

Post a Comment

<< Home