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-users

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: [Xen-users] DomU max memory problem

from [Tej] [Permanent Link][Original]
To: krejca@xxxxxxxxxx
Subject: Re: [Xen-users] DomU max memory problem
From: Tej <bewith.tej@xxxxxxxxx>
Date: Tue, 16 Sep 2008 15:57:17 +0530
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 16 Sep 2008 03:27:54 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=hs5DPitgRSdkSEZg2ZbRtciL8sDoJWO9DUUczdtxl2o=; b=SVbmhZzb8KoOAABVaaELY8IQes+lQoCS4m8nJBdjRnOJpQolDczsdpCAczL3GtIvn+ 3GDDwBt0jE6VT47LvAsdGTazNxy322Y4HnLfbLjmy0ELD7V99FxcQx2COlYDX3GcTNSG WGXZ9D5GoMBhDvSalQlYBVBh6Herhdk/7IZXQ=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=RS4q6ye4nEPHb1KvUPm/D84x6NOdHb1ac3GMUnIGyow89PlSwary4AoTvYJ/SWDBDX xQEmBqUWyTP1BAfGoaUUIG4AHT355UrVZejSQuKsN1gLzOl7eSWbMh+29OMz3lxxfRMg OvEvefKkaWrxEODp2vCbS6ZiLFtrPwGemKyIE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <48CE7906.2050802@xxxxxxxxxx>
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>
References: <48CE7906.2050802@xxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
On 9/15/08, Pavel Krejca <krejca@xxxxxxxxxx> wrote:
> Hi,
>
> when trying to run new domain under xen-3.2.1 with more than 127 MB
> memory set in config file, I get this error message:
> "Error: memory_dynamic_max must be less than or equal to memory_static_max"
>
> 128 MB is probably default value for domu. I tried to raise it by
> "maxmem" option in guest config, but with same result (seems that maxmem
> keyword is ignored by xend). I also tried to increase mem limits with
> "xm mem-max" and "xm mem-set" on running domain, but it has no effect
> unless domain is restarted. But after reboot, I get the same error message.
> Last thing I tried was to hardcode higher default memory limit in
> XendConfig.py (and compiled it to .pyc) but it had no effect too.

check your /etc/xen/xend-config.sxp file for "dom0-min-mem". It should
not be set to 0.

HTH
thanks
-tej

