From: Keith Coleman <list.keith@scaltro.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: Tom Rotenberg <tom.rotenberg@gmail.com>,
James Harper <james.harper@bendigoit.com.au>,
Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: daemon to monitor 'xm dmesg'
Date: Tue, 23 Feb 2010 18:43:30 -0500 [thread overview]
Message-ID: <5411dbdc1002231543v35e70e40u29257f467c6e98b4@mail.gmail.com> (raw)
In-Reply-To: <C74D15B3.4725%keir.fraser@eu.citrix.com>
On Tue, Dec 15, 2009 at 5:30 AM, Keir Fraser <keir.fraser@eu.citrix.com> wrote:
> <log_dir>/hypervisor.log where <log_dir> defaults to /var/log/xen/console
> but can be overridden with command-line option --log-dir=
>
> -- Keir
>
> On 15/12/2009 10:25, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote:
>
>> And then to where will the log be directed to? where will it be
>> located on the HD?
>>
>> On Tue, Dec 15, 2009 at 12:06 PM, Keir Fraser <keir.fraser@eu.citrix.com>
>> wrote:
>>> Start xenconsoled with option --log=hv
>>>
>>> -- Keir
>>>
>>> On 15/12/2009 09:29, "James Harper" <james.harper@bendigoit.com.au> wrote:
>>>
>>>> Is there a way to put xen's logs into a file in dom0? Eg
>>>> /var/log/xen/hypervisor.log or something like that?
>>>>
Has anyone else noticed repeat messages in the log file after enabling
hypervisor logging? It seems like whenever a few messages are logged
to 'xm dmesg' the entire contents of 'xm dmesg' are appended to
hypervisor.log.
Keith Coleman
prev parent reply other threads:[~2010-02-23 23:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-15 9:29 daemon to monitor 'xm dmesg' James Harper
2009-12-15 10:06 ` Keir Fraser
2009-12-15 10:25 ` Tom Rotenberg
2009-12-15 10:30 ` Keir Fraser
2010-02-23 23:43 ` Keith Coleman [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=5411dbdc1002231543v35e70e40u29257f467c6e98b4@mail.gmail.com \
--to=list.keith@scaltro.com \
--cc=Keir.Fraser@eu.citrix.com \
--cc=james.harper@bendigoit.com.au \
--cc=tom.rotenberg@gmail.com \
--cc=xen-devel@lists.xensource.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).