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] [PATCH] Log qemu-dm's message with date, time and pid

To: Kevin Wolf <kwolf@xxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Log qemu-dm's message with date, time and pid
From: Yuji Shimada <shimada-yxb@xxxxxxxxxxxxxxx>
Date: Tue, 01 Jul 2008 17:01:32 +0900
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Yosuke Iwamatsu <y-iwamatsu@xxxxxxxxxxxxx>
Delivery-date: Tue, 01 Jul 2008 01:02:11 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4868AB49.9050109@xxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20080630134036.F31B.SHIMADA-YXB@xxxxxxxxxxxxxxx> <4868AB49.9050109@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
OK. I understand what you tell me. Thanks.

I'll consider about a new implementation. It is multithread or
multiprocess programming for logs in qemu-dm without using an external
tool (ioemu-logger).

Thanks.

--
Yuji Shimada

On Mon, 30 Jun 2008 11:45:45 +0200
Kevin Wolf <kwolf@xxxxxxx> wrote:

> Yuji Shimada schrieb:
> > I agree with developing proper logging functions. But without these
> > functions, I think ioemu-logger is a good solution.
> > 
> > We can reboot xend by the following command.
> >   # /etc/init.d/xend restart
> > Running of guest domains must not be affected by rebooting xend.
> 
> This seems to be a valid point.
> 
> > I'm sure that ioemu-logger dying is rare case. But there is no guarantee
> > that it doesn't die.
> > If xend starts ioemu-logger, xend loses one end of a pipe by rebooting
> > xend. After that, xend can't associates stdin for ioemu-logger with the
> > pipe when xend restarts ioemu-logger after ioemu-logger dies. This
> > problem happens because the life cycle of xend and qemu-dm is different.
> > So I think to start ioemu-logger by qemu-dm is more simple.
> > 
> > Using named pipe (FIFO), it's possible to start ioemu-logger by xend.
> > But sorry, I don't know about python well. Could anyone develope it?
> 
> I'm under the impression that you're completely missing my (and Ian's)
> point. Actually, I'm not talking about having ioemu-logger started by
> xend. I'm talking about not having ioemu-logger at all (at least not as
> a new external tool). Xen has already too many of these small tools,
> IMHO, and we shouldn't add even more to them without need.
> 
> So, please implement it in qemu-dm instead of an external tool, if xend
> is not possible.
> 
> Kevin

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