From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Wolf Subject: Re: [PATCH] Log qemu-dm's message with date, time and pid Date: Fri, 27 Jun 2008 11:10:55 +0200 Message-ID: <4864AE9F.1070207@suse.de> References: <486322FE.3070304@ab.jp.nec.com> <18531.43971.119239.17511@mariner.uk.xensource.com> <20080627171727.A932.SHIMADA-YXB@necst.nec.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20080627171727.A932.SHIMADA-YXB@necst.nec.co.jp> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Yuji Shimada Cc: xen-devel@lists.xensource.com, Ian Jackson , Yosuke Iwamatsu List-Id: xen-devel@lists.xenproject.org Yuji Shimada schrieb: > Ian Jackson wrote: >> I agree with Kevin Wolf's comments. But I would go further: why can >> this not be done by the code in xend which starts qemu-dm ? That >> would avoid any change to the qemu code. Right, that would be even better. Or maybe as another option, introduce proper logging functions instead of fprintf on stderr into (upstream) qemu. This would be the most work, of course, but IMHO also the cleanest solution. > I think that my implementation is more safety way because of the > following reason. > > qemu-dm can easily restart ioemu-logger when ioemu-logger die. > And ioemu-logger death doesn't affected to guest software. ioemu-logger is so simple that it would be a shame to see it crash anyway. > In addition: > > We developed ioemu-logger without changing the codes which write > messages. This enables less changes of the codes in qemu-dm. You could do the same from within qemu-dm or in xend. Kevin