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-users] More memory problems.

To: Xen List <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] More memory problems.
From: James Pifer <jep@xxxxxxxxxxxxxxxx>
Date: Tue, 06 Oct 2009 15:10:51 -0400
Delivery-date: Tue, 06 Oct 2009 12:12:07 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I have several xen servers running on SLES10SP2. I occasionally have
problems with allocating memory. When this happens the only fix I know
of is to shut down all the domUs and restart the server. Or at least
xend, which affects many of my domUs. 

I have this problem on two servers right now. One of them has plenty of
free memory available. See below:

# xm info
host                   : lakxen04
release                :
version                : #1 SMP Fri Oct 31 14:24:07 UTC 2008
machine                : x86_64
nr_cpus                : 8
nr_nodes               : 1
cores_per_socket       : 4
threads_per_core       : 1
cpu_mhz                : 2500
hw_caps                :
total_memory           : 32765
free_memory            : 9169
max_free_memory        : 10705
max_para_memory        : 10701
max_hvm_memory         : 10667
node_to_cpu            : node0:0-7
node_to_memory         : node0:9169
xen_major              : 3
xen_minor              : 2
xen_extra              : .0_16718_18-0.3
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64 
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : 16718
cc_compiler            : gcc version 4.1.2 20070115 (SUSE Linux)
cc_compile_by          : abuild
cc_compile_domain      : suse.de
cc_compile_date        : Thu Oct  9 15:34:16 UTC 2008
xend_config_format     : 4

When I try to start a domU I get:
# xm start lakvre05
Error: [Errno 12] Cannot allocate memory
Usage: xm start <DomainName>

Start a Xend managed domain
  -p, --paused                   Do not unpause domain after starting
  -c, --console_autoconnect      Connect to the console after the
                                 is created

Any suggestions for working around this or is restarting xend the only


Xen-users mailing list

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