From: freisei <forum@xp8.de>
To: kvm@vger.kernel.org
Subject: compile problems userspace-tools from git on ubuntu intrepid 8.10 x64
Date: Wed, 04 Mar 2009 08:43:43 +0100 [thread overview]
Message-ID: <49AE312F.3050604@xp8.de> (raw)
Hi @ll,
I want to update my kvm-84 to the latest git releaste due to an
IOMMU-feature.
git clone git://git.kernel.org/pub/scm/virt/kvm/kvm-userspace.git
Problem: kvm support no - (#error Missing KVM capability
KVM_CAP_DESTROY_MEMORY_REGION_WORKS)
--------------------
root@xp8main3:/usr/local/src/kvm-userspace# ./configure
Install prefix /usr/local
BIOS directory /usr/local/share/qemu
binary directory /usr/local/bin
Manual directory /usr/local/share/man
ELF interp prefix /usr/gnemul/qemu-%M
Source path /usr/local/src/kvm-userspace/qemu
C compiler gcc
Host C compiler gcc
ARCH_CFLAGS -m64
make make
install install
host CPU x86_64
host big endian no
target list x86_64-softmmu
gprof enabled no
sparse enabled no
profiler no
static build no
-Werror enabled no
SDL support yes
SDL static link yes
curses support yes
mingw32 support no
Audio drivers oss
Extra audio cards ac97 es1370 sb16
Mixer emulation no
VNC TLS support no
kqemu support no
kvm support no - (#error Missing KVM capability
KVM_CAP_DESTROY_MEMORY_REGION_WORKS)
CPU emulation yes
brlapi support no
Documentation no
NPTL support yes
vde support no
AIO support yes
Install blobs yes
KVM support no - (#error Missing KVM capability
KVM_CAP_DESTROY_MEMORY_REGION_WORKS)
fdt support no
--------------------
"./configure --with-patched-kernel": same error
i´ve changed the code to give me the var "kerneldir" - i think it´s
correct: "kerneldir: /lib/modules/2.6.29-rc6-xp8no7/build"
then
got newest KVM-Kernel with git clone
git://git.kernel.org/pub/scm/linux/kernel/git/avi/kvm.git and
compiled/installed it the debian/ubuntu way
var "kerneldir" - i think it´s correct: "kerneldir:
/lib/modules/2.6.29-rc6-xp8no8/build"
root@xp8main3:/usr/local/src/kvm-userspace# ls -la
/lib/modules/2.6.29-rc6-xp8no8/build
lrwxrwxrwx 1 root root 29 2009-03-02 11:08
/lib/modules/2.6.29-rc6-xp8no8/build -> /usr/local/src/linux-kvm-git/
root@xp8main3:/usr/local/src/kvm-userspace# ls /usr/local/src/linux-kvm-git/
arch drivers MAINTAINERS samples
stamp-indep-conf
block firmware Makefile scripts
stamp-kernel-headers
config.kbuild fs mm security
stamp-kernel-image
conf.vars include Module.markers sound System.map
COPYING init modules.order stamp-arch-conf usr
CREDITS ipc Module.symvers stamp-configure virt
crypto Kbuild net stamp-configure-arch vmlinux
debian kernel README stamp-configure-indep vmlinux.o
Documentation lib REPORTING-BUGS stamp-debian
looks good, i think. but even the same error:
I think the configure method doesn´t recognize that i HAVE a kernel with
"CAP_DESTROY_MEMORY_REGION_WORKS"
found line 1029 in qemu/configure
#include <linux/kvm.h>
which kvm.h is tested here?
must be this? root@xp8main3:/usr/local/src/kvm-userspace#
../linux-kvm-git/include/linux/kvm.h
found this lines:
/* Bug in KVM_SET_USER_MEMORY_REGION fixed: */
#define KVM_CAP_DESTROY_MEMORY_REGION_WORKS 21
I found it but not the qemu/configure....
Any suggestions?
System is Ubuntu 8.10 x64
greets freisei
next reply other threads:[~2009-03-04 7:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 7:43 freisei [this message]
2009-03-05 2:54 ` compile problems userspace-tools from git on ubuntu intrepid 8.10 x64 Zhang, Xiantao
2009-03-05 6:12 ` Freisei
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=49AE312F.3050604@xp8.de \
--to=forum@xp8.de \
--cc=kvm@vger.kernel.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