>
> So my question is, how can I start guest domain with memory set to more
> than 128 MB? I suspect this value to be saved somewhere in xend cache,
> but I can't find it. Why does Balloon driver think that only 131064 KiB
> is free? Thanks for answer. My configuration follows:
>
> [xen]# cat /etc/xen/auto/testdomain.cfg
> kernel = "/boot/vmlinuz-xenU"
> cpus = "^0"
> maxmem = 512
> memory = 256
> name = "test_domain"
> vif = ['ip=192.168.0.2,bridge=eth0']
> disk = ['phy:sdb1,sda1,w','phy:sdb2,sda2,w']
> root = "/dev/sda1 ro"
>
> [xen]# tail /var/log/xen/xend.log
> [2008-09-12 15:03:46 11411] DEBUG (XendDomainInfo:84)
> XendDomainInfo.create(['vm', ['name', 'test_domain'], ['memory', 256],
> ['maxmem', 512], ['vcpus', 1], ['on_xend_start', 'ignore'],
> ['on_xend_stop', 'ignore'], ['cpus', '^0'], ['image', ['linux',
> ['kernel', '/boot/vmlinuz-xenU'], ['root', '/dev/sda1 ro']]], ['device',
> ['vbd', ['uname', 'phy:sdb1'], ['dev', 'sda1'], ['mode', 'w']]],
> ['device', ['vbd', ['uname', 'phy:sdb2'], ['dev', 'sda2'], ['mode',
> 'w']]], ['device', ['vif', ['ip', '192.168.0.2'], ['bridge', 'eth0']]]])
> [2008-09-12 15:03:46 11411] DEBUG (XendDomainInfo:1618)
> XendDomainInfo.constructDomain
> [2008-09-12 15:03:46 11411] DEBUG (balloon:132) Balloon: 131072 KiB
> free; need 2048; done.
> [2008-09-12 15:03:46 11411] DEBUG (XendDomain:443) Adding Domain: 6
> [2008-09-12 15:03:46 11411] DEBUG (XendDomainInfo:1703)
> XendDomainInfo.initDomain: 6 256
> [2008-09-12 15:03:46 11411] DEBUG (XendDomainInfo:1738)
> _initDomain:shadow_memory=0x0, memory_static_max=0x20000000,
> memory_static_min=0x0.
> [2008-09-12 15:03:46 11411] DEBUG (balloon:138) Balloon: 131064 KiB
> free; 0 to scrub; need 262144; retries: 20.
> [2008-09-12 15:03:46 11411] DEBUG (balloon:153) Balloon: setting dom0
> target to 3744 MiB.
> [2008-09-12 15:03:46 11411] DEBUG (XendDomainInfo:693) Setting memory
> target of domain Domain-0 (0) to 3744 MiB.
> [2008-09-12 15:03:46 11411] ERROR (XendDomainInfo:1775)
> XendDomainInfo.initDomain: exception occurred
> Traceback (most recent call last):
>   File "usr/lib64/python2.5/site-packages/xen/xend/XendDomainInfo.py",
> line 1747, in _initDomain
>     balloon.free(memory + shadow)
>   File "usr/lib64/python2.5/site-packages/xen/xend/balloon.py", line
> 154, in free
>     dom0.setMemoryTarget(new_alloc_mb)
>   File "usr/lib64/python2.5/site-packages/xen/xend/XendDomainInfo.py",
> line 697, in setMemoryTarget
>     self._safe_set_memory('memory_dynamic_max', target * MiB)
>   File "usr/lib64/python2.5/site-packages/xen/xend/XendDomainInfo.py",
> line 2362, in _safe_set_memory
>     self.info._memory_sanity_check()
>   File "usr/lib64/python2.5/site-packages/xen/xend/XendConfig.py", line
> 366, in _memory_sanity_check
>     raise XendConfigError("memory_dynamic_max must be less " \
> XendConfigError: Invalid Configuration: memory_dynamic_max must be less
> than or equal to memory_static_max
> [2008-09-12 15:03:46 11411] ERROR (XendDomainInfo:440) VM start failed
> Traceback (most recent call last):
>   File "usr/lib64/python2.5/site-packages/xen/xend/XendDomainInfo.py",
> line 420, in start
>     XendTask.log_progress(31, 60, self._initDomain)
>   File "usr/lib64/python2.5/site-packages/xen/xend/XendTask.py", line
> 209, in log_progress
>     retval = func(*args, **kwds)
>   File "usr/lib64/python2.5/site-packages/xen/xend/XendDomainInfo.py",
> line 1778, in _initDomain
>     raise exn
> XendConfigError: Invalid Configuration: memory_dynamic_max must be less
> than or equal to memory_static_max
> [2008-09-12 15:03:46 11411] DEBUG (XendDomainInfo:1897)
> XendDomainInfo.destroy: domid=6
> [2008-09-12 15:03:46 11411] DEBUG (XendDomainInfo:1914)
> XendDomainInfo.destroyDomain(6)
> [2008-09-12 15:03:46 11411] DEBUG (XendDomainInfo:1529) Destroying
> device model
> [2008-09-12 15:03:46 11411] DEBUG (XendDomainInfo:1536) Releasing devices
> [2008-09-12 15:03:46 11411] ERROR (XendDomainInfo:89) Domain
> construction failed
> Traceback (most recent call last):
>   File "usr/lib64/python2.5/site-packages/xen/xend/XendDomainInfo.py",
> line 87, in create
>     vm.start()
>   File "usr/lib64/python2.5/site-packages/xen/xend/XendDomainInfo.py",
> line 420, in start
>     XendTask.log_progress(31, 60, self._initDomain)
>   File "usr/lib64/python2.5/site-packages/xen/xend/XendTask.py", line
> 209, in log_progress
>     retval = func(*args, **kwds)
>   File "usr/lib64/python2.5/site-packages/xen/xend/XendDomainInfo.py",
> line 1778, in _initDomain
>     raise exn
> XendConfigError: Invalid Configuration: memory_dynamic_max must be less
> than or equal to memory_static_max
> [2008-09-12 15:03:46 11411] DEBUG (XendDomainInfo:1897)
> XendDomainInfo.destroy: domid=None
> [2008-09-12 15:03:46 11411] DEBUG (XendDomainInfo:1914)
> XendDomainInfo.destroyDomain(None)
> [2008-09-12 15:03:46 11411] DEBUG (XendDomainInfo:1534) No device model
> [2008-09-12 15:03:46 11411] DEBUG (XendDomainInfo:1536) Releasing devices
>
> [xen]# xm list
> Name                                        ID   Mem VCPUs      State
> Time(s)
> Domain-0                                    0   512     1     r-----
> 258.9
> test_domain                               1   127     1     -b----    220.8
>
> [xen]# free -m
>                    total       used       free     shared    buffers
> cached
> Mem:          3872        372       3500          0         88         55
> -/+ buffers/cache:        227       3644
>
> [xen]# uname -a
> Linux xen 2.6.21-xen #3 SMP Fri Sep 5 17:22:35 CEST 2008 x86_64 Intel(R)
> Xeon(R) CPU E5420 @ 2.50GHz GenuineIntel GNU/Linux
>
>
> Pavel
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: [Xen-users] DomU max memory problem, Pavel Krejca
Next by Date:  Re: [Xen-users] DomU max memory problem, Thinline Maillist
Previous by Thread:  Re: [Xen-users] DomU max memory problem, Pavel Krejca
Next by Thread:  Re: [Xen-users] DomU max memory problem, Thinline Maillist
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy