From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Lrwms-00061s-7M for qemu-devel@nongnu.org; Thu, 09 Apr 2009 12:07:34 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Lrwmn-0005yT-95 for qemu-devel@nongnu.org; Thu, 09 Apr 2009 12:07:33 -0400 Received: from [199.232.76.173] (port=44662 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Lrwmm-0005yA-W1 for qemu-devel@nongnu.org; Thu, 09 Apr 2009 12:07:29 -0400 Received: from mail2.shareable.org ([80.68.89.115]:37093) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Lrwmm-0005Q7-Fd for qemu-devel@nongnu.org; Thu, 09 Apr 2009 12:07:28 -0400 Date: Thu, 9 Apr 2009 17:07:24 +0100 From: Jamie Lokier Subject: Re: [libvirt] Re: [Qemu-devel] [PATCH 1/6] Allow multiple monitor devices (v2) Message-ID: <20090409160724.GC14196@shareable.org> 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> <49DE1125.3080108@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49DE1125.3080108@redhat.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: libvir-list@redhat.com, Jan Kiszka , Anthony Liguori , Gerd Hoffmann , Hollis Blanchard Avi Kivity wrote: > 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. In most cases I think commands like 'stop' or a hotunplug command shouldn't break libvirt or other control program. As long as there's a way for libvirt to query the current hotplug state and be notified of changes, why shouldn't it behave much the same as if you asked libvirt to do do the same action itself? -- Jamie