From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: QEMU GUI-Frontend based on Libvert API
Date: Fri, 21 Jul 2006 14:21:21 -0500 [thread overview]
Message-ID: <pan.2006.07.21.19.21.20.193026@codemonkey.ws> (raw)
In-Reply-To: 44C11ED6.3090006@opensourcedemo.com
On Fri, 21 Jul 2006 14:37:10 -0400, Evan Paul wrote:
>
> The libVirt project is a community-sponsored project that aims to bring
> more simplicity and standards to the Linux VM world. At its core,
> libVirt is a C toolkit that provides interaction with virtualization
> capabilities of the Linux operating system (and those related to Linux).
You make it sound so professional :-)
> Currently, there is a project called Virt-Manager that is building a
> GUI-Frontend using the LibVirt API. More info on the Virt-Manager
> project can be found here:
> http://people.redhat.com/berrange/virt-manager/
>
> For me, I personally like the idea and focus of libVirt project and
> would like to see if any QEMU developers from the list would have an
> interest to team up with me to develop an open source GUI-Frontend based
> on the LibVirt API.
Why would you create a second GUI interface when virt-manager already
exists as a libvirt GUI front-end?
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.
I have toyed around with the idea of writing an XML-RPC front-end to QEMU
(with the idea of bridging the gap for libvirt). DV also had a patch
floating around to add a socket management interface to QEMU (although now
there is a TCP character device so I presume his patch is unnecessary).
My first cut at an XML-RPC front-end for QEMU:
http://hg.codemonkey.ws/qemu-rpcd/
Regards,
Anthony Liguori
next prev parent reply other threads:[~2006-07-21 19:21 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 ` Anthony Liguori [this message]
2006-07-21 19:58 ` [Qemu-devel] " 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 ` [Qemu-devel] " Daniel Veillard
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=pan.2006.07.21.19.21.20.193026@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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).