search for: acpi_pm

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

...my problem. However, according to the README [2] this isn't necessary as of CentOS 5.3 and therefore these packages are not maintained anymore (the latest released kernel-vm is 2.6.18-92.1.22). >From what I understand, as of CentOS 5.3 it is possible to use the "divider=10 clocksource=acpi_pm" to reduce the frequency to 100Hz. I tried this setting, and it made no difference at all. I also tried to install the VirtualBox guest extensions, and still, the host CPU never goes below 50%. Is there any way to solve this issue without resorting to a custom kernel build? Thanks, Sagi [1]...

...ent, 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 same kernel options in first line No matter what I try, the CentOS clocks are still fast - at a rate of almost 2 seconds for every 1 real second. What other things I can do i...

...s in ref to timekeeping issue. Any comments or suggestion 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-ticker...

Hello, I was thinking of creating a wiki page about Xen clocksources and timekeeping.. including dom0, PV guests and HVM guests. Dan and Jeremy: You guys might have some ideas for this page.. please let me know your thoughts :) Subjects to cover: - Xen hypervisor clocksources (hpet, acpi_pm, pit) - Xen dom0 clocksource, ntpd, etc - Xen PV guest clocksources, independent_wallclock, ntpd, etc - Xen HVM guest clocksources, ntpd, etc - Live migration - Workarounds for known bugs - Recommended settings - Bad (not recommended) settings -- Pasi _____________________________________...

Hi folks, I hope this is the right place to ask - if not I can switch to the CentOS mailing list. I am running GITCOs 3.4.3 hypervisor with original RHEL5.5/CentOS5.5 kernels in dom0 and domU. I have phenonema I want to get rid of (like time running wild - really wild). So I am looking for a way to compile a kernel with all CentOS refinements/backports/additions and xen 3.4.3. I have

...umped forwards 104 seconds 2011-01-14T11:49:16.842962+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds I've checked the clock settings in Centos and it all looks OK. NTP is running and not complaining about clock drift. Vmware recommend appending 'divider=10 clocksource=acpi_pm' kernel boot options to prevent timekeeping issues, which I've done. Has anyone else encountered this message? Is it something to be concerned about? Thanks, Ian.

[Follow-ups set to gmane.linux.centos.general] My wife had been running CentOS 6.4 almost since its inception; then her PC broke down. We got a PC from System76, and Ubuntu turned out utterly unsuitable for us, as expected -- as bad for us as Gnome3. (I had previously bought a System76 net book (starling iirc), and immediately installed the then current Fedora; all has been

...> [ 1.781091] pnp 00:03: [dma 2] > > [ 1.781112] pnp 00:03: Plug and Play ACPI device, IDs PNP0700 (active) > > [ 1.781248] pnp 00:04: Plug and Play ACPI device, IDs PNP0501 (active) > > [ 1.781553] pnp: PnP ACPI: found 5 devices > > [ 1.787555] clocksource acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns > > [ 1.790067] Switched to clocksource acpi_pm > > [ 1.790589] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7 window] > > [ 1.790591] pci_bus 0000:00: resource 5 [io 0x0d00-0xadff window] > > [ 1....

...Ds PNP0f13 (active) > [ 1.781091] pnp 00:03: [dma 2] > [ 1.781112] pnp 00:03: Plug and Play ACPI device, IDs PNP0700 (active) > [ 1.781248] pnp 00:04: Plug and Play ACPI device, IDs PNP0501 (active) > [ 1.781553] pnp: PnP ACPI: found 5 devices > [ 1.787555] clocksource acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns > [ 1.790067] Switched to clocksource acpi_pm > [ 1.790589] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7 window] > [ 1.790591] pci_bus 0000:00: resource 5 [io 0x0d00-0xadff window] > [ 1.790593] pci_bus 0000...

...Ds PNP0f13 (active) > [ 1.781091] pnp 00:03: [dma 2] > [ 1.781112] pnp 00:03: Plug and Play ACPI device, IDs PNP0700 (active) > [ 1.781248] pnp 00:04: Plug and Play ACPI device, IDs PNP0501 (active) > [ 1.781553] pnp: PnP ACPI: found 5 devices > [ 1.787555] clocksource acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns > [ 1.790067] Switched to clocksource acpi_pm > [ 1.790589] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7 window] > [ 1.790591] pci_bus 0000:00: resource 5 [io 0x0d00-0xadff window] > [ 1.790593] pci_bus 0000...

