From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MJ4AL-0004eI-5R for qemu-devel@nongnu.org; Tue, 23 Jun 2009 07:27:53 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MJ4AG-0004bs-Bq for qemu-devel@nongnu.org; Tue, 23 Jun 2009 07:27:52 -0400 Received: from [199.232.76.173] (port=55747 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MJ4AF-0004bR-Fm for qemu-devel@nongnu.org; Tue, 23 Jun 2009 07:27:47 -0400 Received: from mx2.redhat.com ([66.187.237.31]:40138) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MJ4AE-0003Zr-VM for qemu-devel@nongnu.org; Tue, 23 Jun 2009 07:27:47 -0400 Message-ID: <4A40BC66.8040206@redhat.com> Date: Tue, 23 Jun 2009 14:28:38 +0300 From: Avi Kivity MIME-Version: 1.0 References: <20090623013005.39e27923@doriath> <4A409A4D.8030605@siemens.com> <20090623100428.GD6881@redhat.com> <4A40AA3D.2050807@siemens.com> <4A40AB9D.6040204@redhat.com> <4A40B467.7000604@siemens.com> In-Reply-To: <4A40B467.7000604@siemens.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCH 11/11] QMP: Command-line flag to enable control mode List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: aliguori@us.ibm.com, ehabkost@redhat.com, dlaor@redhat.com, qemu-devel@nongnu.org, Luiz Capitulino On 06/23/2009 01:54 PM, Jan Kiszka wrote: >> It would be a nightmare, consider both libvirt and a user hotplugging >> something into the same pci slot, or a user starting migration, or >> quitting, or ... >> > > Migration, yes, but hot-plugging is resolvable - given config update events. > I'm not saying it's impossible, just that we don't want to do it. >> Having -monitor readonly makes sense. >> > > But not for all features, only those libvirt is capable to handle (I > think there are quite a few qemu specifics libvirt does not bother > about) and only as long as there is no proper synchronization. Again, > migration and save/restore will continue to require exclusive access, > but the rest is just a question of proper synchronization IMHO. > If libvirt "doesn't bother" about something useful, that's a libvirt bug. It's wierd to have something controlled by two parallel management channels. > See, I don't want to kill my management app just because I attached to a > guest via gdb and start injecting reconfiguration events for testing > purposes (e.g. attach/detach a USB device for which I develop a driver). > You're talking about a usb developer, not a qemu developer, working in some virtual lab environment? In that case, libvirt and the management app should certainly support usb. A random usb developer shouldn't need to ever talk to the qemu monitor. -- error compiling committee.c: too many arguments to function