From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: trace-cmd errors on kvm events Date: Sat, 09 Apr 2011 01:42:14 +0200 Message-ID: <4D9F9D56.2050109@web.de> References: <4D9F59AC.6080707@gmail.com> <4D9F790B.2000300@web.de> <4D9F7A4B.3040606@gmail.com> <4D9F7BC0.8010003@web.de> <4D9F99AA.8060803@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigC242A2DCA1FA240DBD7439CA" Cc: LKML , KVM mailing list To: David Ahern Return-path: In-Reply-To: <4D9F99AA.8060803@gmail.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigC242A2DCA1FA240DBD7439CA Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2011-04-09 01:26, David Ahern wrote: > On 04/08/11 15:18, Jan Kiszka wrote: >> Let me check... indeed, I'm getting the same file-not-found here with >> trace-cmd.git 9cce1c9b5b when starting it directly from its build dire= ctory. >> >> But maybe your trace-cmd or kernel versions are too old / incompatible= =2E >> I'm not getting complaints about unparseable events with the above >> snapshot and 2.6.38. >=20 > 2.6.38.2 kernel, trace-cmd 3e8b5b8 which is March 18 (though git pull > done this morning). >=20 > For grins I checked-out 9cce1c9b5b and same error: > trace-cmd record -e kvm -- sleep 1 > trace-cmd report 2>&1 | less >=20 > You do have to put stderr onto stdout to see the messages I reported > earlier. Or look for [FAILED TO PARSE] on the kvm_exit and > kvm_emulate_insn lines. I did that. What I also did is updating trace-cmd git and then reinstalling the latest plugins: make install_plugins prefix=3D$HOME. They then end up in $HOME/.trace-cmd/plugins. Now I do not have a single error message anymore, including that file not found. Jan --------------enigC242A2DCA1FA240DBD7439CA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk2fnVYACgkQitSsb3rl5xQaeACfahnhOaA2BHiSO1JNV9SQ3EDx NjMAoL4fRLt7FM8+ym8O6+FbZildfMjd =aVXn -----END PGP SIGNATURE----- --------------enigC242A2DCA1FA240DBD7439CA--