From: Blue Swirl <blauwirbel@gmail.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: "Andreas Färber" <andreas.faerber@web.de>,
"Jan Kiszka" <jan.kiszka@web.de>, "Avi Kivity" <avi@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Re: POLL: Why do you use kqemu?
Date: Sun, 7 Jun 2009 14:26:46 +0300 [thread overview]
Message-ID: <f43fc5580906070426v65094452t8154df13cf1a7047@mail.gmail.com> (raw)
In-Reply-To: <20090607112325.GD29048@redhat.com>
On 6/7/09, Gleb Natapov <gleb@redhat.com> 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
next prev parent reply other threads:[~2009-06-07 11:26 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 21:57 [Qemu-devel] POLL: Why do you use kqemu? Anthony Liguori
2009-06-04 16:55 ` Anton D Kachalov
2009-06-05 0:44 ` Johannes Schindelin
2009-06-05 7:45 ` Gerd Hoffmann
2009-06-05 8:40 ` Tomasz Chmielewski
2009-06-05 9:08 ` Anton D Kachalov
2009-06-05 9:15 ` Gerd Hoffmann
2009-06-05 20:14 ` Lennart Sorensen
2009-06-05 23:23 ` Johannes Schindelin
2009-06-08 0:13 ` Jamie Lokier
2009-06-08 5:59 ` Avi Kivity
2009-06-08 11:57 ` Jamie Lokier
2009-06-08 12:03 ` Avi Kivity
2009-06-08 12:16 ` Jamie Lokier
2009-06-08 12:28 ` Avi Kivity
2009-06-08 12:44 ` [Qemu-devel] " Jan Kiszka
2009-06-08 13:06 ` Avi Kivity
2009-06-08 13:18 ` Jan Kiszka
2009-06-08 13:24 ` Avi Kivity
2009-06-08 13:44 ` Jan Kiszka
2009-06-08 14:03 ` Avi Kivity
2009-06-08 12:36 ` Jan Kiszka
2009-06-08 18:25 ` [Qemu-devel] " Lennart Sorensen
2009-06-06 13:27 ` Andreas Färber
2009-06-06 16:02 ` Avi Kivity
2009-06-06 16:29 ` Blue Swirl
2009-06-06 17:02 ` [Qemu-devel] " Jan Kiszka
2009-06-06 17:25 ` Blue Swirl
2009-06-06 17:32 ` Jan Kiszka
2009-06-06 19:15 ` Andreas Färber
2009-06-07 5:43 ` Avi Kivity
2009-06-07 5:01 ` Avi Kivity
2009-06-07 7:35 ` Jan Kiszka
2009-06-07 7:46 ` Avi Kivity
2009-06-07 8:33 ` Blue Swirl
2009-06-07 8:50 ` Jan Kiszka
2009-06-07 9:01 ` Blue Swirl
2009-06-07 9:25 ` Jan Kiszka
2009-06-07 9:37 ` Avi Kivity
2009-06-07 9:47 ` Jan Kiszka
2009-06-07 9:52 ` Avi Kivity
2009-06-07 9:56 ` Jan Kiszka
2009-06-07 10:06 ` Avi Kivity
2009-06-07 11:13 ` Blue Swirl
2009-06-07 11:23 ` Gleb Natapov
2009-06-07 11:26 ` Blue Swirl [this message]
2009-06-07 11:29 ` Gleb Natapov
2009-06-07 11:39 ` Avi Kivity
2009-06-07 12:40 ` Blue Swirl
2009-06-07 12:43 ` Avi Kivity
2009-06-07 12:52 ` Gleb Natapov
2009-06-07 12:56 ` Avi Kivity
2009-06-07 13:18 ` Blue Swirl
2009-06-07 13:35 ` Jan Kiszka
2009-06-07 13:35 ` Avi Kivity
2009-06-07 18:37 ` Anthony Liguori
2009-06-07 18:40 ` Blue Swirl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f43fc5580906070426v65094452t8154df13cf1a7047@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=andreas.faerber@web.de \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=jan.kiszka@web.de \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).