WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: Carsten Schiers <carsten@xxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Xen 3.4 strange behaviour as compared to Xen 3.3.1
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Fri, 29 May 2009 16:02:18 +0100
Cc:
Delivery-date: Fri, 29 May 2009 08:02:49 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <H00000670002f628.1243605783.uhura.space.zz@MHS>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcngZlUmqdUiWsiEQb6NNdnvUZFivAACCBn7
Thread-topic: [Xen-devel] Xen 3.4 strange behaviour as compared to Xen 3.3.1
User-agent: Microsoft-Entourage/12.17.0.090302
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