WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 592] New: Para-virtualized Linux memory size cannot be s

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 592] New: Para-virtualized Linux memory size cannot be successfully increased
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Thu, 30 Mar 2006 23:12:41 +0000
Delivery-date: Thu, 30 Mar 2006 23:15:13 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=592

           Summary: Para-virtualized Linux memory size cannot be
                    successfully increased
           Product: Xen
           Version: unstable
          Platform: x86
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Guest-OS
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: john.l.byrne@xxxxxx


If you start a para-virtualized Linux with "memory = 128" and "maxmem = 256" in
the config file, if you do a "xm mem-set domain 256" later, Linux doesn't see
the memory. It looks as if maxmem is never passed to the para-virtualized guest.
If you add the "mem=256M" to the kernel command line, /proc/xen/balloon seems to
indicate that it is ready to do the right thing ("Current allocation" and
"Requested target" are both approximately 128M  has approximately 128M on
"Low-mem balloon "list), but when you try to do a "xm mem-set 256", the
"Requested target" goes to 256M, but the "Xen hard limit" is hit and "Current
allocation" is essentially unchanged.

Behavior on x86_64 is slightly different in that the "Low-free balloon" is zero
even if the "mem=" keyword is specified.

All tests were on SuSE xen 3.0.2_09434-0.

-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 592] New: Para-virtualized Linux memory size cannot be successfully increased, bugzilla-daemon <=