This bug has been copied from bug #584683 and has been proposed to be backported to 5.5 z-stream (EUS).
in 2.6.18-194.5.1.el5
As the result parts show unfriendly in the previous comments,Correct it again. Version |Result ===================+============================================================= 2.6.18-194.el5 |Run out of mem |Show message "'vballoon: page allocation failure.order:0, |mode:0x210d2'."This happens *after* the emergency reserve |pages from the kernel have been used. |Detail in log-2.6.18-194 |FAIL -------------------+------------------------------------------------------------- 2.6.18-194.7.1.el5 |Run out of me |can not see message "'vballoon: page allocation |failure.order:0, mode:0x210d2'."means it's just |going to relax and find pages in a later run. |Detail in log-2.6.18-194.7.1 |PASS ===================+============================================================= So this bug has been fixed in kernel 2.6.18-194.7.1.el5,can be closed.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: The virtio balloon driver was able to access the virtual guest's kernel's reservation pools in order to satisfy a balloon request, which could have caused a kernel of the virtual guest to run out of memory when attempting to satisfy the host operating system's request to donate free memory pages. This has been fixed so that virtual guests do not run out of memory when guest memory usage is high.
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/RHSA-2010-0504.html