From mboxrd@z Thu Jan 1 00:00:00 1970 From: Valtteri Kiviniemi Subject: Re: Latest unstable detects cpu speed incorrectly Date: Tue, 27 Oct 2009 17:51:08 +0200 Message-ID: <4AE716EC.5090508@dataproof.fi> References: <4AE71636.6010009@dataproof.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4AE71636.6010009@dataproof.fi> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org 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" >> >> 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@lists.xensource.com >> http://lists.xensource.com/xen-devel >