From: famcool@gmail.com
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, Fam Zheng <famcool@gmail.com>,
hch@lst.de, stefanha@gmail.com
Subject: [Qemu-devel] [PATCH v2 00/12] Adding VMDK monolithic flat support
Date: Fri, 24 Jun 2011 16:18:15 +0800 [thread overview]
Message-ID: <1308903507-10799-1-git-send-email-famcool@gmail.com> (raw)
From: Fam Zheng <famcool@gmail.com>
VMDK multiple file images can not be recognized for now. This patch series is
adding monolithic flat support to it, that is the image type with two
files, one text descriptor file and a plain data file. This type of
image can be created in VMWare, with the options "allocate all disk
space now" and "store virtual disk as a single file" checked.
A VmdkExtent structure is introduced to hold the image "extent"
information, which makes further adding multi extents support of VMDK
easy. An image creating option "flat" is added for creating flat
(preallocated) image.
Fam Zheng (12):
VMDK: introduce VmdkExtent
VMDK: bugfix, align offset to cluster in get_whole_cluster
VMDK: probe for monolithicFlat images
VMDK: separate vmdk_open by format version
VMDK: add field BDRVVmdkState.desc_offset
VMDK: flush multiple extents
VMDK: move 'static' cid_update flag to bs field
VMDK: change get_cluster_offset return type
VMDK: open/read/write for monolithicFlat image
VMDK: create different subformats
VMDK: fix coding style
BlockDriver: add bdrv_get_allocated_file_size() operation
block.c | 19 +
block.h | 1 +
block/raw-posix.c | 21 +
block/raw-win32.c | 29 ++
block/vmdk.c | 1360 +++++++++++++++++++++++++++++++++++++----------------
block_int.h | 2 +
qemu-img.c | 31 +--
7 files changed, 1026 insertions(+), 437 deletions(-)
next reply other threads:[~2011-06-24 8:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-24 8:18 famcool [this message]
2011-06-24 8:18 ` [Qemu-devel] [PATCH v2 01/12] VMDK: introduce VmdkExtent famcool
2011-06-24 8:18 ` [Qemu-devel] [PATCH v2 02/12] VMDK: bugfix, align offset to cluster in get_whole_cluster famcool
2011-06-24 8:18 ` [Qemu-devel] [PATCH v2 03/12] VMDK: probe for monolithicFlat images famcool
2011-06-24 9:56 ` Stefan Hajnoczi
2011-06-24 8:18 ` [Qemu-devel] [PATCH v2 04/12] VMDK: separate vmdk_open by format version famcool
2011-06-24 8:18 ` [Qemu-devel] [PATCH v2 05/12] VMDK: add field BDRVVmdkState.desc_offset famcool
2011-06-24 8:18 ` [Qemu-devel] [PATCH v2 06/12] VMDK: flush multiple extents famcool
2011-06-24 9:58 ` Stefan Hajnoczi
2011-06-24 8:18 ` [Qemu-devel] [PATCH v2 07/12] VMDK: move 'static' cid_update flag to bs field famcool
2011-06-24 8:18 ` [Qemu-devel] [PATCH v2 08/12] VMDK: change get_cluster_offset return type famcool
2011-06-24 8:18 ` [Qemu-devel] [PATCH v2 09/12] VMDK: open/read/write for monolithicFlat image famcool
2011-06-24 10:11 ` Stefan Hajnoczi
2011-06-24 8:18 ` [Qemu-devel] [PATCH v2 10/12] VMDK: create different subformats famcool
2011-06-24 8:18 ` [Qemu-devel] [PATCH v2 11/12] VMDK: fix coding style famcool
2011-06-24 8:18 ` [Qemu-devel] [PATCH v2 12/12] BlockDriver: add bdrv_get_allocated_file_size() operation famcool
2011-06-24 8:24 ` [Qemu-devel] [PATCH v2 00/12] Adding VMDK monolithic flat support Fam Zheng
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=1308903507-10799-1-git-send-email-famcool@gmail.com \
--to=famcool@gmail.com \
--cc=hch@lst.de \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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).