From: Ingmar Schraub <is@eseco.de>
To: Avi Kivity <avi@redhat.com>
Cc: KVM list <kvm@vger.kernel.org>
Subject: problem with kvm-85 release
Date: Tue, 21 Apr 2009 17:14:37 +0200 [thread overview]
Message-ID: <49EDE2DD.1040501@eseco.de> (raw)
Hello,
I have a problem with this release version (qemu-kvm-devel-85) when
running ./configure
It shows me a problem with KVM support. Last version I tried was 85-rc3
and I haven't had this problem. Please see below:
ingmar@nexoc:~/downloads/KVM/qemu-kvm-devel-85> ./configure --disable-bluez
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 /home/ingmar/downloads/KVM/qemu-kvm-devel-85/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
strip binaries yes
profiler no
static build no
-Werror enabled no
SDL support yes
SDL static link yes
curses support no
mingw32 support no
Audio drivers oss
Extra audio cards ac97 es1370 sb16
Mixer emulation no
VNC TLS support no
VNC SASL support yes
SASL CFLAGS
SASL LIBS -lsasl2
kqemu support no
kvm support no - (field 'arch' has incomplete type, field 'arch'
has incomplete type)
CPU emulation yes
brlapi support no
Documentation yes
NPTL support yes
vde support yes
AIO support yes
Install blobs yes
KVM support no - (field 'arch' has incomplete type, field 'arch'
has incomplete type)
fdt support no
preadv support no
On the other hand 85rc3 shows me:
ingmar@nexoc:~/downloads/KVM/qemu-kvm-devel-85rc3> ./configure
--disable-bluez
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 /home/ingmar/downloads/KVM/qemu-kvm-devel-85rc3/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
strip binaries yes
profiler no
static build no
-Werror enabled no
SDL support yes
SDL static link yes
curses support no
mingw32 support no
Audio drivers oss
Extra audio cards ac97 es1370 sb16
Mixer emulation no
VNC TLS support no
VNC SASL support yes
SASL CFLAGS
SASL LIBS -lsasl2
kqemu support no
kvm support yes
CPU emulation yes
brlapi support no
Documentation yes
NPTL support yes
vde support yes
AIO support yes
Install blobs yes
KVM support yes
fdt support no
I am running opensuse 11.0 64bit on an Intel(R) Core(TM)2 Extreme CPU
X7900 @ 2.80GHz
Thanks, Ingmar
next reply other threads:[~2009-04-21 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 15:14 Ingmar Schraub [this message]
2009-04-22 2:50 ` problem with kvm-85 release Zhang, Xiantao
2009-04-22 7:04 ` Ingmar Schraub
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=49EDE2DD.1040501@eseco.de \
--to=is@eseco.de \
--cc=avi@redhat.com \
--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