All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zhang Haoyu" <zhanghy@sangfor.com>
To: "Zhang Haoyu" <zhanghy@sangfor.com>, "Andreas Färber" <afaerber@suse.de>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [questions]_about_qemu_log
Date: Sat, 26 Jul 2014 11:03:47 +0800	[thread overview]
Message-ID: <201407261103445856515@sangfor.com> (raw)
In-Reply-To: 201407261028057289331@sangfor.com

>>>>> 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.
>>
>I think the "-msg -msg timestamp=on" option will add timestamp to the output of error_report(fmt, ...),
>but where is the output? Which file saves the output?
If during the qmp operation, error_report will output to current monitor, but my concern is to stderr, which file saves the output?
>And where is the output of fprintf(stderr, fmt, ...)?
>Should I redirect of stderr to specified log file?
>
>In libvirt code, when start a vm(qemuProcessStart), it will create a qemu log file named /var/log/libvirt/qemu/vmname.log,
>and redirect the stderr and stdout to file descriptor of this qemu log file.
>
>But if I run a vm directly by qemu command, bypass libvirt, then how to configure qemu to assure that each vm has its own log file,
>and how to redirect the stderr, stdout to each vm's own log file?
>
>Thanks,
>Zhang Haoyu
>
>>Cheers,
>>Andreas

  reply	other threads:[~2014-07-26  3:11 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
2014-07-26  2:28       ` Zhang Haoyu
2014-07-26  3:03         ` Zhang Haoyu [this message]
2014-07-29 19:51         ` 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=201407261103445856515@sangfor.com \
    --to=zhanghy@sangfor.com \
    --cc=afaerber@suse.de \
    --cc=alex.bennee@linaro.org \
    --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 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.