From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LrvgB-0000Mm-Hk for qemu-devel@nongnu.org; Thu, 09 Apr 2009 10:56:35 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Lrvg5-0000IG-Ce for qemu-devel@nongnu.org; Thu, 09 Apr 2009 10:56:34 -0400 Received: from [199.232.76.173] (port=55983 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Lrvg5-0000I9-16 for qemu-devel@nongnu.org; Thu, 09 Apr 2009 10:56:29 -0400 Received: from lizzard.sbs.de ([194.138.37.39]:18136) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Lrvg3-0003jh-Ha for qemu-devel@nongnu.org; Thu, 09 Apr 2009 10:56:28 -0400 Message-ID: <49DE0C98.5000402@siemens.com> Date: Thu, 09 Apr 2009 16:56:24 +0200 From: Jan Kiszka MIME-Version: 1.0 Subject: Re: [libvirt] Re: [Qemu-devel] [PATCH 1/6] Allow multiple monitor devices (v2) References: <1239215702-23818-1-git-send-email-aliguori@us.ibm.com> <49DDAF9F.7040400@redhat.com> <49DDF807.1050707@us.ibm.com> <49DDFAD5.7060808@redhat.com> <49DDFC5C.4080504@us.ibm.com> <49DE0042.9050103@redhat.com> <49DE0303.7070507@redhat.com> <49DE03F0.6070503@redhat.com> In-Reply-To: <49DE03F0.6070503@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: libvir-list@redhat.com, Anthony Liguori , Gerd Hoffmann , Hollis Blanchard , qemu-devel@nongnu.org Avi Kivity wrote: > Gerd Hoffmann wrote: >> On 04/09/09 16:03, Avi Kivity wrote: >>> I don't want multiplexed monitor sessions, at all. >> >> I'm very happy to finally see them. Finally one can run vms with >> libvirt and *still* access the monitor for debugging and development >> purposes. >> > > Right, I like them for that purpose as well. But not for ordinary control. How do you want to differentiate? What further complications would this bring us? > >>> I want async >>> notifications added to a single monitor session. That too could be >>> implemented today (as simple as a term_printf("notification: ...\n"); >> >> No. It is simple on the qemu side only. Parsing notifications poping >> up at random places in the stream is more complex. > > I don't understand why, if there's a common prefix. > > Everywhere you expect (qemu), also expect notification:. Please no more async notifications to the monitors. They are just ugly to parse, at least for us humans. I don't want to see any notification in the middle of my half-typed command e.g. Jan -- Siemens AG, Corporate Technology, CT SE 2 Corporate Competence Center Embedded Linux