From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Nz8MH-0004jE-CX
	for qemu-devel@nongnu.org; Tue, 06 Apr 2010 08:58:21 -0400
Received: from [140.186.70.92] (port=33976 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Nz8MF-0004hk-Mo
	for qemu-devel@nongnu.org; Tue, 06 Apr 2010 08:58:20 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <avi@redhat.com>) id 1Nz8ME-0001co-7T
	for qemu-devel@nongnu.org; Tue, 06 Apr 2010 08:58:19 -0400
Received: from mx1.redhat.com ([209.132.183.28]:39758)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <avi@redhat.com>) id 1Nz8MD-0001ci-UQ
	for qemu-devel@nongnu.org; Tue, 06 Apr 2010 08:58:18 -0400
Message-ID: <4BBB2FE7.60604@redhat.com>
Date: Tue, 06 Apr 2010 15:58:15 +0300
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
References: <B88AE7FC-34E0-4CF2-88BC-0A11071925D8@suse.de>
	<20100406104704.GJ28689@redhat.com> <4BBB2C83.50103@suse.de>
In-Reply-To: <4BBB2C83.50103@suse.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Re: libvirt vs. in-qemu management
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Alexander Graf <agraf@suse.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel Developers <qemu-devel@nongnu.org>

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