From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: kvm-kmod.git Date: Mon, 01 Jun 2009 20:01:21 +0300 Message-ID: <4A240961.4060303@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> 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]:45623 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751653AbZFARBV (ORCPT ); Mon, 1 Jun 2009 13:01:21 -0400 In-Reply-To: <20090601165336.GA6411@us.ibm.com> Sender: kvm-owner@vger.kernel.org List-ID: Ryan Harper wrote: >>> I also wonder what happens if one tries to build on >>> a machine with kvm built into kernel. Ideally one would get >>> a clear error message. >>> >>> >> kvm-kmod is really designed for those running on pre-kvm distro kernels, >> and for those testing newer kvm versions on distro kernels. If you can >> compile your own kernel, download kvm.git and run that. >> > > So no way of having kvm-kmod sync in kvm.git bits and still build > against the current running kernel? > We must be miscommunicating, what you describe is kvm-kmod.git's sole purpose in life. > I wanted to test out 2.6.29-maint kernel modules and in > kvm-userspace/kernel, I could checkout maint/2.6.29 in kvm.git and then > make LINUX= sync. I couldn't quite figure out how to do that with > kvm-kmod since when I do a ./configure --kerneldir -- it's building > modules *for* whatever kernel is at kerneldir rather than just syncing > in the kvm bits from that kerneldir and then building modules against > the running kernel. > 'make sync' will copy the kvm bits from the linux-2.6 directory, or $(LINUX) if you specify that to make. So: LINUX= is for the kvm sources (further controlled by whatever branch is checked out) --kerneldir= is for the host kernel > 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. -- error compiling committee.c: too many arguments to function