Hi, We have the dom0_mem=512M parameter set on boot which does show up after booting however ive noticed that it drops to roughly 256M on one of the boxes after the VMs are all started which is causing slow downs as it needs to swap. The kernel is 2.6.32.43, has anyone else seen this? Thanks Ian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, Aug 17, 2011 at 2:35 PM, Ian Tobin <itobin@tidyhosts.com> wrote:> Hi, > > > > We have the dom0_mem=512M parameter set on boot which does show up after > booting however ive noticed that it drops to roughly 256M on one of the > boxes after the VMs are all started which is causing slow downs as it needs > to swap.IIRC that is expected behaviour, no matter what version the kernel is.> The kernel is 2.6.32.43, has anyone else seen this?dom0_mem only sets dom0''s initial memory. If domU needs more memory, dom0 can still baloon down. See dom0-min-mem and enable-dom0-ballooning on /etc/xen/xend-config.sxp to change this behavior. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hey, I set the dom0 min men to 512m in xend-config.sxp and ballooning is already enabled. I rebooted and it initially shows 512m but one the vms are booted it drops to 256 . Any other thoughts? Thanks On 17 Aug 2011, at 10:44, "Fajar A. Nugraha" <list@fajar.net> wrote:> On Wed, Aug 17, 2011 at 2:35 PM, Ian Tobin <itobin@tidyhosts.com> wrote: >> Hi, >> >> >> >> We have the dom0_mem=512M parameter set on boot which does show up after >> booting however ive noticed that it drops to roughly 256M on one of the >> boxes after the VMs are all started which is causing slow downs as it needs >> to swap. > > IIRC that is expected behaviour, no matter what version the kernel is. > >> The kernel is 2.6.32.43, has anyone else seen this? > > dom0_mem only sets dom0''s initial memory. If domU needs more memory, > dom0 can still baloon down. See dom0-min-mem and > enable-dom0-ballooning on /etc/xen/xend-config.sxp to change this > behavior. > > -- > Fajar > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Try to paste the output of "xm info" and "xm list". -Shunli -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Ian Tobin Sent: Thursday, August 18, 2011 2:03 PM To: Fajar A. Nugraha Cc: Xen User-List Subject: Re: [Xen-users] xen 4.1 missing memory Hey, I set the dom0 min men to 512m in xend-config.sxp and ballooning is already enabled. I rebooted and it initially shows 512m but one the vms are booted it drops to 256 . Any other thoughts? Thanks On 17 Aug 2011, at 10:44, "Fajar A. Nugraha" <list@fajar.net> wrote:> On Wed, Aug 17, 2011 at 2:35 PM, Ian Tobin <itobin@tidyhosts.com> wrote: >> Hi, >> >> >> >> We have the dom0_mem=512M parameter set on boot which does show up >> after booting however ive noticed that it drops to roughly 256M on >> one of the boxes after the VMs are all started which is causing slow >> downs as it needs to swap. > > IIRC that is expected behaviour, no matter what version the kernel is. > >> The kernel is 2.6.32.43, has anyone else seen this?> > dom0_mem only sets dom0''s initial memory. If domU needs more memory, > dom0 can still baloon down. See dom0-min-mem and > enable-dom0-ballooning on /etc/xen/xend-config.sxp to change this > behavior. > > -- > Fajar > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users To report this as spam, please forward to spam@websense.com. Thank you. --- Scanned by ESG 7.6 --- Protected by Websense Hosted Email Security -- www.websense.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Aug 18, 2011 at 1:02 PM, Ian Tobin <itobin@tidyhosts.com> wrote:> Hey, > > I set the dom0 min men to 512m in xend-config.sxp and ballooning is already enabled. I rebooted and it initially shows 512m but one the vms are booted it drops to 256 . > > Any other thoughts?DISABLE ballooning? -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Sure, some bits changed for privacy reasons xm root@myhost:~# xl info host : myhost.domain.com release : 2.6.32.43 version : #6 SMP Tue Jul 26 13:43:40 BST 2011 machine : x86_64 nr_cpus : 4 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 2800 hw_caps : 178bf3ff:efd3fbff:00000000:00001310:00802001:00000000:000037ff:00000000 virt_caps : hvm total_memory : 7935 free_memory : 1195 free_cpus : 0 xen_major : 4 xen_minor : 1 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 xen_commandline : placeholder dom0_mem=512M cc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1) cc_compile_by : root cc_compile_domain : domain.com cc_compile_date : Tue Jul 26 10:42:19 BST 2011 xend_config_format : 4 root@myhost:~# root@myhost:~# xl list Name ID Mem VCPUs State Time(s) Domain-0 0 294 4 r----- 1287.3 Domu1 1 1019 2 -b---- 89.4 Domu2 2 251 2 -b---- 226.4 Domu3 3 763 4 -b---- 266.0 Domu4 4 507 2 -b---- 80.4 Domu5 5 1019 2 -b---- 65.1 Domu6 6 113 1 -b---- 4.3 Domu7 7 507 2 -b---- 96.0 Domu8 8 49 1 -b---- 4.0 Domu9 9 1019 4 -b---- 190.0 Domu10 10 1019 2 -b---- 28.1 root@myhost:~# thanks -----Original Message----- From: Yi, Shunli [mailto:syi@websense.com] Sent: 18 August 2011 07:08 To: Ian Tobin; Fajar A. Nugraha Cc: Xen User-List Subject: RE: [Xen-users] xen 4.1 missing memory Try to paste the output of "xm info" and "xm list". -Shunli -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Ian Tobin Sent: Thursday, August 18, 2011 2:03 PM To: Fajar A. Nugraha Cc: Xen User-List Subject: Re: [Xen-users] xen 4.1 missing memory Hey, I set the dom0 min men to 512m in xend-config.sxp and ballooning is already enabled. I rebooted and it initially shows 512m but one the vms are booted it drops to 256 . Any other thoughts? Thanks On 17 Aug 2011, at 10:44, "Fajar A. Nugraha" <list@fajar.net> wrote:> On Wed, Aug 17, 2011 at 2:35 PM, Ian Tobin <itobin@tidyhosts.com>wrote:>> Hi, >> >> >> >> We have the dom0_mem=512M parameter set on boot which does show up >> after booting however ive noticed that it drops to roughly 256M on >> one of the boxes after the VMs are all started which is causing slow >> downs as it needs to swap. > > IIRC that is expected behaviour, no matter what version the kernel is. > >> The kernel is 2.6.32.43, has anyone else seen this?> > dom0_mem only sets dom0''s initial memory. If domU needs more memory, > dom0 can still baloon down. See dom0-min-mem and > enable-dom0-ballooning on /etc/xen/xend-config.sxp to change this > behavior. > > -- > Fajar > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users To report this as spam, please forward to spam@websense.com. Thank you. --- Scanned by ESG 7.6 --- Protected by Websense Hosted Email Security -- www.websense.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Seems there is still enough memory. So, suggest to disable the balloon driver, and have a try. In /etc/xen/xend-config.sxp: # Dom0 will balloon out when needed to free memory for domU. # dom0-min-mem is the lowest memory level (in MB) dom0 will get down to. # If dom0-min-mem=0, dom0 will never balloon out. (dom0-min-mem 256) Try set (dom0-min-mem 0) to disable the balloon function. Temporarily, set the Domain0 memory by "xm set-mem 0 512" if you don''t want a Domain0 reboot. -Shunli -----Original Message----- From: Ian Tobin [mailto:itobin@tidyhosts.com] Sent: Thursday, August 18, 2011 3:01 PM To: Yi, Shunli; Fajar A. Nugraha Cc: Xen User-List Subject: RE: [Xen-users] xen 4.1 missing memory Sure, some bits changed for privacy reasons xm root@myhost:~# xl info host : myhost.domain.com release : 2.6.32.43 version : #6 SMP Tue Jul 26 13:43:40 BST 2011 machine : x86_64 nr_cpus : 4 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 2800 hw_caps : 178bf3ff:efd3fbff:00000000:00001310:00802001:00000000:000037ff:00000000 virt_caps : hvm total_memory : 7935 free_memory : 1195 free_cpus : 0 xen_major : 4 xen_minor : 1 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 xen_commandline : placeholder dom0_mem=512Mcc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1) cc_compile_by : root cc_compile_domain : domain.com cc_compile_date : Tue Jul 26 10:42:19 BST 2011 xend_config_format : 4 root@myhost:~# root@myhost:~# xl list Name ID Mem VCPUs State Time(s) Domain-0 0 294 4 r----- 1287.3 Domu1 1 1019 2 -b---- 89.4 Domu2 2 251 2 -b---- 226.4 Domu3 3 763 4 -b---- 266.0 Domu4 4 507 2 -b---- 80.4 Domu5 5 1019 2 -b---- 65.1 Domu6 6 113 1 -b---- 4.3 Domu7 7 507 2 -b---- 96.0 Domu8 8 49 1 -b---- 4.0 Domu9 9 1019 4 -b---- 190.0 Domu10 10 1019 2 -b---- 28.1 root@myhost:~# thanks -----Original Message----- From: Yi, Shunli [mailto:syi@websense.com] Sent: 18 August 2011 07:08 To: Ian Tobin; Fajar A. Nugraha Cc: Xen User-List Subject: RE: [Xen-users] xen 4.1 missing memory Try to paste the output of "xm info" and "xm list". -Shunli -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Ian Tobin Sent: Thursday, August 18, 2011 2:03 PM To: Fajar A. Nugraha Cc: Xen User-List Subject: Re: [Xen-users] xen 4.1 missing memory Hey, I set the dom0 min men to 512m in xend-config.sxp and ballooning is already enabled. I rebooted and it initially shows 512m but one the vms are booted it drops to 256 . Any other thoughts? Thanks On 17 Aug 2011, at 10:44, "Fajar A. Nugraha" <list@fajar.net> wrote:> On Wed, Aug 17, 2011 at 2:35 PM, Ian Tobin <itobin@tidyhosts.com>wrote:>> Hi, >> >> >> >> We have the dom0_mem=512M parameter set on boot which does show up >> after booting however ive noticed that it drops to roughly 256M on >> one of the boxes after the VMs are all started which is causing slow >> downs as it needs to swap. > > IIRC that is expected behaviour, no matter what version the kernel is. > >> The kernel is 2.6.32.43, has anyone else seen this?> > dom0_mem only sets dom0''s initial memory. If domU needs more memory, > dom0 can still baloon down. See dom0-min-mem and > enable-dom0-ballooning on /etc/xen/xend-config.sxp to change this > behavior. > > -- > Fajar > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users To report this as spam, please forward to spam@websense.com. Thank you. --- Scanned by ESG 7.6 --- Protected by Websense Hosted Email Security -- www.websense.com --- Scanned by ESG 7.6 --- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
My config is a little different, here is what is currently set:- # dom0-min-mem is the lowest permissible memory level (in MB) for dom0. # This is a minimum both for auto-ballooning (as enabled by # enable-dom0-ballooning below) and for xm mem-set when applied to dom0. (dom0-min-mem 512) # Whether to enable auto-ballooning of dom0 to allow domUs to be created. # If enable-dom0-ballooning = no, dom0 will never balloon out. (enable-dom0-ballooning no) Output of top Cpu(s): 1.9%us, 5.8%sy, 0.0%ni, 91.5%id, 0.0%wa, 0.0%hi, 0.1%si, 0.7%st Mem: 302000k total, 260088k used, 41912k free, 1020k buffers Swap: 1501944k total, 41700k used, 1460244k free, 17460k cached thanks -----Original Message----- From: Yi, Shunli [mailto:syi@websense.com] Sent: 18 August 2011 08:14 To: Ian Tobin; Fajar A. Nugraha Cc: Xen User-List Subject: RE: [Xen-users] xen 4.1 missing memory Seems there is still enough memory. So, suggest to disable the balloon driver, and have a try. In /etc/xen/xend-config.sxp: # Dom0 will balloon out when needed to free memory for domU. # dom0-min-mem is the lowest memory level (in MB) dom0 will get down to. # If dom0-min-mem=0, dom0 will never balloon out. (dom0-min-mem 256) Try set (dom0-min-mem 0) to disable the balloon function. Temporarily, set the Domain0 memory by "xm set-mem 0 512" if you don''t want a Domain0 reboot. -Shunli -----Original Message----- From: Ian Tobin [mailto:itobin@tidyhosts.com] Sent: Thursday, August 18, 2011 3:01 PM To: Yi, Shunli; Fajar A. Nugraha Cc: Xen User-List Subject: RE: [Xen-users] xen 4.1 missing memory Sure, some bits changed for privacy reasons xm root@myhost:~# xl info host : myhost.domain.com release : 2.6.32.43 version : #6 SMP Tue Jul 26 13:43:40 BST 2011 machine : x86_64 nr_cpus : 4 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 2800 hw_caps : 178bf3ff:efd3fbff:00000000:00001310:00802001:00000000:000037ff:00000000 virt_caps : hvm total_memory : 7935 free_memory : 1195 free_cpus : 0 xen_major : 4 xen_minor : 1 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 xen_commandline : placeholder dom0_mem=512Mcc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1) cc_compile_by : root cc_compile_domain : domain.com cc_compile_date : Tue Jul 26 10:42:19 BST 2011 xend_config_format : 4 root@myhost:~# root@myhost:~# xl list Name ID Mem VCPUs State Time(s) Domain-0 0 294 4 r----- 1287.3 Domu1 1 1019 2 -b---- 89.4 Domu2 2 251 2 -b---- 226.4 Domu3 3 763 4 -b---- 266.0 Domu4 4 507 2 -b---- 80.4 Domu5 5 1019 2 -b---- 65.1 Domu6 6 113 1 -b---- 4.3 Domu7 7 507 2 -b---- 96.0 Domu8 8 49 1 -b---- 4.0 Domu9 9 1019 4 -b---- 190.0 Domu10 10 1019 2 -b---- 28.1 root@myhost:~# thanks -----Original Message----- From: Yi, Shunli [mailto:syi@websense.com] Sent: 18 August 2011 07:08 To: Ian Tobin; Fajar A. Nugraha Cc: Xen User-List Subject: RE: [Xen-users] xen 4.1 missing memory Try to paste the output of "xm info" and "xm list". -Shunli -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Ian Tobin Sent: Thursday, August 18, 2011 2:03 PM To: Fajar A. Nugraha Cc: Xen User-List Subject: Re: [Xen-users] xen 4.1 missing memory Hey, I set the dom0 min men to 512m in xend-config.sxp and ballooning is already enabled. I rebooted and it initially shows 512m but one the vms are booted it drops to 256 . Any other thoughts? Thanks On 17 Aug 2011, at 10:44, "Fajar A. Nugraha" <list@fajar.net> wrote:> On Wed, Aug 17, 2011 at 2:35 PM, Ian Tobin <itobin@tidyhosts.com>wrote:>> Hi, >> >> >> >> We have the dom0_mem=512M parameter set on boot which does show up >> after booting however ive noticed that it drops to roughly 256M on >> one of the boxes after the VMs are all started which is causing slow >> downs as it needs to swap. > > IIRC that is expected behaviour, no matter what version the kernel is. > >> The kernel is 2.6.32.43, has anyone else seen this?> > dom0_mem only sets dom0''s initial memory. If domU needs more memory, > dom0 can still baloon down. See dom0-min-mem and > enable-dom0-ballooning on /etc/xen/xend-config.sxp to change this > behavior. > > -- > Fajar > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users To report this as spam, please forward to spam@websense.com. Thank you. --- Scanned by ESG 7.6 --- Protected by Websense Hosted Email Security -- www.websense.com --- Scanned by ESG 7.6 --- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, I will try and do this over the weekend. It looks to me like another bug and the configs are just getting ignored. So far I have DomUs do not shutdown when shutting down the server, they just terminate. DomUs do not auto startup when powering on server VNC has to be set in DomU config to except from 0.0.0.0 even though it is set in xend-config.sxp And now memory usage is being eaten All the above are set in /etc/rc"*.d scripts and in /etc/xen/auto Xen 4.1 on debian 6 is very buggy at the minute but 4.0.1 on debian 5 worked like a charm. Thanks Ian -----Original Message----- From: Yi, Shunli [mailto:syi@websense.com] Sent: 18 August 2011 09:52 To: Ian Tobin Subject: RE: [Xen-users] xen 4.1 missing memory Yes, your config is right for Xen-4.1.1. I have no idea yet. Here is a suggestion for trouble-shooting. 1. Do not start the xendomains service automatically,( by "chkconfig xendomains off") 2. restart your box, and check the memory of Domain0. ( no domainU has been started at that time ) 3. start the domainUs by manually, one by one. To check the memory changes after every DomU starting. By the way, please do check the kernel parameters didn''t limit the memory size in grub.conf. -Shunli -----Original Message----- From: Ian Tobin [mailto:itobin@tidyhosts.com] Sent: Thursday, August 18, 2011 3:30 PM To: Yi, Shunli; Fajar A. Nugraha Cc: Xen User-List Subject: RE: [Xen-users] xen 4.1 missing memory My config is a little different, here is what is currently set:- # dom0-min-mem is the lowest permissible memory level (in MB) for dom0. # This is a minimum both for auto-ballooning (as enabled by # enable-dom0-ballooning below) and for xm mem-set when applied to dom0. (dom0-min-mem 512) # Whether to enable auto-ballooning of dom0 to allow domUs to be created. # If enable-dom0-ballooning = no, dom0 will never balloon out. (enable-dom0-ballooning no) Output of top Cpu(s): 1.9%us, 5.8%sy, 0.0%ni, 91.5%id, 0.0%wa, 0.0%hi, 0.1%si, 0.7%st Mem: 302000k total, 260088k used, 41912k free, 1020k buffers Swap: 1501944k total, 41700k used, 1460244k free, 17460k cached thanks -----Original Message----- From: Yi, Shunli [mailto:syi@websense.com] Sent: 18 August 2011 08:14 To: Ian Tobin; Fajar A. Nugraha Cc: Xen User-List Subject: RE: [Xen-users] xen 4.1 missing memory Seems there is still enough memory. So, suggest to disable the balloon driver, and have a try. In /etc/xen/xend-config.sxp: # Dom0 will balloon out when needed to free memory for domU. # dom0-min-mem is the lowest memory level (in MB) dom0 will get down to. # If dom0-min-mem=0, dom0 will never balloon out. (dom0-min-mem 256) Try set (dom0-min-mem 0) to disable the balloon function. Temporarily, set the Domain0 memory by "xm set-mem 0 512" if you don''t want a Domain0 reboot. -Shunli -----Original Message----- From: Ian Tobin [mailto:itobin@tidyhosts.com] Sent: Thursday, August 18, 2011 3:01 PM To: Yi, Shunli; Fajar A. Nugraha Cc: Xen User-List Subject: RE: [Xen-users] xen 4.1 missing memory Sure, some bits changed for privacy reasons xm root@myhost:~# xl info host : myhost.domain.com release : 2.6.32.43 version : #6 SMP Tue Jul 26 13:43:40 BST 2011 machine : x86_64 nr_cpus : 4 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 2800 hw_caps : 178bf3ff:efd3fbff:00000000:00001310:00802001:00000000:000037ff:00000000 virt_caps : hvm total_memory : 7935 free_memory : 1195 free_cpus : 0 xen_major : 4 xen_minor : 1 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 xen_commandline : placeholder dom0_mem=512Mcc_compiler : gcc version 4.3.2 (Debian 4.3.2-1.1) cc_compile_by : root cc_compile_domain : domain.com cc_compile_date : Tue Jul 26 10:42:19 BST 2011 xend_config_format : 4 root@myhost:~# root@myhost:~# xl list Name ID Mem VCPUs State Time(s) Domain-0 0 294 4 r----- 1287.3 Domu1 1 1019 2 -b---- 89.4 Domu2 2 251 2 -b---- 226.4 Domu3 3 763 4 -b---- 266.0 Domu4 4 507 2 -b---- 80.4 Domu5 5 1019 2 -b---- 65.1 Domu6 6 113 1 -b---- 4.3 Domu7 7 507 2 -b---- 96.0 Domu8 8 49 1 -b---- 4.0 Domu9 9 1019 4 -b---- 190.0 Domu10 10 1019 2 -b---- 28.1 root@myhost:~# thanks -----Original Message----- From: Yi, Shunli [mailto:syi@websense.com] Sent: 18 August 2011 07:08 To: Ian Tobin; Fajar A. Nugraha Cc: Xen User-List Subject: RE: [Xen-users] xen 4.1 missing memory Try to paste the output of "xm info" and "xm list". -Shunli -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Ian Tobin Sent: Thursday, August 18, 2011 2:03 PM To: Fajar A. Nugraha Cc: Xen User-List Subject: Re: [Xen-users] xen 4.1 missing memory Hey, I set the dom0 min men to 512m in xend-config.sxp and ballooning is already enabled. I rebooted and it initially shows 512m but one the vms are booted it drops to 256 . Any other thoughts? Thanks On 17 Aug 2011, at 10:44, "Fajar A. Nugraha" <list@fajar.net> wrote:> On Wed, Aug 17, 2011 at 2:35 PM, Ian Tobin <itobin@tidyhosts.com>wrote:>> Hi, >> >> >> >> We have the dom0_mem=512M parameter set on boot which does show up >> after booting however ive noticed that it drops to roughly 256M on >> one of the boxes after the VMs are all started which is causing slow >> downs as it needs to swap. > > IIRC that is expected behaviour, no matter what version the kernel is. > >> The kernel is 2.6.32.43, has anyone else seen this?> > dom0_mem only sets dom0''s initial memory. If domU needs more memory, > dom0 can still baloon down. See dom0-min-mem and > enable-dom0-ballooning on /etc/xen/xend-config.sxp to change this > behavior. > > -- > Fajar > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users To report this as spam, please forward to spam@websense.com. Thank you. --- Scanned by ESG 7.6 --- Protected by Websense Hosted Email Security -- www.websense.com --- Scanned by ESG 7.6 --- --- Scanned by ESG 7.6 --- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello Fajar, I know this is an old thread, but I have a similar question and unlike the guys who were ignoring your advice, I actually did everything I believe to be necessary to control the usage of RAM memory by dom0 -- and I still see memory missing (precisely 279MB on four PowerEdge R710 servers running "2 x E5620" with 24GB each). This is my scenario: 0. I''m running Xen 3.4.3 (from GITCO repo''s) and different kernel releases, but all same version: 2.6.18 (from CentOS: kernel-xen-2.6.18-194.32.1.el5 , kernel-xen-2.6.18-238.9.1.el5 and kernel-xen-2.6.18-274.3.1.el5); 1. I have dom0_mem=512M on my boot parameters; 2. I have xend-config.xsp configured with: (dom0-min-mem 512) AND (enable-dom0-ballooning no); 3. There are 4 different boxes and they all are missing precisely 279MB immediately after boot, regardless of any VM running or not (besides Dom0, of course); Here are some examples: [root@hypervisor01]# xm list ; xm info | grep mem Name ID Mem VCPUs State Time(s) Domain-0 0 512 16 r----- 1955257.4 Domain-1 10 23500 16 r----- 11442974.1 total_memory : 24563 free_memory : 272 node_to_memory : node0:272 [root@hypervisor01~]# echo ''512+23500+272'' | bc ### adding Dom0 + Dom1 + "free_memory" should give me the same number as "total_memory" 24284 [root@hypervisor01~]# echo ''24563-24284'' | bc ### however it doesn''t, I''m missing 279MB 279 And here, a hypervisor with no VMs running at all, just after a reboot: [root@hypervisor02 ~]# xm list ; xm info | grep mem Name ID Mem VCPUs State Time(s) Domain-0 0 512 16 r----- 1195310.3 total_memory : 24563 free_memory : 23772 node_to_memory : node0:23772 [root@hypervisor02 ~]# echo ''512+23772'' | bc ### Again, adding Dom0 "free_memory" should give me the same number as "total_memory" 24284 [root@hypervisor02 ~]# echo ''24563-24284'' | bc ### And again, I''m missing 279MB 279 Is there any explanation as to where those 279MB are going to? To be honest, it doesn''t bother me that much that I have just a bit more than 1% of "total_memory" simply "disappearing", but the lack of an explanation does take my sleep. Any thoughts? Kind regards, Eduardo Bragatto On Thu, Aug 18, 2011 at 3:34 AM, Fajar A. Nugraha <list@fajar.net> wrote:> On Thu, Aug 18, 2011 at 1:02 PM, Ian Tobin <itobin@tidyhosts.com> wrote: > > Hey, > > > > I set the dom0 min men to 512m in xend-config.sxp and ballooning is > already enabled. I rebooted and it initially shows 512m but one the vms > are booted it drops to 256 . > > > > Any other thoughts? > > DISABLE ballooning? > > -- > Fajar > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users