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:
setmaxmem can set a big mem that libvirt cannot parse
Version-Release number of selected component (if applicable):
libvirt-1.2.8-10.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1.prepare a offline vm
# virsh list --all
Id Name State
----------------------------------------------------
- test4 shut off
2.setmaxmem to a big value to it:
# virsh setmaxmem test4 10000000T
3.check the guest xml:
<memory unit='KiB'>10737418240000000</memory>
4.restart libvirtd guest will disappear
# service libvirtd restart
Redirecting to /bin/systemctl restart libvirtd.service
# virsh setmaxmem test4 10000000T
error: failed to get domain 'test4'
error: Domain not found: no domain with matching name 'test4'
Actual results:
this value is too large to parse for libvirt
Expected results:
cannot set a cannot parse mem via setmaxmem
Now pushed upstream:
commit 3511c12244beb289dd44503739d65b0e823685cd
Author: Ján Tomko <jtomko>
CommitDate: 2015-05-14 17:17:40 +0200
reject out of range memory in SetMemory APIs
The APIs take the memory value in KiB and we store it in KiB
internally, but we cannot parse the whole ULONG_MAX range
on 64-bit systems, because virDomainParseScaledValue
needs to fit the value in bytes in an unsigned long long.
https://bugzilla.redhat.com/show_bug.cgi?id=1176739
git describe: v1.2.15-84-g3511c12
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: setmaxmem can set a big mem that libvirt cannot parse Version-Release number of selected component (if applicable): libvirt-1.2.8-10.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1.prepare a offline vm # virsh list --all Id Name State ---------------------------------------------------- - test4 shut off 2.setmaxmem to a big value to it: # virsh setmaxmem test4 10000000T 3.check the guest xml: <memory unit='KiB'>10737418240000000</memory> 4.restart libvirtd guest will disappear # service libvirtd restart Redirecting to /bin/systemctl restart libvirtd.service # virsh setmaxmem test4 10000000T error: failed to get domain 'test4' error: Domain not found: no domain with matching name 'test4' Actual results: this value is too large to parse for libvirt Expected results: cannot set a cannot parse mem via setmaxmem