From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MDGjN-0007Kp-Nm for qemu-devel@nongnu.org; Sun, 07 Jun 2009 07:40:05 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MDGjI-0007K5-5p for qemu-devel@nongnu.org; Sun, 07 Jun 2009 07:40:04 -0400 Received: from [199.232.76.173] (port=43970 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MDGjI-0007Jx-13 for qemu-devel@nongnu.org; Sun, 07 Jun 2009 07:40:00 -0400 Received: from mx2.redhat.com ([66.187.237.31]:34783) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MDGjH-0000Ts-HF for qemu-devel@nongnu.org; Sun, 07 Jun 2009 07:39:59 -0400 Message-ID: <4A2BA708.4070004@redhat.com> Date: Sun, 07 Jun 2009 14:39:52 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: POLL: Why do you use kqemu? References: <4A2A92FE.2010700@redhat.com> <4A2AA10B.6060401@web.de> <4A2B49C0.8020703@redhat.com> <4A2B6DD8.3090104@web.de> <4A2B7F5E.8050807@web.de> <4A2B8787.5080603@web.de> <20090607112325.GD29048@redhat.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Blue Swirl Cc: =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= , Jan Kiszka , "qemu-devel@nongnu.org" , Gleb Natapov Blue Swirl wrote: > On 6/7/09, Gleb Natapov wrote: > >> On Sun, Jun 07, 2009 at 02:13:15PM +0300, Blue Swirl wrote: >> > kvm-kmod seems to be available only for x86, not amd64. This is not >> > mentioned in README (in fact, there is no README), configure will >> > succeed and make will only generate funky errors. I only found this >> > mentioned in http://www.linux-kvm.org/page/Code after quite a bit of >> > head scratching. >> > >> >> Never used kvm-kmod on x86 only with x86_64. >> > > How do you compile it then, I only get so far: > $ make V=1 > make -C /lib/modules/2.6.26-2-amd64/build M=`pwd` \ > LINUXINCLUDE="-I`pwd`/include -Iinclude \ > \ > -Iarch/x86/include -I`pwd`/include-compat \ > -include include/linux/autoconf.h \ > -include `pwd`/x86/external-module-compat.h " \ > "$@" > make[1]: Entering directory `/usr/src/linux-headers-2.6.26-2-amd64' > test -e include/linux/autoconf.h -a -e include/config/auto.conf || ( \ > echo; \ > echo " ERROR: Kernel configuration is invalid."; \ > echo " include/linux/autoconf.h or > include/config/auto.conf are missing."; \ > echo " Run 'make oldconfig && make prepare' on kernel > src to fix it."; \ > echo; \ > /bin/false) > mkdir -p /tmp/kvm-kmod/.tmp_versions ; rm -f /tmp/kvm-kmod/.tmp_versions/* > make -f scripts/Makefile.build obj=/tmp/kvm-kmod > make -f scripts/Makefile.build obj=/tmp/kvm-kmod/x86 > make[3]: *** No rule to make target `/tmp/kvm-kmod/x86/svm.o', needed > by `/tmp/kvm-kmod/x86/kvm.o'. Stop. > make[2]: *** [/tmp/kvm-kmod/x86] Error 2 > make[1]: *** [_module_/tmp/kvm-kmod] Error 2 > make[1]: Leaving directory `/usr/src/linux-headers-2.6.26-2-amd64' > make: *** [all] Error 2 > What are you building, exactly? Did you load the tarball from sourceforge, or kvm-kmod from git? -- Do not meddle in the internals of kernels, for they are subtle and quick to panic.