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: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Log qemu-dm's message with date, time and pid
From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Date: Thu, 26 Jun 2008 17:38:44 +0100
Cc: Yuji Shimada <shimada-yxb@xxxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Yosuke Iwamatsu <y-iwamatsu@xxxxxxxxxxxxx>, Kevin Wolf <kwolf@xxxxxxx>
Delivery-date: Thu, 26 Jun 2008 09:39:17 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <18531.43971.119239.17511@xxxxxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <486322FE.3070304@xxxxxxxxxxxxx> <48637B96.9090606@xxxxxxx> <18531.43971.119239.17511@xxxxxxxxxxxxxxxxxxxxxxxx>
Reply-to: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.1i
On Thu, Jun 26, 2008 at 03:46:27PM +0100, Ian Jackson wrote:
> Yosuke Iwamatsu writes ("[Xen-devel] [PATCH] Log qemu-dm's message with date, 
> time and pid"):
> > The qemu-dm's log message doesn't have date, time, and pid. It is
> > difficult to find out the message we want.
> 
> 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.
> 
> Also, I think I would discourage the introduction of new features in
> tools/ioemu.  I would much prefer submissions to be made against my
> new merged qemu tree, which you can currently find at
>  http://www.chiark.greenend.org.uk/~ijackson/qemu-xen.git

What are your plans wrt to QEMU longer term ?  Are you going to merge this
GIT repo into tools/ioemu in xen-unstable.hg, or thinking its better to
keep a separate tree on an ongoing basis ? Would we have synced up 
releases of the two, or try to apply some ABI stability to libxc and 
libxenstore APIs to allow separate release of QEMU vs XenD tools ? The
latter could be interesting because apps like Xenner are able to use
QEMU-DM in isolation from the rest of the XenD stack.

Regards,
Daniel
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

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