Skip to contentSkip to conversation

put xen console message into syslog

PATCH In review MINAI Katsuhito 4 participants 6 messages Oct 20, 2006 – Oct 21, 2006

lore
Share & tools
lore
#0 lore raw

PATCH 2/5 put xen console message into syslog

Hi,

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

Best Regards,
Katsuhito Minai

tools/misc/Makefile +2 -2
diff -r 6ed4368b4a9e tools/misc/Makefile
@@ -13,10 +13,10 @@ CFLAGS   += $(INCLUDES)
 
 HDRS     = $(wildcard *.h)
 
-TARGETS  = xenperf xc_shadow
+TARGETS  = xenperf xc_shadow xenlogd
 
 INSTALL_BIN  = $(TARGETS) xencons
-INSTALL_SBIN = netfix xm xen-bugtool xend xenperf
+INSTALL_SBIN = netfix xm xen-bugtool xend xenperf xenlogd
 
 .PHONY: all
 all: build
tools/misc/xenlogd.c new file +307 -0

307 lines not on this page · raw message

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

#1 lore raw
Quoted 3 lines · MINAI Katsuhito

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.

Signature · 4 lines
|=- 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  -=| 
#4 lore raw
In reply to MINAI Katsuhito
Quoted 3 lines · MINAI Katsuhito

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

Quoted 12 lines

Best Regards,
Katsuhito Minai

------------------------------------------------------------------------

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

#2 lore raw
In reply to Daniel P. Berrange
Quoted 7 lines · Daniel P. Berrange
Quoted 2 lines

[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

#3 lore raw
Quoted 8 lines · Keir Fraser
Quoted 3 lines · Daniel P. Berrange
Quoted 2 lines

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

Quoted 8 lines
Quoted 4 lines

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.

Signature · 4 lines
|=- 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  -=| 
#5 lore raw
In reply to Anthony Liguori
Quoted 6 lines · Anthony Liguori
Quoted 1 line

[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