From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomasz Chmielewski Subject: Re: soft lockup after live migration Date: Sun, 08 Nov 2009 12:20:24 +0100 Message-ID: <4AF6A978.5020006@wpkg.org> References: <4AE24CF4.8070405@wpkg.org> <20091024203553.GA6891@amt.cnet> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit To: Marcelo Tosatti , "kvm@vger.kernel.org" Return-path: Received: from mx03.syneticon.net ([78.111.66.105]:60614 "EHLO mx03.syneticon.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753627AbZKHLUT (ORCPT ); Sun, 8 Nov 2009 06:20:19 -0500 In-Reply-To: <20091024203553.GA6891@amt.cnet> Sender: kvm-owner@vger.kernel.org List-ID: Marcelo Tosatti wrote: > Tomasz, > > The screenshots seem to indicate a paravirt mmu problem. > > Try to patch the x86.c file from kvm kernel module with: > > diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c > - case KVM_CAP_PV_MMU: > - r = !tdp_enabled; > + case KVM_CAP_PV_MMU: /* obsolete */ > + r = 0; > > You'll probaby have to do it manually (this disables pvmmu). With this, some guests fail to start with kernel panic; some have soft lockups all the time. Some don't start at all. And generally, everything is "dead slow". -- Tomasz Chmielewski http://wpkg.org