qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Nir Levy <nirl@asocsnetworks.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Stefan Hajnoczi <stefanha@gmail.com>
Subject: Re: [Qemu-devel] errno 13, fopen qemu trace file.
Date: Thu, 18 Aug 2016 14:35:09 +0100	[thread overview]
Message-ID: <20160818133509.GF13050@redhat.com> (raw)
In-Reply-To: <AM4PR06MB1601B1774C1C2B3722D85FADCC150@AM4PR06MB1601.eurprd06.prod.outlook.com>

On Thu, Aug 18, 2016 at 01:31:19PM +0000, Nir Levy wrote:
> Daniel, Thanks for your response.
> 
> But I have succeeded using simpletrace when building libvirt from source file into some/other/dir/install

I can only assume you built libvirt so that qemu runs as root,
instead of an unprivileged user account, and/or have not enabled
selinux for libvirt.

> 
> I am using Fedora22 which does not support lttng.
> at the mather of fact I have installed lttng before and build the kernel modules (2.6.0) still no trace generated.
> Michael Jeanson is working for supplying modules (2.8.0) for the next fedora (25)
> fedora 23 and 24 do support systemtap but not over 22 on my kernel 4.2.8 (which we stick to in Asocs due to known performance degradation in later releases)

systemtap is supported in all Fedora releases - if there's any
problems do file bugs against it, as its expected to work as
it is the supported tracing mechanism for Fedora with qemu and
libvirt.


Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

  reply	other threads:[~2016-08-18 13:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-18 12:58 [Qemu-devel] errno 13, fopen qemu trace file Nir Levy
2016-08-18 13:11 ` Daniel P. Berrange
2016-08-18 13:31   ` Nir Levy
2016-08-18 13:35     ` Daniel P. Berrange [this message]
2016-08-18 13:22 ` Stefan Hajnoczi
2016-08-18 13:40   ` Nir Levy

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=20160818133509.GF13050@redhat.com \
    --to=berrange@redhat.com \
    --cc=nirl@asocsnetworks.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).