Skip to content

Introducing qcow2 extensions + keep backing file format

Uri Lublin qemu-devel 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 0 repliesNew

Changes from V4 from the cover letter

old commented code deleted.
fix temporary snapshot (e.g. -snapshot) support.

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2Introducing qcow2 extensions + keep backing file formatblock-qcow2.c block.c block.h +1 more+141 -60 replies
2/2qemu-img: adding a "-F base_fmt" option to "qemu-img create -b"qemu-img.c qemu-img.texi+23 -50 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [Qemu-devel] [PATCH 0/2] Introducing qcow2 extensions + keep backing file format

Qcow2 extensions are build of magic (id) len (in bytes) and data. They reside between the end of the header and the filename.

We can keep the backing file format in a such a qcow2 extension, to
1. Provide a way to know the backing file format without probing it (setting the format at creation time).
2. Enable using qcow2 format over host block devices.
(only if the user specifically asks for it, by providing the format at creation time).

I've added bdrv_create2 and drv->bdrv_create2 (implemented only by block-qcow2 currently) to pass the backing-format to create.

Based on a work done by Shahar Frank.

Also fixes a security flaw found by Daniel P. Berrange on [1] which summarizes: "Autoprobing: just say no."

[1] http://lists.gnu.org/archive/html/qemu-devel/2008-12/msg01083.html

Changes from V4:
old commented code deleted.
fix temporary snapshot (e.g. -snapshot) support.