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.
I've noticed that bug 1069407 has to be resolved first before we can tackle this. On top of the effort of exposing the backing chain in domain XML, the additional steps required are to have libvirt pre-create the temporary qcow2 wrapper before starting the domain, recording the file it created (probably as a subelement of transient), and tearing down the file when the domain exits. There's additional work to make sure that migration plays nicely with transient disks, and that block chain operations (pull, commit, mirror) are properly prevented and/or safe to do at the same time as a transient image. It's enough work that ought to be tackled upstream first, so it is not obvious when it will be ready for inclusion in RHEL.
(In reply to Eric Blake from comment #6)
>
> *** This bug has been marked as a duplicate of bug 1040068 ***
Swapping the duplicate; the public bug should be the master, not the private.