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:
libvirt should check the --granularity value if it is power of 2
Version-Release number of selected component (if applicable):
libvirt-1.2.13-1.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1.# virsh blockcopy --help
...
--granularity <number> power-of-two granularity to use during the copy
--buf-size <number> maximum amount of in-flight data during the copy
...
2.prepare a transient vm and do blockcopy
# virsh blockcopy test3 hda --xml gluster.xml --granularity 513
error: internal error: unable to execute QEMU command 'drive-mirror': Parameter 'granularity' expects power of 2
Actual results:
qemu report error instead libvirt
Expected results:
we already know this value should be power of 2, i think libvirt should check the --granularity value if it is power of 2, and output error early.
Additional info:
I've pushed the patch upstream:
commit 20aca080f37b9f4ca23df8d210400a1f05390c86
Author: Luyao Huang <lhuang>
AuthorDate: Fri Mar 27 17:56:30 2015 +0800
Commit: Michal Privoznik <mprivozn>
CommitDate: Thu Apr 2 11:12:01 2015 +0200
qemuDomainBlockCopy: Check @granularity to be a power of two
https://bugzilla.redhat.com/show_bug.cgi?id=1206479
As described in virDomainBlockCopy() parameters description, the
VIR_DOMAIN_BLOCK_COPY_GRANULARITY parameter may require the value to
have some specific attributes (e.g. be a power of two or fall within a
certain range). And in qemu, a power of two is required. However, our
code does not check that and let qemu operation fail. Moreover, the
virsh man page is not as exact as it could be in this respect.
Signed-off-by: Luyao Huang <lhuang>
Signed-off-by: Michal Privoznik <mprivozn>
v1.2.14-22-g20aca08
We should also add check if the value of granularity is between 4096 and 65536. But it doesn't matter much, so I'd change this bug to verified status after test with libvirt-1.2.16-1.el7.x86_64.
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://rhn.redhat.com/errata/RHBA-2015-2202.html
description of problem: libvirt should check the --granularity value if it is power of 2 Version-Release number of selected component (if applicable): libvirt-1.2.13-1.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1.# virsh blockcopy --help ... --granularity <number> power-of-two granularity to use during the copy --buf-size <number> maximum amount of in-flight data during the copy ... 2.prepare a transient vm and do blockcopy # virsh blockcopy test3 hda --xml gluster.xml --granularity 513 error: internal error: unable to execute QEMU command 'drive-mirror': Parameter 'granularity' expects power of 2 Actual results: qemu report error instead libvirt Expected results: we already know this value should be power of 2, i think libvirt should check the --granularity value if it is power of 2, and output error early. Additional info: