WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Clock problems with Xen 4.1 + Konrads Kernel 2.6.39.1

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Clock problems with Xen 4.1 + Konrads Kernel 2.6.39.1
From: Iain Kay <spam@xxxxxxxxxxx>
Date: Wed, 15 Jun 2011 21:59:57 +0100
Delivery-date: Wed, 15 Jun 2011 14:01:58 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hey,

I'm experiencing a strange problem with domU's on a xen host node running Xen 
4.1.0 and 2.6.39.1 kernel. The dom0 system timezone is set to UTC and the 
hardware clock is set to UTC time.

I setup the domU to use UTC for system clock and ran cp 
/usr/share/zoneinfo/Europe/London /etc/localtime.

dom0 clock currently reports: Wed Jun 15 20:57:48 UTC 2011
whilst domU clock reports: Thu Jun 16 00:57:48 BST 2011

BST should only be +1 from UTC so something is causing an extra 3 hours to jump 
on the system time.

Any ideas?

I could set dom0 time to be wrong but seems like there could be a better method 
especially when Xen 4.0.1 with the 2.6.32.x kernel was working fine.

Iain
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>