Hello, I have just upgraded my VM from etch to lenny, and things look good overall. One annoyance however is that on a reboot, the clock is ~30 mins in the future and this is only fixed by a CRON @reboot job of "ntpdate", which adjusts this correctly (offset -1935.350400 sec). However, this large adjustment causes dovecot to kill itself. On boot (via console) I can see : .. drivers/rtc/hctosys.c: unable to open rtc device (rtc0) .. Waiting for /dev to be fully populated...done. Setting the system clock. Unable to set System Clock to: Thu Jan 21 15:01:46 UTC 2010 (warning). .. Setting the system clock. Unable to set System Clock to: Thu Jan 21 15:01:49 UTC 2010 (warning). Cleaning up ifupdown.... ... This is using lenny kernel 2.6.26-2-xen-686. I tried setting "xen.independent_wallclock = 1" in /etc/sysctl.conf but this does not make a difference. hwclock --show returns nothing. Any idea why the clock needs such a large adjustment on reboot? Cheers, -- Alastair Sherringham