This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] cpufreq kernel line available parameters

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] cpufreq kernel line available parameters
From: Kai Schaetzl <maillists@xxxxxxxxxxxxx>
Date: Sun, 16 Nov 2008 16:31:15 +0100
Delivery-date: Sun, 16 Nov 2008 07:32:47 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Reply-to: xen-users@xxxxxxxxxxxxxxxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I'm using the cpufreq=dom0-kernel hypervisor kernel parameter to enable 
frequency scaling on the host machines for quite some time now. Since then 
I started to get the "Time went backwards" message on AMD machines (not on 
Intel machines). It's not a big problem, so I only research it once in a 
while when I stumble upon it from yet another direction. There's no really 
good explanation/solution to be found with googling.

It seems there's at least cpufreq=dom0-kernel and cpufreq=xen. It's not 
clear in which versions these are/were available and if there are any more 
options available or one that would make this machine go away (but keep 
the frequency scaling). Can someone shed some light on this?

I'm using CentOS 5.2 with Xen 3.2.0 and 3.2.1.


Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] cpufreq kernel line available parameters, Kai Schaetzl <=