From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KWbsv-00065O-JR for qemu-devel@nongnu.org; Fri, 22 Aug 2008 15:01:21 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KWbsu-00063o-Iv for qemu-devel@nongnu.org; Fri, 22 Aug 2008 15:01:21 -0400 Received: from [199.232.76.173] (port=37869 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KWbsu-00063h-FS for qemu-devel@nongnu.org; Fri, 22 Aug 2008 15:01:20 -0400 Received: from mail2.shareable.org ([80.68.89.115]:45090) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KWbst-0004Wl-QD for qemu-devel@nongnu.org; Fri, 22 Aug 2008 15:01:20 -0400 Date: Fri, 22 Aug 2008 20:01:12 +0100 From: Jamie Lokier Subject: Re: [Xen-devel] Re: [Qemu-devel] [PATCH 12/13] set vnc password from xenstore. Message-ID: <20080822190112.GF24179@shareable.org> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080821214806.GJ1531@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: "Daniel P. Berrange" , qemu-devel@nongnu.org Cc: xen-devel@lists.xensource.com, Gerd Hoffmann Daniel P. Berrange wrote: > On Thu, Aug 21, 2008 at 11:34:41PM +0200, Gerd Hoffmann wrote: > > Hi, > > > > > If there are reasons that Xend doesn't want to interact with the monitor > > > (for instance, if you want to support monitor redirection), we can > > > certainly discuss how to enhance the monitor (like having multiple > > > monitor instances). > > > > 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. If there were multiple monitor instances, you could filter them _all_ through libvirt, so it would always know the VM state. That's what I do in my vM manager script. User can connect to the manager's socket and send a monitor command. It's forwarded to QEMU, but some filtering so the script knows what's going on, e.g. when changing CD-ROM, starting/stopping the CPU etc. You can't do that nicely now, though, because some commands take a long time to execute. Also, there's no nice way to wait for events like "tell me when the guest reboots the CPU" at the moment. -- Jamie