From: "Richard W.M. Jones" <rjones@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel Developers <qemu-devel@nongnu.org>,
Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] Re: libvirt vs. in-qemu management
Date: Tue, 6 Apr 2010 15:14:00 +0100 [thread overview]
Message-ID: <20100406141400.GA26291@amd.home.annexia.org> (raw)
In-Reply-To: <4BBB2C83.50103@suse.de>
On Tue, Apr 06, 2010 at 02:43:47PM +0200, Alexander Graf wrote:
> Does VMware Player support OVF?
> Does VMware Workstation support OVF?
> Does VMware Server support OVF?
Yes, but "OVF" is a rather loose term here. OVF isn't too
well standardized. But ...
> Does it make sense to build an OVF with a Xen PV image?
This hits on the fundamental problem. What your guest might require
could be different from what the hypervisor could provide. Your guest
could require Xen paravirtualization, or even just an obscure network
card which the hypervisor cannot supply.
It's a bit easier if you are building pre-packaged appliances (these
have multiple other problems such as their size, and how they get
updated).
V2V conversion of random guests from another hypervisor to KVM is a
very hard problem, something that we're working on with virt-v2v. We
certainly don't go via OVF, and we do lots of tinkering inside the
guest (eg. installing new kernels).
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming blog: http://rwmj.wordpress.com
Fedora now supports 80 OCaml packages (the OPEN alternative to F#)
http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora
prev parent reply other threads:[~2010-04-06 14:14 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
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 [this message]
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=20100406141400.GA26291@amd.home.annexia.org \
--to=rjones@redhat.com \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.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).