So what's the algorithm? If the time changes by more than half an hour (between the heartbeat sampling the clock) it's a clock change but if its less than half an hour its clock drift. What threshold value would you use? 10 minutes? Half an hour? A minute? I'm interested in opinions here This is easy to add and a good idea, but getting that magic constant right is important.<br>
<br><div class="gmail_quote">On Wed, Jan 12, 2011 at 4:24 AM, Igor Stasenko <span dir="ltr"><<a href="mailto:siguctua@gmail.com">siguctua@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Well, putting the CMOS stuff aside,<br>
i really don't like that VM could hang indefinitely if user will<br>
adjust the clock settings.<br>
<div><div></div><div class="h5"><br>
On 12 January 2011 13:22, Levente Uzonyi <<a href="mailto:leves@elte.hu">leves@elte.hu</a>> wrote:<br>
><br>
> On Wed, 12 Jan 2011, Frank Shearar wrote:<br>
><br>
>><br>
>> Yes, Windows like to set the CMOS clock to local time, and Linux likes to<br>
>> use UTC.<br>
>><br>
>> My brother recently ran into a similar problem with a FreeBSD machine<br>
>> running as a guest inside a Windows host. He had to touch<br>
>> /etc/wall_cmos_clock to fix it.<br>
>><br>
>> From the adjkerntz man page:<br>
>><br>
>> If the file /etc/wall_cmos_clock exists, it means that CMOS clock keeps<br>
>> local time (MS-DOS and MS-Windows compatible mode). If that file does not<br>
>> exist, it means that the CMOS clock keeps UTC time.<br>
>><br>
>> Maybe there's a similar Linux/Mac fix?<br>
><br>
> Yes, there is, but different linux distributions have different files IIRC.<br>
> Btw, if you tell linux to assume that the hardware clock stores the local<br>
> time, you'll still have problems after daylight saving related time changes,<br>
> because both OSs will adjust the clock.<br>
><br>
><br>
> Levente<br>
><br>
>><br>
>> frank<br>
>><br>
>> On 2011/01/12 01:18, Chris Muller wrote:<br>
>>><br>
>>> Every time I jump back and forth from Windows to Linux on my primary<br>
>>> laptop, the clock is wrong...<br>
>>><br>
>>> On Tue, Jan 11, 2011 at 4:37 PM, Igor Stasenko<<a href="mailto:siguctua@gmail.com">siguctua@gmail.com</a>><br>
>>> wrote:<br>
>>>><br>
>>>> Yesterday on my comp two separate running images are hung<br>
>>>> simultaneously, while i were doing something completely outside of<br>
>>>> them.<br>
>>>><br>
>>>> And now during reading the sqUnixHeartBeat.c:<br>
>>>><br>
>>>><br>
>>>> /* The native clock may go backwards, e.g. due to NTP<br>
>>>> adjustments, although<br>
>>>> * why it can't avoid small backward steps itself, I don't know.<br>
>>>> Simply<br>
>>>> * ignore backward steps and wait until the clock catches up<br>
>>>> again. Of<br>
>>>> * course this will cause problems if the clock is manually<br>
>>>> adjusted. To<br>
>>>> * which the doctor says, "don't do that".<br>
>>>> */<br>
>>>><br>
>>>> i start recalling that yesterday i adjusted clock back by 1 hour,<br>
>>>> because after installing a windoze in dual boot it was set it wrongly.<br>
>>>><br>
>>>> But of course it could be anything else :)<br>
>>>><br>
>>>> --<br>
>>>> Best regards,<br>
>>>> Igor Stasenko AKA sig.<br>
>>>><br>
>>><br>
>>><br>
>><br>
>><br>
><br>
<br>
<br>
<br>
</div></div>--<br>
<div><div></div><div class="h5">Best regards,<br>
Igor Stasenko AKA sig.<br>
</div></div></blockquote></div><br>