From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=60852 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OkyZB-0006O0-ED for qemu-devel@nongnu.org; Mon, 16 Aug 2010 08:13:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OkyZ5-0005lu-Il for qemu-devel@nongnu.org; Mon, 16 Aug 2010 08:13:25 -0400 Received: from mx1.redhat.com ([209.132.183.28]:12975) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OkyZ5-0005lc-7E for qemu-devel@nongnu.org; Mon, 16 Aug 2010 08:13:19 -0400 Message-ID: <4C692B51.6000201@redhat.com> Date: Mon, 16 Aug 2010 14:13:05 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <1281622202-3453-8-git-send-email-stefano.stabellini@eu.citrix.com> <4C65948C.8030707@codemonkey.ws> <4C67F5E3.5070709@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCH 08/15] xen: Read and write the state of the VM in xenstore List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefano Stabellini Cc: Anthony Perard , "xen-devel@lists.xensource.com" , "qemu-devel@nongnu.org" On 08/16/2010 01:15 PM, Stefano Stabellini wrote: > On Sun, 15 Aug 2010, Paolo Bonzini wrote: >> On 08/13/2010 02:53 PM, Anthony Liguori wrote: >>> On 08/12/2010 09:09 AM, stefano.stabellini@eu.citrix.com wrote: >>>> From: Anthony PERARD >>>> >>>> Introduce functions to read and write the state of the VM in xenstore. >>> >>> This basically creates a new management interface for QEMU via the >>> xenstore. >>> >>> Our management interface is QMP. If you want to maintain compatibility, >>> you'll need to write a QMP -> xenstore daemon that maps events >>> appropriately. >> >> This would belong in xl/libxl. > > Yes, but considering that we don't want a xenstore-based management > interface I would gladly do without the compatibility daemon. > We'll try to reduce all the xenstore interaction to the bare minimum, > and use QMP everywhere else. Yes, I was just pointing out that you don't need a new compatibility daemon. Since xl is already daemonizing itself to handle on_crash and friends, it could also set up all the watches it cares about, and convert them to QMP commands. It's all more code that needs to be written of course, and boring stuff even. :) Paolo From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH 08/15] xen: Read and write the state of the VM in xenstore Date: Mon, 16 Aug 2010 14:13:05 +0200 Message-ID: <4C692B51.6000201@redhat.com> References: <1281622202-3453-8-git-send-email-stefano.stabellini@eu.citrix.com> <4C65948C.8030707@codemonkey.ws> <4C67F5E3.5070709@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stefano Stabellini Cc: Anthony Perard , "xen-devel@lists.xensource.com" , "qemu-devel@nongnu.org" , Anthony Liguori List-Id: xen-devel@lists.xenproject.org On 08/16/2010 01:15 PM, Stefano Stabellini wrote: > On Sun, 15 Aug 2010, Paolo Bonzini wrote: >> On 08/13/2010 02:53 PM, Anthony Liguori wrote: >>> On 08/12/2010 09:09 AM, stefano.stabellini@eu.citrix.com wrote: >>>> From: Anthony PERARD >>>> >>>> Introduce functions to read and write the state of the VM in xenstore. >>> >>> This basically creates a new management interface for QEMU via the >>> xenstore. >>> >>> Our management interface is QMP. If you want to maintain compatibility, >>> you'll need to write a QMP -> xenstore daemon that maps events >>> appropriately. >> >> This would belong in xl/libxl. > > Yes, but considering that we don't want a xenstore-based management > interface I would gladly do without the compatibility daemon. > We'll try to reduce all the xenstore interaction to the bare minimum, > and use QMP everywhere else. Yes, I was just pointing out that you don't need a new compatibility daemon. Since xl is already daemonizing itself to handle on_crash and friends, it could also set up all the watches it cares about, and convert them to QMP commands. It's all more code that needs to be written of course, and boring stuff even. :) Paolo