From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo Tosatti Subject: Re: [Qemu-devel] [PATCH] kvmclock: Ensure time in migration never goes backward Date: Mon, 5 May 2014 20:31:48 -0300 Message-ID: <20140505233148.GB23113@amt.cnet> References: <1399297882-3444-1-git-send-email-agraf@suse.de> <5367CE81.6030506@beyond.pl> <5367D7BC.2040705@beyond.pl> <20140505232710.GB20638@amt.cnet> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Alexander Graf , "qemu-devel@nongnu.org" , "kvm@vger.kernel.org" To: Marcin =?utf-8?Q?Gibu=C5=82a?= Return-path: Received: from mx1.redhat.com ([209.132.183.28]:22787 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933286AbaEEXcH (ORCPT ); Mon, 5 May 2014 19:32:07 -0400 Content-Disposition: inline In-Reply-To: <20140505232710.GB20638@amt.cnet> Sender: kvm-owner@vger.kernel.org List-ID: Marcin, Can you provide detailed instructions on how to reproduce the problem?=20 Thanks On Mon, May 05, 2014 at 08:27:10PM -0300, Marcelo Tosatti wrote: > On Mon, May 05, 2014 at 08:26:04PM +0200, Marcin Gibu=C5=82a wrote: > > >>is it possible to have kvmclock jumping forward? > > >> > > >>Because I've reproducible case when at about 1 per 20 vm restores= , VM freezes for couple of hours and then resumes with date few hundred= s years ahead. Happens only with kvmclock. > > >> > > >>And this patch seems to fix very similar issue so maybe it's all = the same bug. > > > > > >I'm fairly sure it is the exact same bug. Jumping backward is like= jumping forward by a biiiiig amount :) > >=20 > > Hi, > >=20 > > I've tested your path on my test VM... don't know if it's pure luck > > or not, but it didn't hang with over 70 restores. > >=20 > > The message "KVM Clock migrated backwards, using later time" fires > > every time, but VM is healthy after resume. >=20 > What is the host clocksource? (cat > /sys/devices/system/clocksource/clocksource0/current_clocksource).=20 >=20 > And kernel version? >=20