From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: kvm-kmod.git Date: Mon, 01 Jun 2009 21:17:54 +0300 Message-ID: <4A241B52.3070501@redhat.com> References: <49F5A5DD.4090504@redhat.com> <20090428102030.GB24494@redhat.com> <49F6D96C.1060809@redhat.com> <20090428103409.GC24494@redhat.com> <49F6E026.9020409@redhat.com> <20090601165336.GA6411@us.ibm.com> <4A240961.4060303@redhat.com> <20090601180057.GB6411@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Michael S. Tsirkin" , KVM list To: Ryan Harper Return-path: Received: from mx2.redhat.com ([66.187.237.31]:47989 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751658AbZFASRq (ORCPT ); Mon, 1 Jun 2009 14:17:46 -0400 In-Reply-To: <20090601180057.GB6411@us.ibm.com> Sender: kvm-owner@vger.kernel.org List-ID: Ryan Harper wrote: >> So: >> LINUX= is for the kvm sources (further controlled by whatever branch >> is checked out) >> --kerneldir= is for the host kernel >> > > Ah, excellent, I didn't see it documented on the Code page of the wiki > and I blindly assumed that it went away. Thanks for correction. > It actually did go away, but Jan brought it back. >>> The reason I'm digging is that I'm seeing 64-bit migration failing on >>> maint/2.6.29 kvm modules, but not on upstream kvm kernel bits and I >>> wanted to bisect to find where 64-bit migration is fixed so I can >>> suggest what to pull into maint/2.6.29. >>> >>> >> Thanks, that's helpful. How does it fail? maybe I can supply an >> educated guess. >> > > Migration succeeds, but source and target are frozen (though monitor of > guest is still interactive. > > Nothing interesting in host dmesg, and of course no output from either > guest (they seemed locked). Reproduced this sort of hang for any number > of guests (RHEL4u7/8, SLES10 SP2, SLES11, Win2k3-r2, win2k8, etc.) as > long as they are 64-bit > SMP? Uniprocessor? Try 'info registers' on both source and target and compare. Maybe we lose some bit in EFER. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.