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: Yuji Shimada <shimada-yxb@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Log qemu-dm's message with date, time and pid
From: Kevin Wolf <kwolf@xxxxxxx>
Date: Fri, 27 Jun 2008 11:10:55 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Yosuke Iwamatsu <y-iwamatsu@xxxxxxxxxxxxx>
Delivery-date: Fri, 27 Jun 2008 02:15:24 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20080627171727.A932.SHIMADA-YXB@xxxxxxxxxxxxxxx>
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: <486322FE.3070304@xxxxxxxxxxxxx> <18531.43971.119239.17511@xxxxxxxxxxxxxxxxxxxxxxxx> <20080627171727.A932.SHIMADA-YXB@xxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.12 (X11/20071114)
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

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