Re: Latest unstable detects cpu speed incorrectly

[Jeremy Fitzhardinge <jeremy@goop.org>]

On 10/27/09 08:51, Valtteri Kiviniemi 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.

What kind of domUs are they?  Windows? Linux?  HVM?  PV?  What versions?

    J

>
> - 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@dataproof.fi>
>>> 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
>>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>