qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Veillard <veillard@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: QEMU GUI-Frontend based on Libvert API
Date: Wed, 26 Jul 2006 08:47:02 -0400	[thread overview]
Message-ID: <20060726124702.GA12588@redhat.com> (raw)
In-Reply-To: <pan.2006.07.21.19.21.20.193026@codemonkey.ws>

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/
veillard@redhat.com  | libxml GNOME XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/

      parent reply	other threads:[~2006-07-26 12:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-21 18:37 [Qemu-devel] QEMU GUI-Frontend based on Libvert API Evan Paul
2006-07-21 19:21 ` [Qemu-devel] " Anthony Liguori
2006-07-21 19:58   ` Joe Lee
2006-07-21 20:57     ` [Qemu-devel] " Anthony Liguori
2006-07-21 21:15       ` Linas Žvirblis
2006-07-21 22:01         ` [Qemu-devel] " Anthony Liguori
2006-07-21 22:37           ` Linas Žvirblis
2006-07-23 11:39   ` [Qemu-devel] " Daniel P. Berrange
2006-07-23 15:24     ` Evan Paul
2006-07-24 10:38       ` Daniel P. Berrange
2006-07-23 16:34     ` [Qemu-devel] " Anthony Liguori
2006-07-24 17:01       ` James Olsen
2006-07-26 12:47   ` Daniel Veillard [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060726124702.GA12588@redhat.com \
    --to=veillard@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).