On Fri, Jul 21, 2006 at 02:21:21PM -0500, Anthony Liguori wrote: > As far as I know, the big hurdle for QEMU and libvirt right now is not any > GUI aspects (VNC would work just fine). It's interacting with QEMU. Xen > provides an XML-RPC interface to managing instances whereas QEMU only > really provides the monitor interface. Of course, there's still a bit of > work to do before libvirt uses actually uses that interface (it currently > uses the older S-Expression/HTTP interface). Basically, there's quite a > bit of work to do in libvirt before you could even start writing a GUI for > QEMU.
Yep, it's still in my TODO list. Unfortunately I lost track of QEmu devel recently, so I may need to restart from scratch it seems, but I really want to be able to manage QEmu instances from libvirt. What makes me a bit uneasy is that I didn't really got feedback on my previous patch, so I'm left with the feeling that having work I do integrated might be hard. The two things really needed are the possibility to enumerate quickly what qemu instances are running and then be able to connect to them dynamically to extract informations or control them. The first one could be done by a centralized tool (if if you also caught qemu isntances started on from user shell) or for example by a list of socket in a dedicated directory, the second one would preferably an unix socket or an xml-rpc interface but the later means an XML dependancy and is probably a bit heavy for the task. Is it possible to get some sort of agreement that this would be a good idea to add (then technical issues and patches could be discussed with reasonable expectation that it would end up being integrated) ? Daniel -- Daniel Veillard | Red Hat http://redhat.com/ [EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ _______________________________________________ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
