after shutdown many domu, the memory is not release to dom0,
before:
host: 8g phy memory
16g swap (4g used)
dom0: 600m
domu: consumed all memory, no new domu could be created
after shutdown many domu:
host: 8g phy memory
16g swap (4g used)
dom0: 600m
domu: 2g
why memory of dom0 is still 600m? how to release more to dom0?
pls advise.
Yahoo!香港提供網上安全攻略，教你如何防範黑客! 請前往 http://hk.promo.yahoo.com/security/ 了解更多!
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Mon, Jan 25, 2010 at 4:45 PM, Aclhk Aclhk <aclhkaclhk@ymail.com> wrote:> > after shutdown many domu, the memory is not release to dom0,> why memory of dom0 is still 600m?that''s the way it works. The memory goes to available memory managed by hypervisor. Run "xm info" when domU is running and stopped, look for "free_memory"> how to release more to dom0?xm mem-set 0 .... but most likely you don''t want that. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I just tried i could adjust using virtual machine manager.
1. could i change by xm or virsh or other commands?
2. why the memory allocation not dynamically adjusted upon domu releasing
memory?
--- 2010年1月25日 星期一，Aclhk Aclhk <aclhkaclhk@ymail.com> 寫道﹕
寄件人: Aclhk Aclhk <aclhkaclhk@ymail.com>
主題: [Xen-users] memory not released to dom0
收件人: xen-users@lists.xensource.com
日期: 2010年1月25日,星期一,上午9:45
after shutdown many domu, the memory is not release to dom0,
before:
host: 8g phy memory
16g swap (4g used)
dom0: 600m
domu: consumed all memory, no new domu could be created
after shutdown many domu:
host: 8g phy memory
16g swap (4g used)
dom0: 600m
domu: 2g
why memory of dom0 is still 600m? how to release more to dom0?
pls advise.
Yahoo!香港提供網上安全攻略，教你如何防範黑客!了解更多
-----內含下列附件-----
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Yahoo!香港提供網上安全攻略，教你如何防範黑客! 請前往 http://hk.promo.yahoo.com/security/ 了解更多!
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
> xm mem-set 0 .... > > but most likely you don''t want that. >What exactly does "xm mem-set 0"? How does it affect running domU''s? Just thinking in terms of the "Cannot allocate memory" error.... Thanks, James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Jan 25, 2010 at 01:45:19AM -0800, Aclhk Aclhk wrote:> after shutdown many domu, the memory is not release to dom0, > > before: > host: 8g phy memory > 16g swap (4g used) > dom0: 600m > domu: consumed all memory, no new domu could be created > > after shutdown many domu: > host: 8g phy memory > 16g swap (4g used) > dom0: 600m > domu: 2g > > why memory of dom0 is still 600m? how to release more to dom0? >Please see this wiki page: http://wiki.xensource.com/xenwiki/XenBestPractices Xen dom0 shouldn''t have all the memory visible to it in the first place! "xm info" will show you the free memory in the Xen hypervisor. -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Jan 25, 2010 at 9:32 PM, James Pifer <jep@obrien-pifer.com> wrote:> >> xm mem-set 0 .... >> >> but most likely you don''t want that. >> > > What exactly does "xm mem-set 0"?"xm mem-set" sets the memory for a domain. For example, if you run "xm mem-set 0 1024M", you set dom0 memory to 1024M> How does it affect running domU''s?it shouldn''t. It will only affect running domUs if you run "xm mem-set" on a domU.> Just thinking in terms of the "Cannot allocate memory" error....Your problem is different. I''d look and see why your xend uses so much memory. For example, on my setup xend uses around 300M memory with 40M res. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Jan 26, 2010 at 12:59 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote:> Please see this wiki page: > http://wiki.xensource.com/xenwiki/XenBestPracticesIMHO you should also add dedicating a core/CPU to dom0 on that page. IIRC, the purpose is not just so dom0 always get enough CPU time, but also to reduce the number of CPU context switches. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Jan 26, 2010 at 10:14:39AM +0700, Fajar A. Nugraha wrote:> On Tue, Jan 26, 2010 at 12:59 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > > Please see this wiki page: > > http://wiki.xensource.com/xenwiki/XenBestPractices > > IMHO you should also add dedicating a core/CPU to dom0 on that page. > IIRC, the purpose is not just so dom0 always get enough CPU time, but > also to reduce the number of CPU context switches. >That''s here.. since I was not sure if it''s a best practice or not: http://wiki.xensource.com/xenwiki/XenCommonProblems -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Jan 26, 2010 at 1:58 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote:> That''s here.. since I was not sure if it''s a best practice or not: > http://wiki.xensource.com/xenwiki/XenCommonProblemsGood point. We need a "standard" criteria on what a "best practice" is :D As far as dedicated dom0 CPU goes, there''s this entry from http://www.cl.cam.ac.uk/research/srg/netos/xen/readmes/user/user.html "If you are running IO intensive tasks, its typically better to dedicate either a hyperthread or whole core to running domain 0, and hence pin other domains so that they can''t use CPU 0. If your workload is mostly compute intensive, you may want to pin vcpus such that all physical CPU threads are available for guest domains." Since in my environment I/O (disk and network) becomes the bottleneck, it''s a best practice for me. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Jan 26, 2010 at 06:16:26PM +0700, Fajar A. Nugraha wrote:> On Tue, Jan 26, 2010 at 1:58 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > > That''s here.. since I was not sure if it''s a best practice or not: > > http://wiki.xensource.com/xenwiki/XenCommonProblems > > Good point. We need a "standard" criteria on what a "best practice" is :D >Yeah :)> As far as dedicated dom0 CPU goes, there''s this entry from > http://www.cl.cam.ac.uk/research/srg/netos/xen/readmes/user/user.html > > "If you are running IO intensive tasks, its typically better to > dedicate either a hyperthread or whole core to running domain 0, and > hence pin other domains so that they can''t use CPU 0. If your workload > is mostly compute intensive, you may want to pin vcpus such that all > physical CPU threads are available for guest domains." > > Since in my environment I/O (disk and network) becomes the bottleneck, > it''s a best practice for me. >Well.. I''ll add a note of this to XenBestPractices :) -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users