From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Ahern Subject: Re: trace-cmd errors on kvm events Date: Fri, 08 Apr 2011 15:12:43 -0600 Message-ID: <4D9F7A4B.3040606@gmail.com> References: <4D9F59AC.6080707@gmail.com> <4D9F790B.2000300@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: LKML , KVM mailing list To: Jan Kiszka Return-path: In-Reply-To: <4D9F790B.2000300@web.de> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 04/08/11 15:07, Jan Kiszka wrote: > On 2011-04-08 20:53, David Ahern wrote: >> 2.6.38.2 kernel with trace-cmd git pulled this morning: >> >> trace-cmd record -e kvm >> >> trace-cmd report 2>&1 | less >> >> trace-cmd: No such file or directory > > Does this error come from trace-cmd failing to find its kvm plugin? > Check what strace -e open says. > > Jan > Tried that before - it was not enlightening. strace -e trace=open trace-cmd report 2>&1 | less open("/etc/ld.so.cache", O_RDONLY) = 3 open("/lib64/libdl.so.2", O_RDONLY) = 3 open("/lib64/libc.so.6", O_RDONLY) = 3 open("/root/trace.dat", O_RDONLY) = 3 trace-cmd: No such file or directory function ftrace_print_symbols_seq not defined failed to read event print fmt for kvm_nested_vmexit_inject function ftrace_print_symbols_seq not defined failed to read event print fmt for kvm_nested_vmexit function ftrace_print_symbols_seq not defined failed to read event print fmt for kvm_exit bad op token { failed to read event print fmt for kvm_emulate_insn open("/proc/meminfo", O_RDONLY) = 4 David