2.6.38 fixes it and cpufreq scaling works as expected.
As I did not find a precompiled 2.6.38 Dom0 kernel, I just took
linux-image-2.6.38-1-amd64 from sid (obviously that one lacks the Dom0 backend
drivers for supporting DomUs, but it is still capable of running as a Xen Dom0
by itself - so e.g. xm dmesg shows clearly that the kernel is running on the
hypervisor, but xm create fails due to missing kernel support).
So the bug was introduced somewhere between 2.6.25 and 2.6.31 and fixed
somewhere between 2.6.33 and 2.6.38.
> Seems like this is a regression bug in the kernel:
> I installed linux-{image,ubuntu-modules}-2.6.24-28-xen from Ubuntu 8.04
> and cpufreq=dom0-kernel worked exactly as expected (i.e. the Dom0 kernel does
> cpufreq scaling in exactly the same way it would if it were running
> natively).
> I also tried linux-{image,modules}-2.6.26-2-xen-amd64 from Debian Lenny,
> but unfortunately that one lacks the cpufreq modules.
--
NEU: FreePhone - kostenlos mobil telefonieren und surfen!
Jetzt informieren: http://www.gmx.net/de/go/freephone
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
