This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-bugs] [Bug 651] New: kernel panic when set dom0 to value less than

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 651] New: kernel panic when set dom0 to value less than 1 to 2 % of host mem
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Wed, 17 May 2006 12:39:37 -0700
Delivery-date: Wed, 17 May 2006 12:40:17 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

           Summary: kernel panic when set dom0 to value less than 1 to 2 %
                    of host mem
           Product: Xen
           Version: unstable
          Platform: x86-64
        OS/Version: Linux-2.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: krysans@xxxxxxxxxx
                CC: aravindh.puthiyaparambil@xxxxxxxxxx

Running on Unisys ES7000/one with 16 GB of RAM; dom0 is allocated almost all of
the memory.  I issued xm mem-set 0 256 to decrease dom0's memory to 256 MB. 
Using xentop, I see the amount of memory allocated to dom0 slowly decrease.   
Using SLES10 Beta 11 upgraded to xen changeset 9994. The serial console output
indicates out of memory condition and is attached.  

In devel list, Keir indicated:
I don't think this behaviour is surprising. The kernel is probably 
taking about 1% of memory to track memory usage. So trying to balloon 
down to 1-2% of your initial memory reservation is rather harsh.

The 'fix' here is to stop users being able to shoot their feet off, by 
setting a lower bound on ballooning that is related to the initial 
memory size of the guest, and/or quiesce the balloon driver when 
low-memory and out-of-memory code paths are executed in the guest.

Aravindh is looking into a fix for this and will send in a patch.

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>