...it > just goes to that CentOS error message, and stops. > > I've also googled for '"upstream testing" hardware' > > Any thoughts or experience??. > > Did you try adding to the kernel line the parameter "clocksource=tsm" or "clocksource=acpi_pm"? Alexander

...9; 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 "topology" (dir). However under /sys/devices/system/clocksource/clocksource0, available_clocksource reads acpi_pm jiffies tsc pit, current_clocksource reads pit. (I put in the line clocksource=pit) in the grub boot up line. Divider=10 in the bootup line causes the boot up process to hang and a reset has to be performed; removing it and the CentOS boots properly. I'm currently using 2.6.18-53.1.13.el5, w...

...o 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 2), the VM must be VMWare 6 profile type, then in Settings -> Options -> Advanced, check on "Enable VMware paravirtual kernel support"). I was unable to use VMI before because my entire Vista (x64...

We've noticed our fully-virtualized KVM guests' time keeps getting faster, despite running ntpd. A quick google reveals this to be a known 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

...ng latency timer to 64 rtc_cmos 00:01: setting system clock to 2011-12-15 09:33:28 UTC (1323941608) ata_piix 0000:00:01.1: setting latency timer to 64 Clocksource tsc unstable (delta = -547592984 ns) [root at xxxx ~]# cat /sys/devices/system/clocksource/clocksource0/available_clocksource kvm-clock acpi_pm [root at xxxx ~]# cat /sys/devices/system/clocksource/clocksource0/current_clocksource kvm-clock cpuspeed service is not active on the guest. acpid service is active on the guest (so it can be shut down from the host with "virsh shutdown"). reading Redhat documentation, I did everythin...

...hat is able to correct this big mismatch. But what I don't understand is that the host does not seem to help the client with it's timekeeping. On a fedora16 machine I can tell that kvm-clock is being used: cat /sys/devices/system/clocksource/clocksource0/available_clocksource kvm-clock tsc acpi_pm cat /sys/devices/system/clocksource/clocksource0/current_clocksource kvm-clock One the centos5 client I can think I see the same: dmesg|grep time.c time.c: Using 1.193182 MHz WALL KVM GTOD KVM timer. If I suspend a client, I see the time is correct just after resume. If I save and restore the tim...

...ler version 39.2 ? then 3 attempts to locate an ipmi interface at different addresses ... Refined TSC clocksource calibration: 2175.999 MHz switching to clocksource TSC Googling a bit, finds a few references to similar issues on gentoo and at lkml. There was a suggestion to boot with clocksource=acpi_pm but for me that hangs at the same location (minus the switching clock source message) I have updated the motherboard BIOS to latest. I had used the the 6.3 net installer disk (and the 6.4 repo) which I noticed had kernel 2.6.32-279, so I retrieved that kernel from the vault and it works. The 2...

...ian version) We tried different things to debug the cause of this issue but we're out if ideas now. This is what we have tested so far: * Newer kernel from jessie-backports * Newer qemu-kvm from jessie-backports * Set clocksource=hpet on the hosts, this made drifts even worse (not tested yet: acpi_pm) * Tried to run guests without kvm_steal_time setting * Tried without running OpenNTPD on the guests We have some hints along our investigations. Novell for example says that CPU pinning may help on drifting guests: https://www.novell.com/support/kb/doc.php?id=7008698 Others suggested using an &q...

...ian version) We tried different things to debug the cause of this issue but we're out if ideas now. This is what we have tested so far: * Newer kernel from jessie-backports * Newer qemu-kvm from jessie-backports * Set clocksource=hpet on the hosts, this made drifts even worse (not tested yet: acpi_pm) * Tried to run guests without kvm_steal_time setting * Tried without running OpenNTPD on the guests We have some hints along our investigations. Novell for example says that CPU pinning may help on drifting guests: https://www.novell.com/support/kb/doc.php?id=7008698 Others suggested using an &q...