qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Toms Varghese <tomsvhere@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Output of fprintf messages in qemu source
Date: Mon, 23 Mar 2015 12:47:16 +0000	[thread overview]
Message-ID: <20150323124716.GC9268@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <CAJd_G4wK=tK9XztNiNLYa6UtA0KH_Gm6kYX-4xKMHfYiCwn49w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 898 bytes --]

On Thu, Mar 19, 2015 at 12:17:29AM +0530, Toms Varghese wrote:
> Hi all,
> 
> I can see some fprintf (stderr, ...) statements in qemu source code. I
> expect the output to be shown in  the terminal window. I use libvirt to
> manage my VMs and hence have no idea about the exact qemu command line
> being used. From the comments in the below post
> http://blog.vmsplice.net/2011/03/how-to-write-trace-analysis-scripts-for.html
> I found that libvirt is supposed to store the stderr outputs
> in /var/lib/libvirt/qemu/.log file. But I am unable to find any such log
> file in /var/lib/libvirt/qemu. Can anyone please tell me how to get the
> output of fprintfs in this case as it would help me a lot?
> I am using fedora 21, qemu 2.0.2 and libvirt 1.2.9.2.

The file name is:
/var/lib/libvirt/qemu/<domain>.log

It includes the QEMU command-line as well as stderr output.

Stefan

[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2015-03-23 12:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-18 18:47 [Qemu-devel] Output of fprintf messages in qemu source Toms Varghese
2015-03-23 12:47 ` Stefan Hajnoczi [this message]
2015-03-24 13:34   ` Toms Varghese
2015-03-30 15:05     ` Stefan Hajnoczi

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=20150323124716.GC9268@stefanha-thinkpad.redhat.com \
    --to=stefanha@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=tomsvhere@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).