AW: Re: [Xen-devel] Xen 3.4 strange behaviour as compared to Xen 3.3.1

["Carsten Schiers" <carsten@xxxxxxxxxx>]

Thanks Keir, I tried it out but there is no difference. And by the way: 
it
is in lowest p-state and doesn't come up, even if under heavy load. Hmm.

BR,
Carsten.

-----Ursprüngliche Nachricht-----
Von: Keir Fraser [mailto:keir.fraser@xxxxxxxxxxxxx] 
Gesendet: Freitag, 29. Mai 2009 17:02
An: Carsten Schiers; xen-devel
Betreff: Re: [Xen-devel] Xen 3.4 strange behaviour as compared to Xen 
3.3.1

On 29/05/2009 15:03, "Carsten Schiers" <carsten@xxxxxxxxxx> wrote:

>   - as already reported, ondemand manager in dom0-kernel doesn't step,
> manual
>     setting works so it seems a bit like the communication between 
dom0
> and
>     hypervisor regarding idle time is not working

Could be an interaction with C-state support, preferring deep sleep to
running at lower voltage/frequency? You could try no-cpuidle on Xen's
command line at boot time and see if that changes things.

 -- Keir

>   - all beside one domu use Xen 3.4.0 kernel, the one who uses it's
> customized
>     kernel won't start up as first domu. It simply hangs and this
> prevents also
>     all other domus (I all auto start them, no save/restore) don't 
come
> up. When
>     I start the chain with a different one and this (with the 
different
> kernel)
>     is started as #2 or #3, not problem
> 
>   - one domu is for vdr with three dvb pci cards passed trough. This
> one, when
>     started as the first one, will cause xentop to show 20% load. When
> restarted
>     or started as #2, the load is like with 3.3.1 at roughly 3-5%.





_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel