From: "Daniel P. Berrange" <berrange@redhat.com>
To: joelee724@gmail.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU GUI
Date: Thu, 29 Jun 2006 14:19:17 +0100 [thread overview]
Message-ID: <20060629131917.GA29611@redhat.com> (raw)
In-Reply-To: <44A30AC3.5060104@gmail.com>
On Wed, Jun 28, 2006 at 07:03:31PM -0400, Joe Lee wrote:
> >
> >I would be interested in a GUI that is not specific to QEMU. e.g. Xen/VT,
> >Basilisk II, SheepShaver, etc. ;-)
> Gwenole, can you elaborate more on your comments above. Are your
> comments referring to having a GUI that can both run and manage several
> virtualization product (QEMU, XEN, etc) from one central GUI interface?
> If so, I had a similar thought on this BUT was not sure how possible
> this was. Would like to hear more on what your thoughts are on this.
> Anyone else thought and comments to this would be appreciated!
Its entirely feasible if you have a management API to use which supports
the different virtualization backends. That would allow the GUI to be
written to a single API, and yet control multiple systems like QEMU, Xen,
etc. The libvirt project aims to provide such a backend API, currently
supporting Xen, and a 'mock hypervisor' backend for testing purposes, and
it would be very desirable to have backends to drive QEMU & VMWare systems.
While the GUI would no doubt still have some differences in the area of
hardware /device configuration the bulk of it could be shared by using
the generic libvirt backend. I've got an early prototype of a Python/GTK
based GUI for managing VMs via libvirt:
http://people.redhat.com/berrange/virt-manager/
So if anyone's interested in trying to put together a QEMU backend for
libvirt the project site is http://libvirt.org/
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
next prev parent reply other threads:[~2006-06-29 13:19 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 18:11 [Qemu-devel] QEMU GUI Fabrice Bellard
2006-06-21 19:42 ` Mike Kronenberg
2006-06-22 19:32 ` gbeauchesne
2006-06-22 19:32 ` gbeauchesne
2006-06-28 23:03 ` Joe Lee
2006-06-29 13:19 ` Daniel P. Berrange [this message]
2006-06-29 21:05 ` Joe Lee
2006-06-29 21:47 ` Daniel P. Berrange
2006-06-22 15:06 ` Luca Barbato
2006-07-01 22:47 ` Chris Wilson
2006-07-05 20:51 ` Luca Barbato
2006-07-08 2:14 ` Chris Wilson
2006-07-08 2:46 ` Johannes Schindelin
2006-07-08 6:34 ` M. Warner Losh
2006-07-08 14:34 ` wxWidgets and C: was " Jim C. Brown
2006-07-08 15:02 ` Joe Lee
2006-07-08 15:13 ` Jim C. Brown
2006-07-08 16:34 ` Kevin F. Quinn
2006-07-08 21:26 ` Oliver Gerlich
2006-07-10 0:03 ` John R.
2006-07-10 0:10 ` Jim C. Brown
2006-07-11 7:44 ` David Fraser
2006-07-11 12:40 ` Jason Gress
2006-07-11 13:17 ` Linas Žvirblis
2006-07-11 14:52 ` Oliver Gerlich
2006-07-11 15:29 ` Linas Žvirblis
2006-07-12 8:17 ` Luca Barbato
2006-07-12 13:15 ` [Qemu-devel] Insert module into kernel Tieu Ma Dau
2006-07-12 13:36 ` Paul Brook
2006-07-13 8:11 ` Tieu Ma Dau
2006-06-22 15:18 ` [Qemu-devel] QEMU GUI Christian MICHON
2006-06-30 10:28 ` Dan Sandberg
2006-06-22 21:50 ` Anthony Liguori
2006-06-23 0:18 ` Kevin F. Quinn
2006-06-23 1:53 ` Anthony Liguori
2006-06-23 7:17 ` Kevin F. Quinn
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=20060629131917.GA29611@redhat.com \
--to=berrange@redhat.com \
--cc=joelee724@gmail.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).