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] Latest unstable detects cpu speed incorrectly

To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Latest unstable detects cpu speed incorrectly
From: Valtteri Kiviniemi <valtteri.kiviniemi@xxxxxxxxxxxx>
Date: Tue, 27 Oct 2009 18:14:16 +0200
Delivery-date: Tue, 27 Oct 2009 09:14:38 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4AE71BD8.9080906@xxxxxxxxxxxx>
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>
Organization: Dataproof
References: <C70CCAE6.188FD%keir.fraser@xxxxxxxxxxxxx> <4AE71BD8.9080906@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.23 (Windows/20090812)
Hi,

I'll take that back, now its occuring in every virtual.

xentop shows this:

xentop - 18:13:15   Xen 3.5-unstable
6 domains: 4 running, 0 blocked, 0 paused, 0 crashed, 0 dying, 0 shutdown
Mem: 16758480k total, 4884612k used, 11873868k free    CPUs: 8 @ 2493MHz
NAME STATE CPU(sec) CPU(%) MEM(k) MEM(%) MAXMEM(k) MAXMEM(%) VCPUS NETS NETTX(k) NETRX(k) VBDS VBD_OO VBD_RD VBD_WR SSID cvx -----r 1239 318.2 1048576 6.3 1048576 6.3 8 1 4882 2706 2 0 9308 5191 0 db ------ 33 27.6 524288 3.1 524288 3.1 8 1 1307 920 2 0 7170 518 0 Domain-0 -----r 2531 4.7 520448 3.1 no limit n/a 8 0 0 0 0 0 0 0 0 game -----r 1407 338.8 1048576 6.3 1048576 6.3 8 1 1013 1002 2 0 3770 630 0 gj ------ 375 48.0 524288 3.1 524288 3.1 8 1 0 0 2 0 0 0 0 markka -----r 14565 62.8 1048576 6.3 1048576 6.3 8 1 42202 39013 2 0 132016 122133 0


- Valtteri Kiviniemi

Valtteri Kiviniemi kirjoitti:
Hi,

I have to wait for that to occur again. There were no error messages, suddenly domU's with emulated TSC started to use a lot of CPU until they were so slow that they had to be destroyed. domU's with native tsc are working fine.

Is there any way to track down the problem?

- Valtteri Kiviniemi

Keir Fraser kirjoitti:
Haven't heard any other reports of that. Can you provide more details?

 -- Keir

On 27/10/2009 15:51, "Valtteri Kiviniemi" <valtteri.kiviniemi@xxxxxxxxxxxx>
wrote:

Hi,

Seems like that emulation is not quite working as it should be. domU's
are using all the available cpu and then they crash. I did a fallback
back to the old behaviour and the virtuals running with tsc_native=1 are
working fine.

- Valtteri Kiviniemi

Valtteri Kiviniemi kirjoitti:
Hi,

Ok, good to know. Is it always at 1GHz or can it be adjusted? Is there
some other new features different from 3.4.1 that I should know?


- Valtteri Kiviniemi

Keir Fraser kirjoitti:
On 27/10/2009 15:22, "Valtteri Kiviniemi"
<valtteri.kiviniemi@xxxxxxxxxxxx>
wrote:

We are testing the latest xen-unstable and found an interesting bug.
dom0 detects cpu speed correctly but when booting domU it detects it
incorrectly:

"Detected 1000.000 MHz processor."
TSC is emulated at that speed. If you want old behaviour then add
tsc_native=1
to your domain config file.

 -- Keir



_______________________________________________
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




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

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