Hans van Kranenburg
2009-Mar-02 15:52 UTC
[Pkg-xen-devel] Bug#517863: Make logging of guest console output in dom0 via xenconsoled configurable
Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: wishlist Hi, this morning I spend some time to find out how to log console output of Xen guest domains into a file in dom0. I ended up using a quick 'n dirty solution: mario:/usr/lib/xen-3.2-1/bin 0-# diff -u xend.orig xend --- xend.orig 2009-03-02 16:49:49.000000000 +0100 +++ xend 2009-03-02 16:16:03.000000000 +0100 @@ -100,7 +100,8 @@ import time time.sleep(2) if os.fork() == 0: - execute('xenconsoled') + args = ["--log", "guest", "--log-dir", "/var/log/xen/guest/"] + execute('xenconsoled', args) def start_blktapctrl(): if os.fork() == 0: mario:/usr/lib/xen-3.2-1/bin 0-# It seems the options used to start xenconsoled cannot be configured in Debian now. /etc/init.d/xend executes /usr/lib/xen-3.2-1/bin/xend which executes xenconsoled subsequently. Hans van Kranenburg
Debian Bug Tracking System
2011-Jun-02 11:09 UTC
[Pkg-xen-devel] Bug#517863: marked as done (Make logging of guest console output in dom0 via xenconsoled configurable)
Your message dated Thu, 2 Jun 2011 13:06:37 +0200 with message-id <20110602110637.GA5891 at entuzijast.net> and subject line fixed a while ago in the up-to-date version has caused the Debian Bug report #517863, regarding Make logging of guest console output in dom0 via xenconsoled configurable to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner at bugs.debian.org immediately.) -- 517863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=517863 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: Hans van Kranenburg <hans.van.kranenburg at mendix.com> Subject: Make logging of guest console output in dom0 via xenconsoled configurable Date: Mon, 02 Mar 2009 16:52:51 +0100 Size: 2646 URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20110602/25fb4500/attachment.mht> -------------- next part -------------- An embedded message was scrubbed... From: Josip Rodin <joy at debbugs.entuzijast.net> Subject: fixed a while ago in the up-to-date version Date: Thu, 2 Jun 2011 13:06:37 +0200 Size: 2403 URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20110602/25fb4500/attachment-0001.mht>
Hans van Kranenburg
2011-Jun-02 13:15 UTC
[Pkg-xen-devel] Bug#517863: closed by Josip Rodin <joy@debbugs.entuzijast.net> (fixed a while ago in the up-to-date version)
Hi Josip, thanks for the information and closing this wishlist-item. The XENCONSOLED_ARGS= is exactly what I was looking for. I don't think logging should be enabled by default, as it could potentially be a way for misbehaving guests to unexpectedly fill up your hypervisors disk space. But I think xenconsoled should have a manual page to document the options which can be used. Running /usr/lib/xen-4.0/bin/xenconsoled --help does list the options, but does not explain them. It would probably be nice to include some documentation in /usr/share/doc/xen-utils-4.0/README.Debian about this, the logrotate example could be included there as well. I'll open a new bug against xen-utils-4.0, providing some documentation that could be included in README.Debian. Hans van Kranenburg
Possibly Parallel Threads
- Bug#628912: xenconsoled and xenstored stopping unhandled by init script
- [PATCH] xen init script: don't fail when being run in domU
- Bug#851654: Prerm maintainer script unconditionally stops xend/xenconsoled
- xenconsoled
- [PATCH 1 of 4] xenconsoled: do not write the pty under serial