[Gllug] Hardware problems / good replacements

[Phil Reynolds]

On 11/02/12 19:40, James Courtier-Dutton wrote:
> On 10 February 2012 22:40, Phil Reynolds <phil-gllug at tinsleyviaduct.com> wrote:
>> Hmmm... how could I check for a system timer problem?
>>
> 
> How far does it get in the boot process? Does it get as far as the command line?

Yes, always did even before the recent improvements.

> Start with a PC that is keeping accurate time that you trust, using ntpd.
> One way to check the timer is to just type "date" at the command line
> in the VM and compare it the other trusted machine. Note the
> difference, to the nearest second or two.
> Then, wait about 10 mins and try it again, and see how far out it is that time.
> If the difference is the same both times, you don't have a timer
> problem, if the time is out, then there is your problem.
> On problem machines, I saw the time drifting out by more than 10
> seconds over a 10 minute period, so it is easy to spot.
> If the time is your problem, you need to look at virtualised
> clock-source drivers for inside the VM.

When I next actually see a problem, or when I finish my current round of
bringing my VMs up to date (they are all roughly six months out of date
at present), I will try this test. Thanks for the hint, though if it
does prove a problem, I am not sure how to deal with the fix.

-- 
Phil Reynolds
mail: phil-gllug at tinsleyviaduct.com
--
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug