Xen devel - Oct 2006 - [PATCH] [2/5] put xen console message into syslog

Hi,

[2/5] add xenlogd daemon for xen console logging

Signed-off-by: Katsuhito Minai <minai@jp.fujitsu.com>

Best Regards,
Katsuhito Minai


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

On Fri, Oct 20, 2006 at 09:48:48PM +0900, MINAI Katsuhito
wrote:
> Hi,
> 
> [2/5] add xenlogd daemon for xen console logging
Why have yet another daemon running in Dom0? We''ve already got
xenconsoled
reading this data from the guest ring buffers, so it strikes me it''d be
better to just add a command line flag to that existing daemon to make
it log stuff to syslog directly.

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

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

MINAI Katsuhito wrote:
> Hi,
> 
> [2/5] add xenlogd daemon for xen console logging
Instead of adding yet another daemon to Xen, why not just add this 
functionality to xenconsoled?

Seems like an appropriate place for it.

Regards,

Anthony Liguori

> Signed-off-by: Katsuhito Minai <minai@jp.fujitsu.com>
> 
> Best Regards,
> Katsuhito Minai
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

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

On 20/10/06 5:52 pm, "Daniel P. Berrange" <berrange@redhat.com>
wrote:
>> 
>> [2/5] add xenlogd daemon for xen console logging
> 
> Why have yet another daemon running in Dom0? We''ve already got
xenconsoled
> reading this data from the guest ring buffers, so it strikes me
it''d be
> better to just add a command line flag to that existing daemon to make
> it log stuff to syslog directly.
I assume this is for Xen''s own logging output (''xm
dmesg''). Still, it would
fairly natural to extend xenconsoled with a new ''backend type''
that can read
the logging data from Xen.

 -- Keir



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

On Fri, Oct 20, 2006 at 08:07:28PM +0100, Keir Fraser
wrote:
> 
> 
> 
> On 20/10/06 5:52 pm, "Daniel P. Berrange"
<berrange@redhat.com> wrote:
> 
> >> 
> >> [2/5] add xenlogd daemon for xen console logging
> > 
> > Why have yet another daemon running in Dom0? We''ve already
got xenconsoled
> > reading this data from the guest ring buffers, so it strikes me
it''d be
> > better to just add a command line flag to that existing daemon to make
> > it log stuff to syslog directly.
> 
> I assume this is for Xen''s own logging output (''xm
dmesg''). Still, it would
> fairly natural to extend xenconsoled with a new ''backend
type'' that can read
> the logging data from Xen.
Ah yes, I didn''t look closely enough to see it was the hypervisor logs
rather than guest logs. We certainly could also benefit from having the
guest consoles persistently logged in the host too.

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

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

On 20/10/06 5:59 pm, "Anthony Liguori" <anthony@codemonkey.ws>
wrote:
>> [2/5] add xenlogd daemon for xen console logging
> 
> Instead of adding yet another daemon to Xen, why not just add this
> functionality to xenconsoled?
> 
> Seems like an appropriate place for it.
Yes, I''m going to sort through the patches and apply the useful
hypervisor
and library pieces, but we don''t want another daemon. Adding
xen-console and
persistent-logging support to xenconsoled is the way to go. The only
question then is what is the right way to configure it (e.g., to tell it
what to log to syslogd, or to a file, or send via a socket)? I think
configuration via xenbus nodes written by xend would be reasonable -- allows
dynamic configuration changes e.g., as domains come and go.

 -- Keir



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