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 documentation has Mbps (megabits) instead of MBps (megabytes), at least for migration routine virDomainMigrateToURI2 [1]. Though the difference is not too big, it is still approx. 8 times.
Connected issue is #925981
[1] — http://libvirt.org/html/libvirt-libvirt.html#virDomainMigrateToURI2
Fixed upstream by
commit 96c45f66fb5acdce0eb7dc0613d06a15601d9ec7
Author: Ján Tomko <jtomko>
AuthorDate: 2013-04-09 16:15:07 +0200
Commit: Ján Tomko <jtomko>
CommitDate: 2013-04-09 16:45:24 +0200
docs: use MiB/s instead of Mbps for migration speed
We decided not to rebase libvirt in RHEL 6.5 to avoid stability issues
we faced in 6.4. This bug has already been trivially fixed upstream but
it is not considered important enough to be backported to RHEL 6.5.
Thus I'm pushing this bug to RHEL 6.6 (and setting Upstream keyword to
indicate we have patches upstream) for now. If you don't agree with
this resolution, please, give us reasons which you think are strong
enough for us to reevaluate the decision not to backport patches for
this bug.
Verified pass in libvirt-0.10.2-32.el6:
Found 20 "MiB/s" and no "Mbps" in http://libvirt.org/html/libvirt-libvirt.html#virDomainMigrateToURI2
# man virsh | grep "MiB/s" --color
copying bandwidth limit in MiB/s, although for qemu, it may be non-
specifies copying bandwidth limit in MiB/s.
copying bandwidth limit in MiB/s.
Set the maximum migration bandwidth (in MiB/s) for a domain which
Get the maximum migration bandwidth (in MiB/s) for a domain.
Setting VERIFIED.
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.
http://rhn.redhat.com/errata/RHBA-2014-1374.html