All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Evan Paul <paulev@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: QEMU GUI-Frontend based on Libvert API
Date: Mon, 24 Jul 2006 11:38:18 +0100	[thread overview]
Message-ID: <20060724103818.GA1875@redhat.com> (raw)
In-Reply-To: <44C394A6.4070309@opensourcedemo.com>

On Sun, Jul 23, 2006 at 11:24:22AM -0400, Evan Paul wrote:
> Daniel P. Berrange wrote:
> >I'd actually go so far as to say - if you added support for QEMU in libvirt
> >the 'virt-manager' GUI would 'just work' without need for any further 
> >coding.
> >This is one of the major points of libvirt - you can have multiple backends
> >for different virtualization technologies, but your end user applications 
> >never have to really care (much) about the differences since they are 
> >presented a consistent API. The only real differences will be in the range
> >of virtual hardware devices exposed by each backend & what config options
> >they allow.
> 
> Dan, I have this question regarding virt-manager: Does it currently 
> support actually creating VM. I see features where it provides the 
> ability to configure stuff but saw nothing about creating VM.

That is the main capability under development at this time. I expect it
to be in the next release in 3-4 weeks time.

> Also, does virt-manager have support to actually install/update a 
> particular VMM like XEN or QEMU (when support is avaialble) from the GUI 
> interface itself. If not, that would be a good feature where users can 
> download a given file within the GUI and some script would auto install 
> and set it up.

Installation of the VMM itself is not a job that is applicable to this
application. There are already perfectly good applications for installing
software on Linux - RPM, Debian PKG, etc. By virtue of having the
virt-manager application installed, packaging dependancies will already
have pulled in Xen / QEMU. Windows of course is a completely different
scenario, but I know there are plenty of packaging tools for dealing
with this on Windows, although I've not used them myself.

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  -=| 

  reply	other threads:[~2006-07-24 10:38 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 [this message]
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=20060724103818.GA1875@redhat.com \
    --to=berrange@redhat.com \
    --cc=paulev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.