From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: Massive Instant Clock Jump & Freeze domU Issue (NOT Related to Drift, Live Migration or Saving/Restoring) Date: Tue, 23 Apr 2013 10:33:13 +0100 Message-ID: <1366709593.20256.77.camel@zakaz.uk.xensource.com> References: <5176708202000078000CFDAE@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5176708202000078000CFDAE@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: Tom W , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On Tue, 2013-04-23 at 10:29 +0100, Jan Beulich wrote: > >>> On 23.04.13 at 00:50, Tom W wrote: > > -for all dom0s & domUs: independent_wallclock=0, ntpd is running, > > clocksource=jiffies, Xen version 3.1.2 > > I can only second Ian's recommendation to drop this clocksource= > option. > > And unless this was a typo, you surely want to get off that really > old hypervisor. FWIW I had assumed this was the RHEL5/CentOS5 supplied hypervisor (it's the right era at least) and not a typo. > Nobody's going to help you with issues there, If I'm right then it would be better to start by reporting a RHEL bug IMHO. Ian.