Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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:
This is another instance of these "we need -blockdev" features. Reassigning to Markus. If there is no RFE for it yet, we can take this one, otherwise this should probably be closed as a duplicate.
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.
(In reply to comment #2)
> Why not use qemu-img to change the meta data?
> Orit, maybe we'll need it for iscsi+block live migration anyway
Dor,We don't need to modify the meta data in iscsi+block live migration.
Comment 7Markus Armbruster
2011-12-02 15:23:59 UTC
I think this is a fair RFE. It needs to be pursued upstream. No ETA, yet.
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.
Comment 27Markus Armbruster
2014-07-16 14:36:48 UTC
Also missing upstream: blockdev-del. Tracked for 7.1 as bug 1086193.
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