From: Stefan Hajnoczi <stefanha@gmail.com>
To: Fam Zheng <famcool@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] VMDK development plan for Summer of Code 2011
Date: Wed, 1 Jun 2011 05:29:11 +0100 [thread overview]
Message-ID: <BANLkTim_=bVyLucRyKwysG=X4X-KhBB5SA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinA_FbK32HO2szoCFeYg3SbC12KvQ@mail.gmail.com>
On Sun, May 29, 2011 at 2:19 PM, Fam Zheng <famcool@gmail.com> wrote:
> As a project of Google Summer of Code 2011, I'm now working on
> improving VMDK image support. There are many subformats of VMDK
> virtual disk, some of which have separate descriptor file and others
> don't, some allocate space at once and some others grow dynamically,
> some have optional data compression. The current support of VMDK
> format is very limited, i.e. qemu now supports single file images, but
> couldn't recognize the widely used multi-file types. We have planned
> to add such support to VMDK block driver and enable more image types,
> and the working timeline is set in weeks (#1 to #7) as:
>
> [#1] Monolithic flat layout support
> [#2] Implement compression and Stream-Optimized Compressed Sparse
> Extents support.
> [#3] Improve ESX Server Sparse Extents support.
> [#4] Debug and test. Collect virtual disks with various versions and
> options, test qemu-img with them. By now some patches may be ready to
> deliver.
> [#5, 6] Add multi-file support (2GB extent formats)
> [#7] Clean up and midterm evaluation.
Thanks to Fam's work, we'll hopefully support the latest real-world
VMDK files in qemu-img convert within the next few months.
If anyone has had particular VMDK "problem files" which qemu-img
cannot handle, please reply, they would make interesting test cases.
Stefan
next prev parent reply other threads:[~2011-06-01 4:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-29 13:19 [Qemu-devel] VMDK development plan for Summer of Code 2011 Fam Zheng
2011-06-01 4:29 ` Stefan Hajnoczi [this message]
2011-06-01 8:49 ` Alexander Graf
2011-06-01 9:11 ` Kevin Wolf
2011-06-01 9:13 ` Alexander Graf
2011-06-01 22:11 ` Stefan Hajnoczi
2011-06-06 9:50 ` Kevin Wolf
2011-06-06 10:53 ` Stefan Hajnoczi
2011-06-06 11:08 ` Kevin Wolf
2011-06-06 11:12 ` Stefan Hajnoczi
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='BANLkTim_=bVyLucRyKwysG=X4X-KhBB5SA@mail.gmail.com' \
--to=stefanha@gmail.com \
--cc=famcool@gmail.com \
--cc=kwolf@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).