[prev in list] [next in list] [prev in thread] [next in thread]
List: xen-users
Subject: [Xen-users] xend memory usage is increasing steadily and make dom0
From: dongkyu lee <dongq.lee () gmail ! com>
Date: 2010-04-29 16:52:09
Message-ID: t2s5bff363c1004290952nc58681f2j2c1e951d2847e2e5 () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
I have posted this question a couple of days ago and I am trying to explain
it in more detail.
More than two hundreds Xen VMs has been running more than a year and no xend
memory problems with the only linux vms.
Recently, we decided to use Windows VMs. After that, we have experienced
lack of dom0 memory serveral times
because dom0 memory usage (because of xend) has increased linearly until
dom0 became out of memory.
(Eventually OOM killer make the server reboot)
We created six windows VMs to test memory usage of xend for a week. Now xend
is using 4.6GB memory (out of 32GB)
It is 22% usage of total memory size. Monitoring system shows increasing
line gradually.
After restart xend, memory usage % of xend becomes normal (less 1%)
As work around, we regularly restart xend to prevent dom0 out of memory.
Is it known issue or something wrong with configuration.
SYSTEM INFO
- Xen Version:3.4.1
- dom0 : CentOS 5.3
- Windows : Windows Server 2003 R2
- Physical Server Model: HP DL360G6 (dual socket, QC)
[Windows VM configuration]
import os, re
arch = os.uname()[4]
if re.search('64', arch):
arch_libdir = 'lib64'
else:
arch_libdir = 'lib'
device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
name = "Win01"
memory = "2048"
vcpus = 2
builder = "hvm"
kernel = "/usr/lib/xen/boot/hvmloader"
boot = "dc"
disk = [
'file:/home1/xen/vm_images/Win01,xvda,w','file:/home1/xen/vm_images/win2k3_01.iso,xvdc:cdrom,r']
vif = [ 'bridge=eth1' ]
sdl=0
vnc=1
vnclisten="0.0.0.0"
vncconsole=1
stdvga=0
serial='pty'
on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'restart'
[xm info]
host : tpriv04.covi
release : 2.6.18-164.el5xen
version : #1 SMP Thu Sep 3 04:03:03 EDT 2009
machine : x86_64
nr_cpus : 8
nr_nodes : 1
cores_per_socket : 4
threads_per_core : 1
cpu_mhz : 1995
hw_caps :
bfebfbff:20100800:00000000:00000140:0004e33d:00000000:00000001:00000000
virt_caps : hvm
total_memory : 32762
free_memory : 12
node_to_cpu : node0:0-7
node_to_memory : node0:12
xen_major : 3
xen_minor : 4
xen_extra : .1
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 : unavailable
cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-44)
cc_compile_by : root
cc_compile_domain : gitco.tld
cc_compile_date : Tue Sep 8 22:51:53 CEST 2009
xend_config_format : 4
Thank you in advance.
[Attachment #5 (text/html)]
I have posted this question a couple of days ago and I am trying to explain it in \
more detail.<br><br>More than two hundreds Xen VMs has been running more than a year \
and no xend memory problems with the only linux vms.<br> <div \
class="gmail_quote">Recently, we decided to use Windows VMs. After that, we have \
experienced lack of dom0 memory serveral times<br> because dom0 memory usage (because \
of xend) has increased linearly until dom0 became out of memory.<br>(Eventually OOM \
killer make the server reboot)<br><br>We created six windows VMs to test memory usage \
of xend for a week. Now xend is using 4.6GB memory (out of 32GB)<br>
It is 22% usage of total memory size. Monitoring system shows increasing line \
gradually.<br>After restart xend, memory usage % of xend becomes normal (less \
1%)<br>As work around, we regularly restart xend to prevent dom0 out of memory. <br> \
Is it known issue or something wrong with configuration.<br><br>SYSTEM \
INFO<br><ul><li>Xen Version:3.4.1</li><li>dom0 : CentOS 5.3</li><li>Windows : Windows \
Server 2003 R2</li><li>Physical Server Model: HP DL360G6 (dual socket, QC)<br> \
</li></ul><br>[Windows VM configuration]<br><div style="margin-left: 40px;">import \
os, re<br>arch = os.uname()[4]<br>if re.search('64', arch):<br> \
arch_libdir = 'lib64'<br>else:<br> arch_libdir = 'lib'<br> \
<br>device_model = '/usr/' + arch_libdir + \
'/xen/bin/qemu-dm'<br><br>name = "Win01"<br>memory = \
"2048"<br>vcpus = 2<br>builder = "hvm"<br>kernel = \
"/usr/lib/xen/boot/hvmloader"<br> boot = "dc"<br>disk = [ \
'file:/home1/xen/vm_images/Win01,xvda,w','file:/home1/xen/vm_images/win2k3_01.iso,xvdc:cdrom,r']<br>vif \
= [ 'bridge=eth1' \
]<br><br>sdl=0<br>vnc=1<br>vnclisten="0.0.0.0"<br> \
vncconsole=1<br>stdvga=0<br>serial='pty'<br><br>on_poweroff = \
'destroy'<br>on_reboot = 'restart'<br>on_crash = \
'restart'<br></div><br>[xm info]<br><div style="margin-left: 40px;">host \
: tpriv04.covi<br> release : 2.6.18-164.el5xen<br>version \
: #1 SMP Thu Sep 3 04:03:03 EDT 2009<br>machine : x86_64<br>nr_cpus \
: 8<br>nr_nodes : 1<br>cores_per_socket : 4<br> threads_per_core \
: 1<br>cpu_mhz : 1995<br>hw_caps : \
bfebfbff:20100800:00000000:00000140:0004e33d:00000000:00000001:00000000<br>virt_caps \
: hvm<br>total_memory : 32762<br> free_memory : \
12<br>node_to_cpu : node0:0-7<br>node_to_memory : \
node0:12<br>xen_major : 3<br>xen_minor : 4<br>xen_extra \
: .1<br>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 <br> xen_scheduler : credit<br>xen_pagesize \
: 4096<br>platform_params : virt_start=0xffff800000000000<br>xen_changeset \
: unavailable<br>cc_compiler : gcc version 4.1.2 20080704 (Red Hat \
4.1.2-44)<br> cc_compile_by : root<br>cc_compile_domain : \
gitco.tld<br>cc_compile_date : Tue Sep 8 22:51:53 CEST \
2009<br>xend_config_format : 4<br></div><br><br>Thank you in advance. <br> \
<br><br><br><br><br> </div><br>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic