From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicholas Lee Subject: Re: [Xen-users] Setting the date not working in xen Date: Sat, 30 Jul 2005 10:22:33 +1200 Message-ID: <2b6116b305072915227ddf4ae0@mail.gmail.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Pratt Cc: xen-devel@lists.xensource.com, Franck , xen-users@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 7/29/05, Ian Pratt wrote: > independent_wallclock=3D1 on the kernel command line should fix this too. >=20 > Should we change the default? I guess today's common usage model for Xen No. The hardware time and syncing this to UTC is a function of the system, not the instances. Why have n ntpd daemons running when one is sufficent? I think "independent_wallclock=3D1" should be the special case, when someone wants to change the instance's view of UTC. Personally I've simply removed the ntpdate/ntpd package from my domU init packages. --=20 Nicholas Lee http://stateless.geek.nz gpg 8072 4F86 EDCD 4FC1 18EF 5BDD 07B0 9597 6D58 D70C