From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mauro Subject: Re: [Xen-devel] Xen 4 TSC problems Date: Sat, 29 Sep 2012 14:19:55 +0200 Message-ID: References: <68c41dd8-9195-41b0-83d7-9242b8eff809@default> <65395f62-74e5-4910-b701-8df629c2ce3b@default> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org To: Olivier Hanesse Cc: Dan Magenheimer , xen-devel@lists.xensource.com, Keir Fraser , Jeremy Fitzhardinge , Jan Beulich , Keir Fraser , Xen Users , Mark Adams List-Id: xen-devel@lists.xenproject.org It's happened another time, system date 50 minutes ahead. There is really no solution? root@xen-p02:~# date sab 29 set 2012, 15.06.25, CEST root@xen-p02:~# hwclock --debug hwclock from util-linux-ng 2.17.2 Using /dev interface to clock. Last drift adjustment done at 1348816781 seconds after 1969 Last calibration done at 1348816781 seconds after 1969 Hardware clock is on UTC time Assuming hardware clock is kept in UTC time. Waiting for clock tick... ...got clock tick Time read from Hardware Clock: 2012/09/29 12:16:58 Hw clock time : 2012/09/29 12:16:58 = 1348921018 seconds since 1969 sab 29 set 2012 14:16:58 CEST -0.751536 seconds root@xen-p02:~# hwclock --show sab 29 set 2012 14:17:12 CEST -0.423643 seconds