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 1695558 - the default value of migration max-postcopy-bandwidth should not be 0 and no unit when check it in hmp /qmp
Summary: the default value of migration max-postcopy-bandwidth should not be 0 and no ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: qemu-kvm
Version: 9.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Dr. David Alan Gilbert
QA Contact: Li Xiaohui
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-03 11:03 UTC by Li Xiaohui
Modified: 2022-03-01 07:27 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-01 07:27:22 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Li Xiaohui 2019-04-03 11:03:37 UTC
Description of problem:
via qmp or hmp command, found the default value of migration max-postcopy-bandwidth is 0, and no unit


Version-Release number of selected component (if applicable):
host info:
src host: kernel-4.18.0-80.5.el8.x86_64 & qemu-img-3.1.0-20.module+el8+2904+e658c755.x86_64
dst host: kernel-4.18.0-80.el8.x86_64 & qemu-img-3.1.0-20.module+el8+2904+e658c755.x86_64
guest info:
kernel-4.18.0-73.el8.x86_64


How reproducible:
100%


Steps to Reproduce:
1.boot guest on src host
2.via hmp or qmp, check max-postcopy-bandwidth default value:
(1) hmp 
(qemu) info migrate_parameters 
...
max-bandwidth: 33554432 bytes/second
downtime-limit: 300 milliseconds
x-checkpoint-delay: 20000
block-incremental: off
x-multifd-channels: 2
x-multifd-page-count: 16
xbzrle-cache-size: 67108864
max-postcopy-bandwidth: 0
(2)qmp
{"execute":"query-migrate-parameters"}
{"return": {"xbzrle-cache-size": 67108864, "cpu-throttle-initial": 20, "decompress-threads": 2, "compress-threads": 8, "compress-level": 1, "block-incremental": false, "compress-wait-thread": true, "downtime-limit": 300, "tls-creds": "", "x-multifd-page-count": 16, "max-cpu-throttle": 99, "max-postcopy-bandwidth": 0, "tls-hostname": "", "x-multifd-channels": 2, "max-bandwidth": 33554432, "x-checkpoint-delay": 20000, "cpu-throttle-increment": 10}}


Actual results:
like above step 2


Expected results:
from step 2
(1)the default value of migration max-postcopy-bandwidth should not be 0
(2)via hmp command, there no unit about the value of max-postcopy-bandwidth, should like max-bandwidth, has unit such as "bytes/second"


Additional info:
(1)when use the default max-postcopy-bandwidth value "0" to migrate, found throughput is not 0 after migration finished:
(qemu) info migrate
globals:
...
Migration status: completed
total time: 18789 milliseconds
downtime: 22 milliseconds
setup: 19 milliseconds
transferred ram: 1974360 kbytes
throughput: 861.76 mbps

Comment 3 Dr. David Alan Gilbert 2019-04-08 12:12:36 UTC
The '0' is unlimited, which is the default unless something sets it - so that I don't think is really
a bug.
I should fix the lack of units.

Comment 4 Li Xiaohui 2019-04-08 14:46:40 UTC
(In reply to Dr. David Alan Gilbert from comment #3)
> The '0' is unlimited, which is the default unless something sets it - so
> that I don't think is really
> a bug.
> I should fix the lack of units.

ok.
There other parameters are lack of units(x-checkpoint-delay,xbzrle-cache-size,...)when execute "info migrate_parameters" in hmp, feel free to fix if you think need.

Comment 5 Ademar Reis 2020-02-05 22:56:10 UTC
QEMU has been recently split into sub-components and as a one-time operation to avoid breakage of tools, we are setting the QEMU sub-component of this BZ to "General". Please review and change the sub-component if necessary the next time you review this BZ. Thanks

Comment 8 RHEL Program Management 2021-03-15 07:34:52 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 9 Li Xiaohui 2021-09-01 02:29:09 UTC
Could still reproduce bz on rhelav-8.5 and rhel9.
According to Comment 3: fix the lack of units about max-postcopy-bandwidth, so reopen this bz.

Comment 11 John Ferlan 2021-09-08 21:28:01 UTC
Move RHEL-AV bugs to RHEL9. If necessary to resolve in RHEL8, then clone to the current RHEL8 release.

Comment 13 RHEL Program Management 2022-03-01 07:27:22 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


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