Bug#674907: severity
On 1 October 2012 21:01, Thomas Goirand <thomas@goirand.fr> wrote:
> On 10/01/2012 09:21 PM, Bastian Blank wrote:
>>
>> Please don't top-post.
>>
>> On Mon, Oct 01, 2012 at 02:42:54PM +0200, Pierre Colombier wrote:
>>>
>>> - Unreliable Time affects all the system and can make the whole host
>>> useless. At least for production use.
>>
>>
>> Still the system.
>>
>>> - Is "just" broken for all my 53 physical servers with different
>>> hardware. (with 2 or 3 server "shift" per week on the whole cluster.)
>>
>>
>> So? Since when is it broken? Squeeze was released 1.5 years ago and
>> noone mentioned a problem before this bug report was filed. This are
>> identical or mostly identical servers?
>>
>>> so, I think I'am not playing with words on the severity definition.
>>
>>
>> Right now it seems to only affect two users.
>>
>> Bastian
>
>
> Pierre,
>
> Have you tried using independent wallclock and the ntp daemon on your domUs?
http://my.opera.com/marcomarongiu/blog/2011/01/05/independent-wallclock-in-xen-4
It seems that independent wallclock is not supported anymore.
Reply to: