First one doesn't make much sense but oVirt used it before, so we should
allow it now as well. Block copy makes sense and thus should be fixed
either way.

Last patch is for actually validating that it works.

Peter Krempa (5):
  storage_file: create: Create new images with write permission bit
  qemuBlockStorageSourceCreateFormat: Force write access when formatting
    images
  qemu: snapshot: Allow snapshots of read-only disks when we can create
    them
  qemu: blockcopy: Allow copy of read-only disks with -blockdev
  HACK: qemu: caps: enable blockdev reopen

 src/qemu/qemu_block.c                             | 12 ++++++++++++
 src/qemu/qemu_blockjob.c                          |  5 +++++
 src/qemu/qemu_capabilities.c                      |  1 +
 src/qemu/qemu_driver.c                            | 11 ++++++++++-
 src/qemu/qemu_monitor_json.c                      |  2 +-
 src/storage/storage_file_fs.c                     |  6 +-----
 src/storage/storage_file_gluster.c                |  6 +-----
 tests/qemucapabilitiesdata/caps_4.0.0.aarch64.xml |  1 +
 tests/qemucapabilitiesdata/caps_4.0.0.ppc64.xml   |  1 +
 tests/qemucapabilitiesdata/caps_4.0.0.riscv32.xml |  1 +
 tests/qemucapabilitiesdata/caps_4.0.0.riscv64.xml |  1 +
 tests/qemucapabilitiesdata/caps_4.0.0.s390x.xml   |  1 +
 tests/qemucapabilitiesdata/caps_4.0.0.x86_64.xml  |  1 +
 tests/qemucapabilitiesdata/caps_4.1.0.x86_64.xml  |  1 +
 tests/qemucapabilitiesdata/caps_4.2.0.aarch64.xml |  1 +
 tests/qemucapabilitiesdata/caps_4.2.0.ppc64.xml   |  1 +
 tests/qemucapabilitiesdata/caps_4.2.0.s390x.xml   |  1 +
 tests/qemucapabilitiesdata/caps_4.2.0.x86_64.xml  |  1 +
 tests/qemucapabilitiesdata/caps_5.0.0.aarch64.xml |  1 +
 tests/qemucapabilitiesdata/caps_5.0.0.ppc64.xml   |  1 +
 tests/qemucapabilitiesdata/caps_5.0.0.riscv64.xml |  1 +
 tests/qemucapabilitiesdata/caps_5.0.0.x86_64.xml  |  1 +
 tests/qemucapabilitiesdata/caps_5.1.0.x86_64.xml  |  1 +
 23 files changed, 47 insertions(+), 12 deletions(-)

-- 
2.26.2