From: Sam Eiderman <shmuel.eiderman@oracle.com>
To: kwolf@redhat.com, qemu-block@nongnu.org, qemu-devel@nongnu.org,
mreitz@redhat.com
Cc: liran.alon@oracle.com, shmuel.eiderman@oracle.com,
karl.heubaum@oracle.com, arbel.moshe@oracle.com
Subject: [Qemu-devel] [PATCH v3 0/3] vmdk: Add read-only support for the new seSparse format
Date: Thu, 20 Jun 2019 12:10:54 +0300 [thread overview]
Message-ID: <20190620091057.47441-1-shmuel.eiderman@oracle.com> (raw)
v1:
VMware introduced a new snapshot format in VMFS6 - seSparse (Space
Efficient Sparse) which is the default format available in ESXi 6.7.
Add read-only support for the new snapshot format.
v2:
Fixed after Max's review:
* Removed strict sesparse checks
* Reduced maximal L1 table size
* Added non-write mode check in vmdk_open() on sesparse
v3:
Change non-write mode check in vmdk_open() to bdrv_apply_auto_read_only().
Sam Eiderman (3):
vmdk: Fix comment regarding max l1_size coverage
vmdk: Reduce the max bound for L1 table size
vmdk: Add read-only support for seSparse snapshots
block/vmdk.c | 372 ++++++++++++++++++++++++++++++++++++++++++---
tests/qemu-iotests/059.out | 2 +-
2 files changed, 353 insertions(+), 21 deletions(-)
--
2.13.3
next reply other threads:[~2019-06-20 9:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 9:10 Sam Eiderman [this message]
2019-06-20 9:10 ` [Qemu-devel] [PATCH v3 1/3] vmdk: Fix comment regarding max l1_size coverage Sam Eiderman
2019-06-20 9:10 ` [Qemu-devel] [PATCH v3 2/3] vmdk: Reduce the max bound for L1 table size Sam Eiderman
2019-06-20 9:10 ` [Qemu-devel] [PATCH v3 3/3] vmdk: Add read-only support for seSparse snapshots Sam Eiderman
2019-06-20 13:44 ` [Qemu-devel] [PATCH v3 0/3] vmdk: Add read-only support for the new seSparse format Max Reitz
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=20190620091057.47441-1-shmuel.eiderman@oracle.com \
--to=shmuel.eiderman@oracle.com \
--cc=arbel.moshe@oracle.com \
--cc=karl.heubaum@oracle.com \
--cc=kwolf@redhat.com \
--cc=liran.alon@oracle.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--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).