From: "Andreas Färber" <afaerber@suse.de>
To: Zhang Haoyu <zhanghy@sangfor.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [questions] about qemu log
Date: Fri, 25 Jul 2014 15:20:17 +0200 [thread overview]
Message-ID: <53D25991.3010001@suse.de> (raw)
In-Reply-To: <201407251907132706648@sangfor.com>
Am 25.07.2014 13:07, schrieb Zhang Haoyu:
>>> Hi, all
>>>
>>> If I use qemu command directly to run vm, bypass libvirt, how to configure qemu to assure that each vm has its own log file, like vmname.log?
>>> For example, VM: rhel7-net has its own log file, rhel7-net.log,
>>> VM:rhel7-stor has its own log file, rhel7-stor.log.
>>
>> -D /path/to/unique/file/name.log
>>
> -D option is to configure qemu_logfile for the output logs which are controlled by qmp command "logfile", which can be enabled/disabled on run time.
>
> I want to configure the log file for the output of fprintf(stderr, fmt, ...), .etc,
> i.e., how to redirect the output of fprintf(stderr, fmt, ...), or some other log-interface to a specified file?
In a shell you would write something like:
2> stderr.log
You may also want to toggle QEMU's -msg timestamp=on option.
Cheers,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2014-07-25 13:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 6:42 [Qemu-devel] [questions] about qemu log Zhang Haoyu
2014-07-25 10:22 ` Alex Bennée
2014-07-25 11:07 ` Zhang Haoyu
2014-07-25 13:20 ` Andreas Färber [this message]
2014-07-26 2:28 ` Zhang Haoyu
2014-07-26 3:03 ` [Qemu-devel] [questions]_about_qemu_log Zhang Haoyu
2014-07-29 19:51 ` [Qemu-devel] [questions] about qemu log Eric Blake
2014-08-05 20:48 ` William Dauchy
2014-08-05 22:40 ` Peter Crosthwaite
2014-08-06 1:23 ` Zhang Haoyu
2014-08-06 2:49 ` Peter Crosthwaite
2014-08-06 3:41 ` Zhang Haoyu
2014-08-06 6:20 ` Markus Armbruster
2014-08-06 7:00 ` Zhang Haoyu
2014-08-06 7:42 ` Markus Armbruster
2014-08-06 12:04 ` Peter Crosthwaite
2014-08-06 10:43 ` William Dauchy
2014-08-06 20:42 ` William Dauchy
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=53D25991.3010001@suse.de \
--to=afaerber@suse.de \
--cc=alex.bennee@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=zhanghy@sangfor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.