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:
When tuning memory parameters at domain shutoff, config xml is updated with <memtune> part, but when live tuning domain memory parameters, setting is done without live update domain xml.
Version-Release number of selected component (if applicable):
libvirt-0.10.2-18.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.352.el6.x86_64
kernel-2.6.32-356.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1. tuning memory parameter when domain is shut off
# virsh destroy libvirt_test_api
Domain libvirt_test_api destroyed
# virsh memtune libvirt_test_api --swap-hard-limit -1 --soft-limit -1
# virsh memtune libvirt_test_api --config
hard_limit : 0
soft_limit : unlimited
swap_hard_limit: unlimited
# virsh dumpxml libvirt_test_api
...
<memtune>
<soft_limit unit='KiB'>9007199254740991</soft_limit>
<swap_hard_limit unit='KiB'>9007199254740991</swap_hard_limit>
</memtune>
...
2. tuning memory parameter when domain is on
# virsh start libvirt_test_api
Domain libvirt_test_api started
# virsh memtune libvirt_test_api --live
hard_limit : 25417216
soft_limit : unlimited
swap_hard_limit: unlimited
# virsh memtune libvirt_test_api --swap-hard-limit 25417216000 --soft-limit 2541721600 --live
# virsh memtune libvirt_test_api --live
hard_limit : 25417216
soft_limit : 2541721600
swap_hard_limit: 25417216000
# virsh dumpxml libvirt_test_api
...
<memtune>
<soft_limit unit='KiB'>9007199254740991</soft_limit>
<swap_hard_limit unit='KiB'>9007199254740991</swap_hard_limit>
</memtune>
...
live update did not update the domain xml, it remains as set when domain is off.
Actual results:
memtune did not live update domain xml
Expected results:
memtune should live update domain xml
Additional info:
commit 0047d5d6e86cf84e71b2503c3939fc97c3ffe8b9
Author: Guannan Ren <gren>
Date: Wed Mar 6 00:24:57 2013 +0800
qemu: update domain live xml for virsh memtune with --live flag
virsh subcommand memtune forgot updating domain live xml
after setting cgroup value.
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.
Comment 6RHEL Program Management
2014-04-04 20:58:52 UTC
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.
Description of problem: When tuning memory parameters at domain shutoff, config xml is updated with <memtune> part, but when live tuning domain memory parameters, setting is done without live update domain xml. Version-Release number of selected component (if applicable): libvirt-0.10.2-18.el6.x86_64 qemu-kvm-rhev-0.12.1.2-2.352.el6.x86_64 kernel-2.6.32-356.el6.x86_64 How reproducible: always Steps to Reproduce: 1. tuning memory parameter when domain is shut off # virsh destroy libvirt_test_api Domain libvirt_test_api destroyed # virsh memtune libvirt_test_api --swap-hard-limit -1 --soft-limit -1 # virsh memtune libvirt_test_api --config hard_limit : 0 soft_limit : unlimited swap_hard_limit: unlimited # virsh dumpxml libvirt_test_api ... <memtune> <soft_limit unit='KiB'>9007199254740991</soft_limit> <swap_hard_limit unit='KiB'>9007199254740991</swap_hard_limit> </memtune> ... 2. tuning memory parameter when domain is on # virsh start libvirt_test_api Domain libvirt_test_api started # virsh memtune libvirt_test_api --live hard_limit : 25417216 soft_limit : unlimited swap_hard_limit: unlimited # virsh memtune libvirt_test_api --swap-hard-limit 25417216000 --soft-limit 2541721600 --live # virsh memtune libvirt_test_api --live hard_limit : 25417216 soft_limit : 2541721600 swap_hard_limit: 25417216000 # virsh dumpxml libvirt_test_api ... <memtune> <soft_limit unit='KiB'>9007199254740991</soft_limit> <swap_hard_limit unit='KiB'>9007199254740991</swap_hard_limit> </memtune> ... live update did not update the domain xml, it remains as set when domain is off. Actual results: memtune did not live update domain xml Expected results: memtune should live update domain xml Additional info: