From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shahzad Chohan Subject: Re: Setting the date not working in xen Date: Fri, 29 Jul 2005 12:43:00 +0100 Message-ID: <36967cc9050729044361f8b093@mail.gmail.com> References: Reply-To: Shahzad Chohan 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-users-bounces@lists.xensource.com Errors-To: xen-users-bounces@lists.xensource.com To: Ian Pratt Cc: xen-devel@lists.xensource.com, Franck , ian.pratt@cl.cam.ac.uk, xen-users@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 7/29/05, Ian Pratt wrote: > > echo 1 > /proc/sys/xen/independent_wallclock > > ntpdate ntp0.oleane.net >=20 > 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 > has worked out a little differently from what we imagined way back, and > some of the defaults are probably wrong. >=20 > Ian I think we should change the defaults. Its quite common to use ntpdate. Does it make a lot of difference if the change is made, what does it affect? In addition to this I'd say alos include iptables in the xenU kernel build, I feel its quite a necessity. Yes it might make the kernel larger but does that really create aproblem in todays hardware world. Shaz