search for: chanm

Hi everyone: Just a follow up on the fast clock issue: "Can you double-check that 'cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq' outputs the same number as your 'cpuKHZ' setting in your config.ini file?" There is no cpufreq directory under /sys/devices/system/cpu/cpu0; all I see is "cache" (dir), "crash_notes" (a file) and

...-virt] Fwd: Fast clock under VMWare > To: Discussion about the virtualization on CentOS > <centos-virt at centos.org> > Message-ID: <C3E9B88C.5B99%elliot at vmware.com> > Content-Type: text/plain; charset="US-ASCII" > > On 2/26/08 12:28 PM, "chanms" <chanms at gmail.com> wrote: > > > What other things I can do in order to fix this? > > Hi, > > There were a few replies to your post on Friday. Please follow up on them. > > Best, > -- Elliot

Hi everyone, I have been struggling with having the clock of Linux VM's (including CentOS 4.6 and 5.1) running very fast under VMWare, no matter what I have tried. My platform: - AMD Turion X2 TL-60 - AMD 690 chipset with integrated Radeon x1250 (probably doesn't concern in this case) - Windows Vista Ultimate x64, all Windows Update patches loaded (no SP1 yet) - 4GB RAM - VMWare

Well, to the clock being fast work around, I kind of found a way to work around it for now... 1) use a distribution that supports VMI (VMware's paravirtualization) 2) enable VMI paravirtualization support in VMware Workstation 6 VM's profile 3) use vmi-timer as the clocksource (as opposed to pit, acpi_pm, etc.) 4) CPU must be constantly at maximum frequency For 1), I use Ubuntu 7.10 For