From: "Vadim A. Misbakh-Soloviov" <mva@mva.name>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Problem with growing up dom0 memory
Date: Sat, 27 Oct 2012 18:44:03 +0700 [thread overview]
Message-ID: <508BC903.8050104@mva.name> (raw)
In-Reply-To: <508BC02B.5040607@mva.name>
[-- Attachment #1.1: Type: text/plain, Size: 2696 bytes --]
Sorry, I forgot to tell:
Xen/Xen-tools version: 4.2.0
Kernel: 3.5.3 on the first node, and 3.6.3 on second (where I get
cpupool issue)
Also,
xl infos:
1)
node1 ~mva % xl info
host : node1
release : 3.5.3
version : #3 SMP PREEMPT Fri Sep 7 16:12:20 MSK 2012
machine : x86_64
nr_cpus : 12
nr_nodes : 1
cores_per_socket : 6
threads_per_core : 2
cpu_mhz : 3475
hw_caps :
bfebfbff:2c100800:00000000:00003f40:029ae3bf:00000000:00000001:00000000
virt_caps : hvm hvm_directio
total_memory : 24567
free_memory : 0
free_cpus : 0
xen_major : 4
xen_minor : 1
xen_extra : .3
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 : dom0_max_vcpus=8 dom0_vcpus_pin dom0_max_mem=24G
cc_compiler : gcc version 4.5.4 (Gentoo 4.5.4 p1.0, pie-0.4.7)
cc_compile_by :
cc_compile_domain :
cc_compile_date : Sun Sep 2 05:07:49 MSK 2012
xend_config_format : 4
2)
node1 ~mva % xl info
host : node1
release : 3.6.3
version : #1 SMP Fri Oct 26 05:58:21 MSK 2012
machine : x86_64
nr_cpus : 12
max_cpu_id : 15
nr_nodes : 1
cores_per_socket : 6
threads_per_core : 2
cpu_mhz : 3200
hw_caps :
bfebfbff:2c100800:00000000:00002f40:17bee3bf:00000000:00000001:00000000
virt_caps : hvm hvm_directio
total_memory : 64948
free_memory : 100
sharing_freed_memory : 0
sharing_used_memory : 0
free_cpus : 0
xen_major : 4
xen_minor : 2
xen_extra : .0
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 : dom0_max_vcpus=12 dom0_max_mem=64G
cc_compiler : x86_64-pc-linux-gnu-gcc (Gentoo 4.5.4 p1.0,
pie-0.4.7) 4.5.4
cc_compile_by :
cc_compile_domain : (none)
cc_compile_date : Wed Oct 24 20:45:01 MSK 2012
xend_config_format : 4
(yes, both nodes has hostname "node1" :P)
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 897 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-10-27 11:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-27 11:06 Problem with growing up dom0 memory Vadim A. Misbakh-Soloviov
2012-10-27 11:44 ` Vadim A. Misbakh-Soloviov [this message]
2012-10-27 11:59 ` Vadim A. Misbakh-Soloviov
2012-12-19 22:01 ` Konrad Rzeszutek Wilk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=508BC903.8050104@mva.name \
--to=mva@mva.name \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).