All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: libvirt vs. in-qemu management
Date: Tue, 06 Apr 2010 15:58:15 +0300	[thread overview]
Message-ID: <4BBB2FE7.60604@redhat.com> (raw)
In-Reply-To: <4BBB2C83.50103@suse.de>

On 04/06/2010 03:43 PM, Alexander Graf wrote:
>
> Does VMware Player support OVF?
> Does VMware Workstation support OVF?
> Does VMware Server support OVF?
> Do older VMware ESX versions support OVF?
> Does it make sense to build an OVF with a Xen PV image?
>
> We need to deliver vendor specific configs anyways. Of course we could
> ship a VMware type, a Xen type and an OVF type. But that would certainly
> not help KVM's awareness because it's hidden underneath the OVF type.
>    

Adding yet another format into the mix isn't helping people who create 
appliances.

> It's also hard to tell people what to use. People know KVM. But people
> don't know what UI KVM does have. Because there is none. I think we're
> losing quite a bit of traction due to that.
>    

Of course there is a UI,  RHEV-M, proxmox, virt-manager, others.  
virt-manager is special in that it also manages other hypervisors.

Note the esx UI is not called esx, it's called vCenter or something.

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2010-04-06 12:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-05 21:11 [Qemu-devel] libvirt vs. in-qemu management Alexander Graf
2010-04-05 22:14 ` [Qemu-devel] " Avi Kivity
2010-04-05 22:29   ` Alexander Graf
2010-04-06 12:09     ` Avi Kivity
2010-04-06 12:28       ` Alexander Graf
2010-04-06 12:41         ` Avi Kivity
2010-04-06 12:51           ` Alexander Graf
2010-04-06 20:15             ` Jamie Lokier
2010-04-06 11:06   ` Daniel P. Berrange
2010-04-06 12:49     ` Alexander Graf
2010-04-06 13:00       ` Daniel P. Berrange
2010-04-06 13:20         ` Alexander Graf
2010-04-06 20:08         ` Jamie Lokier
2010-04-06 10:47 ` Daniel P. Berrange
2010-04-06 12:43   ` Alexander Graf
2010-04-06 12:58     ` Avi Kivity [this message]
2010-04-06 13:39     ` Daniel P. Berrange
2010-04-06 13:53       ` Alexander Graf
2010-04-06 14:06         ` Daniel P. Berrange
2010-04-06 15:06           ` Alexander Graf
2010-04-06 19:43             ` Jamie Lokier
2010-04-06 14:14     ` Richard W.M. Jones

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=4BBB2FE7.60604@redhat.com \
    --to=avi@redhat.com \
    --cc=agraf@suse.de \
    --cc=aliguori@us.ibm.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.