From: Johannes Bauer <dfnsonfsduifb@gmx.de>
To: David Ahern <dsahern@gmail.com>
Cc: Gleb Natapov <gleb@redhat.com>, Avi Kivity <avi@redhat.com>,
kvm@vger.kernel.org
Subject: Re: KVM entry failed, hardware error
Date: Wed, 06 Jun 2012 20:19:24 +0200 [thread overview]
Message-ID: <4FCF9F2C.2070501@gmx.de> (raw)
In-Reply-To: <4FCE10D7.8060707@gmail.com>
On 05.06.2012 15:59, David Ahern wrote:
> You need to install the plugins for trace-cmd:
> make install_plugins
>
> you could also try setting:
> export TRACE_CMD_PLUGIN_DIR=/path/to/plugins
Aha, with that I get more messages:
trace-cmd: No such file or directory
cound not load plugin '/home/joe/qEmu/trace/trace-cmd/plugin_kvm.so'
/home/joe/qemu/trace/trace-cmd/plugin_kvm.so: undefined symbol:
ud_translate_att
However, during the build process, udis86 is linked in like it should be:
[...]
gcc -g -Wall -I. '-DPLUGIN_DIR="/usr/local/share/trace-cmd/plugins"'
-DHAVE_UDIS86 -ludis86 -DHAVE_BLK_TC_FLUSH -shared -nostartfiles -o
plugin_blk.so plugin_blk.o
But when looking, I just noticed that it does not appear in the imports
$ ldd plugin_kvm.so
linux-vdso.so.1 => (0x00007fff3cfff000)
libc.so.6 => /lib64/libc.so.6 (0x00007f6429e1c000)
/lib64/ld-linux-x86-64.so.2 (0x00007f642a3e4000)
Nor do I actually *have* the .so of udis86 in my /usr/lib directory.
Gentoo by default just built the static library. Weird! I'll recompile
myself and then it'll work for sure.
Best regards,
Joe
next prev parent reply other threads:[~2012-06-06 18:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-03 12:18 KVM entry failed, hardware error Johannes Bauer
2012-06-03 12:33 ` Avi Kivity
2012-06-03 13:01 ` Johannes Bauer
2012-06-03 13:43 ` Avi Kivity
2012-06-03 16:25 ` Johannes Bauer
2012-06-04 8:53 ` Gleb Natapov
2012-06-04 8:56 ` Avi Kivity
2012-06-04 18:28 ` Johannes Bauer
2012-06-04 18:32 ` Johannes Bauer
2012-06-05 13:59 ` David Ahern
2012-06-06 18:19 ` Johannes Bauer [this message]
2012-06-06 15:53 ` Avi Kivity
2012-06-06 18:07 ` Johannes Bauer
2012-06-07 7:12 ` Avi Kivity
2012-06-07 10:03 ` Johannes Bauer
2012-06-07 10:54 ` Avi Kivity
2012-06-07 14:52 ` Avi Kivity
2012-06-07 15:39 ` Johannes Bauer
2012-06-07 17:25 ` Avi Kivity
2012-06-07 19:14 ` Johannes Bauer
2012-06-10 15:19 ` Avi Kivity
2012-06-12 10:23 ` Johannes Bauer
2012-06-12 10:45 ` Avi Kivity
2012-06-07 19:46 ` Johannes Bauer
2012-06-07 19:54 ` Johannes Bauer
2012-06-03 13:04 ` Johannes Bauer
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=4FCF9F2C.2070501@gmx.de \
--to=dfnsonfsduifb@gmx.de \
--cc=avi@redhat.com \
--cc=dsahern@gmail.com \
--cc=gleb@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