Description of problem:
I would like to be able to tell qemu the exact chain of images and let it override the information written within the image metadata
The arg should be something on the line of:
-drive=qcow2:/tmp/A.img,qcow2:/tmp/B.img,raw:/tmp/c.img
The exact formatting is unimportant as long as separators can be escaped and image format can also be specified.
This will allow users that have the base image in multiple location specify the base image on-the-fly without changing the image metadata.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:

Changing the MD is costly and requires write privileged to all the files in the chain.
Also on long chains we might want to have different chains on different hosts (Locally cached templates). This will mean changing the Metadata while a VM is running. And will mean exclusively locking the template because the same VM might want to be used by another VM on another host.
The point is we have to assume base images never change. This changing the metadata before each VM run breaks this assumption.

Basic support is already in 7.0, however even upstream there are a few parts
missing:
* Support for network protocol drivers in blockdev-add
* Modifying backing file options doesn't work for all options yet (e.g. cache)
We're relatively close to implementing these, so I'll leave this BZ for 7.1
for the moment, while keeping cond-nack upstream.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2017:2392

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2017:2392

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2017:2392

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2017:2392

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2017:2392

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2017:2392

Note

You need to
log in
before you can comment on or make changes to this bug.