WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] daemon to monitor 'xm dmesg'

On Tue, Dec 15, 2009 at 5:30 AM, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> 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@xxxxxxxxx> 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@xxxxxxxxxxxxx>
>> wrote:
>>> Start xenconsoled with option --log=hv
>>>
>>>  -- Keir
>>>
>>> On 15/12/2009 09:29, "James Harper" <james.harper@xxxxxxxxxxxxxxxx> 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

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>
  • Re: [Xen-devel] daemon to monitor 'xm dmesg', Keith Coleman <=