gpg: Signature made Tue Feb 16 19:41:16 2010 UTC using DSA key ID BF15490B
gpg: Good signature from "Andy Smith <andy@strugglers.net>"
gpg: aka "Andrew James Smith <andy@strugglers.net>"
gpg: aka "Andy Smith (UKUUG) <andy.smith@ukuug.org>"
gpg: aka "Andy Smith (BitFolk Ltd.) <andy@bitfolk.com>"
gpg: aka "Andy Smith (Linux User Groups UK) <andy@lug.org.uk>"
gpg: aka "Andy Smith (Cernio Technology Cooperative) <andy.smith@cernio.com>"
Hi Joseph,
On Tue, Feb 16, 2010 at 07:18:37PM +0000, Joseph Heenan wrote:
> I'm not entirely sure I am seeing the same thing as Alistair. At least
> one of the things I see is two 'Unable to set System clock' messages
> whilst the VPS is booting - though I now see they're happening before
> independent_wallclock gets set:
That's where the usual boot scripts attempt to read the hardware
clock (i.e. the BIOS) to get the system time from it. Xen
paravirtual machines don't have hardware clocks so this always
fails, and is harmless.
As long as you have xen.independent_wallclock set to 1 then you
should be able to set your clock yourself. If you don't then you
won't be able to change it at all. It will just fail silently.
I recommend that you set that to 1, run ntpd and put in a support
ticket to support@??? for me to monitor your ntpd for you.
You'll know then if it ever loses sync.
I do find that the clock is sometimes set oddly after boot or after
a suspend/restore, but I am able to fix it with ntpdate and keep it
synced with ntpd.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
