From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Lrvz0-0004R4-19 for qemu-devel@nongnu.org; Thu, 09 Apr 2009 11:16:02 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Lrvyv-0004QH-66 for qemu-devel@nongnu.org; Thu, 09 Apr 2009 11:16:01 -0400 Received: from [199.232.76.173] (port=40679 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Lrvyu-0004QE-S6 for qemu-devel@nongnu.org; Thu, 09 Apr 2009 11:15:56 -0400 Received: from mx2.redhat.com ([66.187.237.31]:43892) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Lrvyt-0006vL-S1 for qemu-devel@nongnu.org; Thu, 09 Apr 2009 11:15:56 -0400 Message-ID: <49DE1125.3080108@redhat.com> Date: Thu, 09 Apr 2009 18:15:49 +0300 From: Avi Kivity 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> <49DE0C98.5000402@siemens.com> In-Reply-To: <49DE0C98.5000402@siemens.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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: Jan Kiszka Cc: libvir-list@redhat.com, Anthony Liguori , Gerd Hoffmann , Hollis Blanchard , qemu-devel@nongnu.org Jan Kiszka wrote: > 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'm not sure I understand your questions. Multiple monitor sessions are like multiple shell sessions. I don't think a control program should use more than one session, but it should allow a developer to connect to issue 'info registers' and 'x/20i' commands. Of course if a developer issues 'quit' or a hotunplug command, things will break. > > 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. > If we can identify an interactive session, we might redraw the partial command after the prompt. btw, why would a human enable notifications? Note notifications enabled on the management session will only be displayed there. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic.