From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KWQiM-0008OP-4L for qemu-devel@nongnu.org; Fri, 22 Aug 2008 03:05:42 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KWQiH-0008Mh-PA for qemu-devel@nongnu.org; Fri, 22 Aug 2008 03:05:41 -0400 Received: from [199.232.76.173] (port=53020 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KWQiH-0008Me-K6 for qemu-devel@nongnu.org; Fri, 22 Aug 2008 03:05:37 -0400 Received: from mx20.gnu.org ([199.232.41.8]:41488) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KWQiG-0007hV-PG for qemu-devel@nongnu.org; Fri, 22 Aug 2008 03:05:37 -0400 Received: from mx1.redhat.com ([66.187.233.31]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KWQhB-0007ur-A2 for qemu-devel@nongnu.org; Fri, 22 Aug 2008 03:04:29 -0400 Message-ID: <48AE64F5.3090303@redhat.com> Date: Fri, 22 Aug 2008 09:04:21 +0200 From: Gerd Hoffmann MIME-Version: 1.0 Subject: Re: [Xen-devel] Re: [Qemu-devel] [PATCH 12/13] set vnc password from xenstore. References: <1219336054-15919-1-git-send-email-kraxel@redhat.com> <1219336054-15919-13-git-send-email-kraxel@redhat.com> <48ADCCA2.8050201@codemonkey.ws> <20080821201955.GG1531@redhat.com> <48ADCE91.2070602@codemonkey.ws> <48ADDF71.5040209@redhat.com> <20080821214806.GJ1531@redhat.com> In-Reply-To: <20080821214806.GJ1531@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: "Daniel P. Berrange" Cc: xen-devel@lists.xensource.com, qemu-devel@nongnu.org Daniel P. Berrange wrote: >> Multiple monitor instances would be very useful anyway. >> >> Right now there is no way to use the monitor for libvirt-managed qemu >> instances because libvirt uses the monitor. Being able to both use >> libvirt *and* have a monitor prompt to type commands would be great. > > I disagree - that means you'll no longer be able to trust what libvirt > tells you about the VM, and libvirt won't have a guarenteed consistent > view of the VM's state because things will be changed behind its back. It is *not* the only purpose of the monitor to confuse libvirt. The whole 'info ' command family is very useful for development and debugging purposes and it will not interfere at all with libvirt. I can't stand your attitude to refuse any feature just because you fear users might abuse it. That applies to almost any feature which makes life easier for developers. Which in turn means using libvirt for development is either a bit complicated or impossible. cheers, Gerd -- http://kraxel.fedorapeople.org/xenner/