From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org, S KH <sgh8183@gmail.com>
Subject: Re: [Qemu-devel] Question in QEMU : The result of printf does not appear in the qemu VM's log.
Date: Wed, 8 May 2019 11:12:33 +0100 [thread overview]
Message-ID: <20190508101233.GF32552@redhat.com> (raw)
In-Reply-To: <CAE519-niSfXffzKMY09_JJZ7q3KDRf+z-AU-XNeNqD=Z-DAeoA@mail.gmail.com>
Re-adding qemu-devel - please don't take mailing list threads private.
On Wed, May 08, 2019 at 07:07:01PM +0900, S KH wrote:
> Hello.
>
> Thanks to help, I can see the results of the output in the log file. Thank
> you very much for your help. I am currently working with the QEMU source as
> well as the SPICE source. After checking the source, I found that the QEMU
> source calls the SPICE function. So I used the 'g_printerr' function in the
> SPICE source to figure out the flow. Maybe it should be obvious,
> 'g_printerr' used by SPICE will not show in 'domain_name.log' file
> 'in/var/log/libvirt/qemu.' It may not be a good question for qemu-devel,
> but I wonder where the 'g_printerr' results from SPICE sources can be seen.
The SPICE server library is linked directly to QEMU so g_printerr should
work fine from SPICE code in the same way as QEMU code. If you're not
seeing the results, then my guess would be that the QEMU you are launching
is not actually using the SPICE library you built with debugging. It is
probably still using the SPICE library from the OS distro.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2019-05-08 10:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 1:51 [Qemu-devel] Question in QEMU : The result of printf does not appear in the qemu VM's log S KH
2019-05-08 9:15 ` Daniel P. Berrangé
[not found] ` <CAE519-niSfXffzKMY09_JJZ7q3KDRf+z-AU-XNeNqD=Z-DAeoA@mail.gmail.com>
2019-05-08 10:12 ` Daniel P. Berrangé [this message]
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=20190508101233.GF32552@redhat.com \
--to=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sgh8183@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).