From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:44358) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WhMyj-0005es-H2 for qemu-devel@nongnu.org; Mon, 05 May 2014 13:47:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WhMyc-0004zT-1i for qemu-devel@nongnu.org; Mon, 05 May 2014 13:47:01 -0400 Received: from mx.beyond.pl ([92.43.117.49]:35512) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WhMyb-0004z4-RG for qemu-devel@nongnu.org; Mon, 05 May 2014 13:46:53 -0400 Message-ID: <5367CE81.6030506@beyond.pl> Date: Mon, 05 May 2014 19:46:41 +0200 From: =?UTF-8?B?TWFyY2luIEdpYnXFgmE=?= MIME-Version: 1.0 References: <1399297882-3444-1-git-send-email-agraf@suse.de> In-Reply-To: <1399297882-3444-1-git-send-email-agraf@suse.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] kvmclock: Ensure time in migration never goes backward List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: agraf@suse.de Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org W dniu 2014-05-05 15:51, Alexander Graf pisze: > When we migrate we ask the kernel about its current belief on what the guest > time would be. However, I've seen cases where the kvmclock guest structure > indicates a time more recent than the kvm returned time. Hi, 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 hundreds years ahead. Happens only with kvmclock. And this patch seems to fix very similar issue so maybe it's all the same bug. -- mg