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.
Bug 1625257 - block-commit is not usable with -blockdev setup
Summary: block-commit is not usable with -blockdev setup
Keywords:
Status: CLOSED DUPLICATE of bug 1623986
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev
Version: 7.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Kevin Wolf
QA Contact: Gu Nini
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-04 13:38 UTC by Kevin Wolf
Modified: 2018-09-05 08:58 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-05 08:58:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Kevin Wolf 2018-09-04 13:38:40 UTC
There are two problems that make the block-commit QMP command difficult or impossible to use with a setup where the block graph is built node by node with individual -blockdev options or blockdev-add QMP commands.

1. The block-commit only accepts filenames to identify the top and the base node for the commit operation. However, with individual options set, this can easily cause QEMU to use a json: filename, the exact layout of which is hard to predict. Instead, block-commit should offer options to identify top and base by their node name.

2. Commit automatically reopens the base if it is currently reopened read-only. In a graph built node by node, however, the reopen fails because base->file isn't also reopened and you can't have a read-write format layer on top of a read-only protocol layer. Commit must be changed so that it reopens all relevant nodes so that it can be used even when the base node is opened read-only originally.

The following command line runs into the same problem 2, though I can't say yet if it should work in the end or not (depends on whether the best fix is in reopen itself or in commit's use of reopen):
qemu-io -r -c 'reopen -w' --image-opts driver=qcow2,file.driver=file,file.filename=/tmp/backing.qcow2,file.read-only=on,read-only=on


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