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

[Xen-devel] Re: Problem with booting 2.6.32.16 pvops DomU

To: Carsten Schiers <carsten@xxxxxxxxxx>
Subject: [Xen-devel] Re: Problem with booting 2.6.32.16 pvops DomU
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Wed, 07 Jul 2010 08:34:26 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 07 Jul 2010 08:35:00 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <3119103.71278493658977.JavaMail.root@uhura>
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>
References: <3119103.71278493658977.JavaMail.root@uhura>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100430 Fedora/3.0.4-2.fc12 Lightning/1.0b2pre Thunderbird/3.0.4
On 07/07/2010 02:07 AM, Carsten Schiers wrote:
> Hi,
>
> I tried to boot a 64 Bit 2.6.32.16 pvops DomU from Jeremy's git on Xen 
> 3.4.4-rc1-pre 
> and 64 Bit 2.6.18.8 Dom0.
>
> It will hang very quickly after 0.5 secs and produce the following output on 
> xm dmesg:
>
> (XEN) traps.c:2230:d25 Domain attempted WRMSR 00000000c0010004 from 
> 00009310:79804ace to 00000000:00000000
>
> (XEN) traps.c:2230:d25 Domain attempted WRMSR 00000000c0010000 from 
> 00000009:0487e489 to 00000000:00430076
>   

Do you get any other console output?  Could you boot with
"earlyprink=xen" (and "console=hvc0" if you don't already) on the kernel
command line to see if any more comes out.

Those two MSRs relate to the K8 performance counter subsystem, but I
can't see any obviously relevent changes in 2.6.32.15->16 which might
cause this regression.

It might also be useful to use xenctx to work out where the hang is.

Thanks,
    J

>
> BR,
> Carsten.
>
>
>
> ----- Originalnachricht -----
> Von: Carsten Schiers <carsten@xxxxxxxxxx>
> Gesendet: Mon, 5.7.2010 11:09
> An: xen-devel@xxxxxxxxxxxxxxxxxxx
> Betreff: [Xen-devel] Question on xenpm
>
> Dear all,
>
> after having upgraded my server from AMD 4050e to X4 640, I now use 
> cpufreq=xen and had
> to adapt a munin script (monitoring tool) to display the residency in the 
> different P-states.
> This script uses /sys/device/system/cpu/cpu0/cpufreq to read out the 
> information, whereas
> I now use xenpm get-cpufreq-state.
>
> Before I noticed that the CPU is in highest possible P-state (lowest 
> frequences) nearly all 
> of the time, and a minimal percentage in the lowest. Now I can see a 50/50 
> distribution. 
> Interesting enough, the xenpm get-cpuidle-state will show that the CPUs are 
> at aprox. 90%
> in C1 idle state.
>
> Can there be a difference in how the two methods to collect the info are 
> working? I mean 
> something like xenpm will not count residency when in C1, but cpufreq driver 
> will normaly
> do?
>
> BR,
> Carsten.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>
>   


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

<Prev in Thread] Current Thread [Next in Thread>