Cset 15328 from xen-3.1-testing.hg returns memory to dom0 if an autoballoon attempt fails. It is recommended for inclusion in RHEL 5.2
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
This request was previously evaluated by Red Hat Product Management for inclusion in the current Red Hat Enterprise Linux release, but Red Hat was unable to resolve it in time. This request will be reviewed for a future Red Hat Enterprise Linux release.
Created attachment 331572 [details] Bug fix Before ballooning memory and allocating new memory to a new domain it saves the current dom0 memory status and if autobaloon fails, it gives memory back to dom0 by restoring the memory size allocated to dom0. It's backport of upstream at http://xenbits.xensource.com/xen-3.1-testing.hg?rev/73f18a202ea3 . Works fine for me, tested on RHEL x86_64. Michal
A test package which fixes this issue (and several others as well) has been made available at: http://people.redhat.com/jdenemar/xen/ Could the reporter try it out and report if it fixes the problem or not? Thank you for your cooperation.
Fix built into xen-3.0.3-81.el5
Could you please help give this bug test steps? Thanks. (Because it is hard to make autoballoon fail)
(In reply to comment #7) > Could you please help give this bug test steps? Thanks. > (Because it is hard to make autoballoon fail) You should be able to make autoballoon fail pretty easily by changing the dom0-min-mem parameter in /etc/xen/xend-config.sxp. So, assuming you have 4GB of memory, do something like: (dom0-min-mem 2048) And then try to start a 3GB guest; that should cause the auto-balloon to fail, and then you should be able to validate that this is fixed. Chris Lalancette
Verified on xen-3.0.3-91.el5 PASS
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-2009-1328.html