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-devel] Small Memory Issue with Xm-Test

To: Dan Smith <danms@xxxxxxxxxx>, Ewan Mellor <ewan@xxxxxxxxxxxxx>, Xen Mailing List <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Small Memory Issue with Xm-Test
From: Daniel Stekloff <dsteklof@xxxxxxxxxx>
Date: Mon, 17 Apr 2006 10:19:58 -0700
Cc: Ryan Harper <ryanh@xxxxxxxxxx>
Delivery-date: Mon, 17 Apr 2006 10:20:26 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
The recent move to the -xen kernel has made the small memory issue
resurface with xm-test. The 15_create_smallmem_pos.py will fail because
the 16 MBs it loads isn't enough, the domain hangs with out of memory
issues. We can't know, ahead of time, the minimal amount of memory that
will allow the domain to boot and work. Xm-Test needs to be adjusted to

Should we?

1) Bump 15_create_smallmem_pos.py to 32 or 64 MBs? Is there a number
that seems reasonable? 

2) Bump the default memory for domains from 64 MBs to something larger?

We can certainly document the issue in xm-test and describe how to bump
memory should an issue occur.

This brings up handling the normal case of domain creation with regard
to small memory. It isn't possible to know ahead of time how much memory
will be needed by the created domain. We could:

1) Patch the xm create process to warn the user if a domain is created
with less than a certain memory amount like 32 or 64 MBs. 

2) Patch the default domain configs to contain a warning about using
small memory amounts and the possible repercussions. 

3) Patch documentation to outline the issue - such as the xm manpage and
the user manual.


I can certainly create the patches. I would like to know what the
consensus is regarding what to do.

I've created bug 616 to track this issue:




Xen-devel mailing list

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