search for: notsc

...n this case) - Windows Vista Ultimate x64, all Windows Update patches loaded (no SP1 yet) - 4GB RAM - VMWare Workstation 6.0.2 - BIOS has no options to disable power management, etc. On my host PC - C:\ProgramData\VMware\VMware Workstation\Config.ini, put in host.cpukHz = "2000000", host.noTSC = "TRUE", ptsc.noTSC = "TRUE" - AMD's dual core optimizer loaded On CentOS 5.1 VM - use kernel options "noapic nolapic nosmp clocksource=acpi_pm" - use "divider=10" option in the regular kernel - try the vm version of the kernel in centos-plus with the s...

.... Guest OS's are 32-bit FreeBSD (clock works fine after disabling ACPI, setting the clock source to the PIT, and running the guest tools), WinXP (unknown clock status), and i686 CentOS 5.2 (here is the problem). I've tried pretty much everything to try to fix it. I have host.cpukHz, host.noTSC, and ptsc.noTSC set in /etc/vmware/config. I've booted my kernel with noapic, nosmp, noacpi, divider=10. Sadly, I hit the clocksource=pit with divider bug, so I have not been able to boot with both that and divider=10, although clocksource=pit without a divider also does not work. I even bui...

Lguest currently requires a TSC, which breaks older machines and Matt Mackall who boots the host with "notsc". In addition, there is no good solution to changing TSC speeds (informing all the guests about the TSC impending change before it happens would be a great deal of code and have issues with disobedient guests). This patch makes the host determine if the TSC is both constant and stable: if no...

Lguest currently requires a TSC, which breaks older machines and Matt Mackall who boots the host with "notsc". In addition, there is no good solution to changing TSC speeds (informing all the guests about the TSC impending change before it happens would be a great deal of code and have issues with disobedient guests). This patch makes the host determine if the TSC is both constant and stable: if no...

...problem with virtual guests. It seems there are a variety of solutions, some apparently vendor-specific. What is the best practice as of now for KVM guests? * Setting independent_wallclock=1 (or is that a xen-only thing)? * Passing kernel parameters? If so, which? The vmware KB mentions "notsc divider=10" -- is that vmware-specific? * Just don't run ntpd on virtual guests? And let it get its time from the host. The last seems like the easiest/cleanest, if it really does always get its time from the host. Thanks for any info. johnny

...conda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/vg00/root divider=10 notsc # initrd /initrd-version.img #boot=/dev/vda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.18-164.el5) root (hd0,0) kernel /vmlinuz-2.6.18-164.el5 ro root=/dev/vg00/root divider=10 notsc initrd /initrd-2.6.18-164.el5.img titl...

Hi, I followed the discussions regarding the "time moved backward" problem and the use of ntp in such cases. At our department we are running two dovecot servers within an vmware server environment, and unfortunately the timedrift (with ntpd active) exceeds sometimes up to 30 minutes virtual drift within 10 minutes realtime (mostly into future). This is due to some overcorrections

...estion would be appreciated. - CS. ------------------- # For EL5 virtual machines, Append the following in Grub to help keep the clock from drifting # and to reduce the interupt requests # 32bit: --append="rhgb quiet divider=10 clocksource=acpi_pm" # 64bit: --append="rhgb quiet notsc divider=10" bootloader --location=mbr --md5pass=$1$mXSD1l6mO$BBCk1gYArAATS7dlCQGthN. --append="rhgb quiet divider=10 clocksource=acpi_pm" %packages --nobase # Other packages not listed here # ntp was installed ntp ### Add step-tickers ### cat > /etc/ntp/step-tickers <<\EOF...

...perating system that is using TSC on that platform. Action is required for these operating systems as outlined in the "Solutions" section below, but, fortunately, many of them already provide simple boot configuration options that allow the TSC to be bypassed (such as "notsc" and "clock=pmtmr") to work around this problem. C2 and C3 State Change ====================== The core-clock grid can be divided up and down when entering and exiting C2 and C3 states and the TSC is adjusted accordingly. However, the clock-grid of all cores on...

Stan, Thanks for the reply. In our case we have actually already done most of the work you suggested to no avail. We had rebuilt two new ntp servers that sync against two stratum 1 sources, and all our nfs clients, regardless of using dovecot, sync to those two machines. You bring up the difference between bare metal and hypervisor, and we are running these machines on vmware 4.0. All the

Hi all, If you are using the kernel divider= option in your vmware quest, you are probably aware of the bugs reported at: https://bugzilla.redhat.com/show_bug.cgi?id=315471 Someone @redhat "confirmed" the fix is in the test kernel -92. I tried it but it seems to have the same problem as before - when used with clocksource=pit, it hangs on bootup. Wonder if some of you can test this