search for: free_memory

Hello, I have some dom0 which have 8GB RAM, but when I look with xm list, it just shows me 6GB, I need to setup some new VM, each with 1GB, so I should have with 3VM still 5GB free, but im only seeing 3GB. Can I just create 2 new VM with each 1GB and still have 3GB for the dom0? #xm top xentop - 11:31:17 Xen 3.1.0-53.1.14.el5 4 domains: 1 running, 3 blocked, 0 paused, 0 crashed, 0 dying, 0

You need to add dom0_mem=XXXm to xen or scale back the memory of domain0 with using "xm mem-set <DomId> <Mem>" command. Your domain0 used up almost all physical mem. >total_memory : 1023 >free_memory : 62 Thanks Yunfeng >-----Original Message----- >From: xen-devel-bounces@lists.xensource.com >[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Ed Smith >Sent: 2006年4月28日 4:56 >To: xen-devel@lists.xensource.com >Subject: [Xen-devel] Problem booting fully vi...

...: x86_64 nr_cpus : 4 nr_nodes : 1 sockets_per_node : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 2400 hw_caps : bfebfbff:20100800:00000000:00000940:0000e3bd:00000000:00000001 total_memory : 4095 free_memory : 383 node_to_cpu : node0:0-3 xen_major : 3 xen_minor : 1 xen_extra : .2-238.9.1.el5 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_pagesize : 4096 platform_params...

...UTC 2009 machine : x86_64 nr_cpus : 4 nr_nodes : 1 cores_per_socket : 2 threads_per_core : 1 cpu_mhz : 1995 hw_caps : bfebfbff:20100800:00000000:00000140:0004e33d:00000000:00000001 total_memory : 24570 free_memory : 918 node_to_cpu : node0:0-3 xen_major : 3 xen_minor : 2 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...

...om0 and i do a free -m i get that the system only has 432 under the total section. booting into the stock debian kernel 2.6.26-2-amd64 kernel gives me 8192 free memory for i did not limit that. when i run xm info |grep memory under the xen kernel I get the following. total_memory : 8191 free_memory : 7578 node_to_memory : node0:7578 the server only has 8gb of memory installed which is confirmed via the system bios. is there anyway to figure out what is going on here? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.c...

...: x86_64 nr_cpus : 4 nr_nodes : 1 cores_per_socket : 2 threads_per_core : 2 cpu_mhz : 1666 hw_caps : bfebfbff:20100800:00000000:00000940:0040e31d:00000000:00000001:00000000 virt_caps : total_memory : 4079 free_memory : 581 node_to_cpu : node0:0-3 node_to_memory : node0:581 node_to_dma32_mem : node0:581 max_node_id : 0 xen_major : 4 xen_minor : 0 xen_extra : .1-rc5 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p xen_sche...

...pus : 16 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 2 cpu_mhz : 2400 hw_caps : bfebfbff:28100800:00000000:00000340:009ce3bd:00000000:00000001:00000000 virt_caps : hvm total_memory : 24567 free_memory : 22240 node_to_cpu : node0:0-15 node_to_memory : node0:22240 xen_major : 3 xen_minor : 4 xen_extra : .2 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...

...pus : 16 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 2 cpu_mhz : 2400 hw_caps : bfebfbff:28100800:00000000:00000340:009ce3bd:00000000:00000001:00000000 virt_caps : hvm total_memory : 24567 free_memory : 22240 node_to_cpu : node0:0-15 node_to_memory : node0:22240 xen_major : 3 xen_minor : 4 xen_extra : .2 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...

...quot;, info.cores_per_socket, - "sockets_per_node", info.sockets_per_node, - "nr_nodes", info.nr_nodes, - "total_memory", pages_to_kib(info.total_pages), - "free_memory", pages_to_kib(info.free_pages), - "scrub_memory", pages_to_kib(info.scrub_pages), - "cpu_khz", info.cpu_khz, - "hw_caps", cpu_cap); + ret_obj = Py_BuildValue(&qu...

...: 2 > cores_per_socket : 6 > threads_per_core : 1 > cpu_mhz : 3325 > hw_caps : > bfebfbff:2c100800:00000000:00003f40:029ee3ff:00000000:00000001:00000000 > virt_caps : hvm > total_memory : 98291 > free_memory : 62390 > sharing_freed_memory : 0 > sharing_used_memory : 0 > free_cpus : 0 > xen_major : 4 > xen_minor : 2 > xen_extra : .2 > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > hvm-3...

Hi Ian (and all), I recently came across a bug in xl autoballooning in Xen 4.2.2 that I found mentioned way back in May 2012. In a nutshell, I tried to create a new DomU with 1024M of memory. The Dom0 had 3100M free: # xl info | grep memory total_memory : 20479 free_memory : 3100 The guest template is very simple: # cat /etc/xen/template.vm name = "template.vm" memory = 1024 vcpus = 1 cpus = "1-7" disk = [ ''phy:/dev/vg_hosting/template.vm,xvda,w'' ] vif =...

...64 nr_cpus : 16 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 2 cpu_mhz : 2261 hw_caps : bfebfbff:28100800:00000000:00000340:009ce3bd:00000000:00000001:00000000 virt_caps : hvm total_memory : 32758 free_memory : 3974 node_to_cpu : node0:0-15 node_to_memory : node0:3974 xen_major : 3 xen_minor : 4 xen_extra : .2 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 :...

...86_64 nr_cpus : 4 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 2133 hw_caps : bfebfbff:28100800:00000000:00003b40:009ce3bd:00000000:00000001:00000000 virt_caps : hvm total_memory : 2037 free_memory : 988 free_cpus : 0 xen_major : 4 xen_minor : 2 xen_extra : .2-23.el6 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 pl...

...: x86_64 nr_cpus : 2 nr_nodes : 1 cores_per_socket : 1 threads_per_core : 2 cpu_mhz : 2800 hw_caps : bfebfbff:20000800:00000000:00000180:0000641d:00000000:00000000:00000000 virt_caps : total_memory : 6143 free_memory : 2054 node_to_cpu : node0:0-1 node_to_memory : node0:2054 node_to_dma32_mem : node0:1807 max_node_id : 0 xen_major : 4 xen_minor : 0 xen_extra : .1-rc3 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p xen_...

...: 8 max_cpu_id : 7 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 2 cpu_mhz : 3392 hw_caps : bfebfbff:28100800:00000000:00007f40:77bae3ff:00000000:00000001:00000281 virt_caps : hvm total_memory : 3970 free_memory : 442 sharing_freed_memory : 0 sharing_used_memory : 0 free_cpus : 0 cpu_topology : cpu: core socket node 0: 0 0 0 1: 0 0 0 2: 1 0 0 3: 1 0 0 4: 2...

...39;m doing wrong? I have xen-4.1.1-3 installed from http://xenbits.xen.org/people/mayoung/EL6.xen on my centos6 server. I am running 2.6.32-131.12.1.el6.xendom0.x86_64 kernel available from the same place. 'xl info' reports about available memory as follows: total_memory : 24567 free_memory : 3698 xen_commandline : dom0_mem=2048M and in xend-config.sxp I have: (dom0-min-mem 256) (enable-dom0-ballooning no) (total_available_memory 0) Now one would think that I should have 2048M memory for dom0, right? I started from there, but when starting domUs it has been reduce...

...: i686 nr_cpus : 1 nr_nodes : 1 sockets_per_node : 1 cores_per_socket : 1 threads_per_core : 1 cpu_mhz : 2793 hw_caps : bfebfbff:20000000:00000000:00000180:0000e43d:00000000:00000001 total_memory : 1023 free_memory : 62 xen_major : 3 xen_minor : 0 xen_extra : -unstable xen_caps : xen-3.0-x86_32 hvm-3.0-x86_32 platform_params : virt_start=0xfc000000 xen_changeset : Tue Apr 25 18:22:11 2006 +0100 9744:1ad06bd6832d cc_compiler...

...07 machine : x86_64 nr_cpus : 4 nr_nodes : 1 sockets_per_node : 2 cores_per_socket : 1 threads_per_core : 2 cpu_mhz : 2992 hw_caps : bfebfbff:20100800:00000000:00000180:0000641d total_memory : 4095 free_memory : 3246 xen_major : 3 xen_minor : 1 xen_extra : .0-53.1.4.el5 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable cc_compile...