From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, "Daniel Berrange" <berrange@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Kevin Wolf" <kwolf@redhat.com>, "Max Reitz" <mreitz@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>
Subject: [Qemu-devel] [PATCH v3 0/2] qcow2: include LUKS payload overhead in qemu-img measure
Date: Mon, 18 Feb 2019 10:45:23 +0000 [thread overview]
Message-ID: <20190218104525.23674-1-stefanha@redhat.com> (raw)
v3:
* Use encrypt.iter-time=10 to speed up qemu-iotests 178 [Max]
v2:
* Take into account all "encrypt." image creation options since the LUKS
payload size varies depending on the cipher [Max]
The LUKS payload has a significant size (>1 MB). It must be included in the
qemu-img measure calculation so we arrive at the correct minimum image size.
Stefan Hajnoczi (2):
qcow2: include LUKS payload overhead in qemu-img measure
iotests: add LUKS payload overhead to 178 qemu-img measure test
block/qcow2.c | 72 +++++++++++++++++++++++++++++++-
tests/qemu-iotests/178 | 8 ++++
tests/qemu-iotests/178.out.qcow2 | 24 +++++++++++
3 files changed, 103 insertions(+), 1 deletion(-)
--
2.20.1
next reply other threads:[~2019-02-18 10:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 10:45 Stefan Hajnoczi [this message]
2019-02-18 10:45 ` [Qemu-devel] [PATCH v3 1/2] qcow2: include LUKS payload overhead in qemu-img measure Stefan Hajnoczi
2019-02-18 10:45 ` [Qemu-devel] [PATCH v3 2/2] iotests: add LUKS payload overhead to 178 qemu-img measure test Stefan Hajnoczi
2019-02-18 17:30 ` [Qemu-devel] [PATCH v3 0/2] qcow2: include LUKS payload overhead in qemu-img measure 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=20190218104525.23674-1-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=berrange@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=philmd@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).