[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] xen power management
I don't know much, is http://wiki.xen.org/wiki/Xen_power_management helpful? I suspect some dom0 kernel options need to be enabled relating to PM and cpufreq even in Xen mode (i.e. to propagate ACPI info to the h/v). In particular if you are using an upstream paravirt ops kernel this may require you to have a new enough version, but again I don't know the specifics of what "new enough" means here. Posting details of the versions you are running and the config might trigger someone's memory perhaps. Ian. On Wed, 2014-12-03 at 04:09 +0100, lee wrote: > Nobody knows? Is power management broken? > > > lee <lee@xxxxxxxxxxx> writes: > > > Hi, > > > > what could I do the get power management to work? > > > > > > root@heimdall:~# xenpm get-cpufreq-states all > > root@heimdall:~# xenpm get-cpufreq-para all > > [CPU0] failed to get cpufreq parameter > > [CPU1] failed to get cpufreq parameter > > [CPU2] failed to get cpufreq parameter > > [CPU3] failed to get cpufreq parameter > > [CPU4] failed to get cpufreq parameter > > [CPU5] failed to get cpufreq parameter > > [CPU6] failed to get cpufreq parameter > > [CPU7] failed to get cpufreq parameter > > root@heimdall:~# xenpm get-cpu-topology all > > CPU core socket node > > CPU0 0 1 0 > > CPU1 1 1 0 > > CPU2 2 1 0 > > CPU3 3 1 0 > > CPU4 0 0 0 > > CPU5 1 0 0 > > CPU6 2 0 0 > > CPU7 3 0 0 > > root@heimdall:~# xenpm set-scaling-governor ondemand all > > failed to set governor name > > root@heimdall:~# > > > > > > 'xenpm get-cpuidle-states all' gives some output and says "total C-states : > > 2". The CPUs are L5420s. > > > > > > xen-4.1-amd64.gz placeholder dom0_mem=1024M,max:1024M dom0_max_vcpus=2 > > cpufreq=xen cpuidle hpetbroadcast > _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxx http://lists.xen.org/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |