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:
In virsh, the memtune command is displaying bogus large values when it should be clearly indicating
a word like "unlimited".
virsh # list
Id Name State
----------------------------------
4 Fedora_14_x64 running
virsh # memtune Fedora_14_x64
hard_limit : 9007199254740991
soft_limit : 9007199254740991
swap_hard_limit: 9007199254740991
The number "9007199254740991" here is incorrect.
Version-Release number of selected component (if applicable):
libvirt 0.8.7 and git master
How reproducible:
Every time
Steps to Reproduce:
1. Start a virtual machine using virsh or virt-manager (make sure the guest doesn't have memory limits set)
2. Run the virsh "memtune" command on the running virtual machine
The bug shows up now.
Actual results:
virsh # memtune Fedora_14_x64
hard_limit : 9007199254740991
soft_limit : 9007199254740991
swap_hard_limit: 9007199254740991
Expected results:
virsh # memtune Fedora_14_x64
hard_limit : unlimited
soft_limit : unlimited
swap_hard_limit: unlimited
(or similar wording)
Additional info:
A patch for this is being worked upon in libvirt upstream.
Latest incarnation so far:
https://www.redhat.com/archives/libvir-list/2011-January/msg00441.html
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0596.html
Description of problem: In virsh, the memtune command is displaying bogus large values when it should be clearly indicating a word like "unlimited". virsh # list Id Name State ---------------------------------- 4 Fedora_14_x64 running virsh # memtune Fedora_14_x64 hard_limit : 9007199254740991 soft_limit : 9007199254740991 swap_hard_limit: 9007199254740991 The number "9007199254740991" here is incorrect. Version-Release number of selected component (if applicable): libvirt 0.8.7 and git master How reproducible: Every time Steps to Reproduce: 1. Start a virtual machine using virsh or virt-manager (make sure the guest doesn't have memory limits set) 2. Run the virsh "memtune" command on the running virtual machine The bug shows up now. Actual results: virsh # memtune Fedora_14_x64 hard_limit : 9007199254740991 soft_limit : 9007199254740991 swap_hard_limit: 9007199254740991 Expected results: virsh # memtune Fedora_14_x64 hard_limit : unlimited soft_limit : unlimited swap_hard_limit: unlimited (or similar wording) Additional info: A patch for this is being worked upon in libvirt upstream. Latest incarnation so far: https://www.redhat.com/archives/libvir-list/2011-January/msg00441.html