From mboxrd@z Thu Jan  1 00:00:00 1970
From: Matt Mullins <mmullins+lkml@tuxags.com>
Subject: Re: Live migration locks up 3.2 guests in do_timer(ticks ~ 500000)
Date: Mon, 27 Oct 2014 11:42:16 -0700
Message-ID: <20141027184216.GA29098@hydra.tuxags.com>
References: <20140908055416.GE23305@hydra.tuxags.com>
 <540D663E.2070905@redhat.com>
 <20140908155642.GF23305@hydra.tuxags.com>
 <540DD6E6.70409@redhat.com>
 <20140910065349.GM23305@hydra.tuxags.com>
 <20140915181441.GN23305@hydra.tuxags.com>
 <5417F801.20408@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: kvm@vger.kernel.org
To: Paolo Bonzini <pbonzini@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from hydra.tuxags.com ([64.13.172.54]:38416 "EHLO mail.tuxags.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751977AbaJ0Sts (ORCPT <rfc822;kvm@vger.kernel.org>);
	Mon, 27 Oct 2014 14:49:48 -0400
Content-Disposition: inline
In-Reply-To: <5417F801.20408@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Tue, Sep 16, 2014 at 10:42:41AM +0200, Paolo Bonzini wrote:
> Il 15/09/2014 20:14, Matt Mullins ha scritto:
> > I'm not really sure what to look at from here.  I suppose leaving kvmclock
> > disabled is a workaround for now, but is there a major disadvantage to doing
> > so?
> 
> Sorry for not following up.  I think we have QEMU patches to fix this
> issue.  I'll reply as soon as they are available in a git tree.

Do you have any more information on the fix?  Are there any downsides if I
disable kvmclock for my guests instead?