From: Avi Kivity <avi@redhat.com>
To: "Liu, Jinsong" <jinsong.liu@intel.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
kvm <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] qemu-kvm log
Date: Mon, 10 Sep 2012 16:28:08 +0300 [thread overview]
Message-ID: <504DEAE8.7080703@redhat.com> (raw)
In-Reply-To: <DE8DF0795D48FD4CA783C40EC829233532528F@SHSMSX101.ccr.corp.intel.com>
On 09/10/2012 01:44 PM, Liu, Jinsong wrote:
> Hi,
>
> I'm recently debugging a qemu-kvm issue. I add some print code like 'fprintf(stderr, ...)', however I fail to see any info at stdio. Anyone can tell me where is qemu-kvm logfile, or, what I need do to record my fprintf info?
If you're running via libvirt, the log is in /var/log/libvirt/qemu. If
you're running from the command line and printf()s should end on your
terminal.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-09-10 13:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 10:44 [Qemu-devel] qemu-kvm log Liu, Jinsong
2012-09-10 13:28 ` Avi Kivity [this message]
2012-09-10 14:05 ` Liu, Jinsong
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=504DEAE8.7080703@redhat.com \
--to=avi@redhat.com \
--cc=jinsong.liu@intel.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).