From: Alexander Bienzeisler <chosi@amd.co.at>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: can not use all available memory
Date: Fri, 23 Nov 2012 13:06:26 +0100 [thread overview]
Message-ID: <50AF66C2.6020402@amd.co.at> (raw)
In-Reply-To: <20121123115254.GU8912@reaktio.net>
I am currently using Xen 4.2.1-pre built from git source. Kernel version
3.1.1
xl info before:
host : susi-0
release : 3.1.1-xen
version : #1 SMP Fri Nov 18 10:16:22 CET 2011
machine : x86_64
nr_cpus : 24
max_cpu_id : 31
nr_nodes : 2
cores_per_socket : 6
threads_per_core : 2
cpu_mhz : 3325
hw_caps :
bfebfbff:2c100800:00000000:00003f40:029ee3ff:00000000:00000001:00000000
virt_caps : hvm hvm_directio
total_memory : 98291
free_memory : 28969
sharing_freed_memory : 0
sharing_used_memory : 0
free_cpus : 0
xen_major : 4
xen_minor : 2
xen_extra : .1-pre
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 : Wed Nov 14 11:46:07 2012 +0000 25922:8ca6372315f8
xen_commandline : placeholder loglvl=all dom0_mem=2048M
dom0_max_vcpus=2 dom0_vcpus_pin com2=115200 console=com2,vga
cc_compiler : gcc (Debian 4.4.5-8) 4.4.5
cc_compile_by : root
cc_compile_domain : wsk.tu-chemnitz.de
cc_compile_date : Thu Nov 22 13:50:09 CET 2012
xend_config_format : 4
xl list before:
Name ID Mem VCPUs State Time(s)
Domain-0 0 2048 2 r----- 3490.0
Squeeze 19 4091 2 -b---- 370.3
win2k8_2_susi6 31 16373 12 -b---- 1619.3
win2k8_susi5 33 32757 12 -b---- 1264.0
win7_susi3 43 4085 4 -b---- 416.0
scientific_susi7 44 8192 16 -b---- 39.9
domU config:
name = "centos_susi8"
uuid = "2e87b315-fd5a-dfbc-fe9d-6e121fdfa632"
maxmem = 16384
memory = 16384
vcpus = 16
builder = "generic"
bootloader = "pygrub"
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"
vfb = [ "type=vnc,vncunused=1,keymap=de" ]
disk = [ "phy:/dev/mapper/storage-SL5,xvda,w" ]
vif = [ "mac=00:50:56:37:61:17,bridge=xenbr0" ]
error message after:
xl create /root/configs/centos_susi8.cfg
Parsing config from /root/configs/centos_susi8.cfg
libxl: error: libxl.c:3433:libxl_set_memory_target: new target 0 for
dom0 is below the minimum threshold
with 8gigs:
xl info after:
host : susi-0
release : 3.1.1-xen
version : #1 SMP Fri Nov 18 10:16:22 CET 2011
machine : x86_64
nr_cpus : 24
max_cpu_id : 31
nr_nodes : 2
cores_per_socket : 6
threads_per_core : 2
cpu_mhz : 3325
hw_caps :
bfebfbff:2c100800:00000000:00003f40:029ee3ff:00000000:00000001:00000000
virt_caps : hvm hvm_directio
total_memory : 98291
free_memory : 20776
sharing_freed_memory : 0
sharing_used_memory : 0
free_cpus : 0
xen_major : 4
xen_minor : 2
xen_extra : .1-pre
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 : Wed Nov 14 11:46:07 2012 +0000 25922:8ca6372315f8
xen_commandline : placeholder loglvl=all dom0_mem=2048M
dom0_max_vcpus=2 dom0_vcpus_pin com2=115200 console=com2,vga
cc_compiler : gcc (Debian 4.4.5-8) 4.4.5
cc_compile_by : root
cc_compile_domain : wsk.tu-chemnitz.de
cc_compile_date : Thu Nov 22 13:50:09 CET 2012
xend_config_format : 4
xl list after:
Name ID Mem VCPUs State Time(s)
Domain-0 0 2048 2 r----- 3550.0
Squeeze 19 4091 2 -b---- 381.5
win2k8_2_susi6 31 16373 12 -b---- 1627.1
win2k8_susi5 33 32757 12 ------ 1269.0
win7_susi3 43 4085 4 -b---- 418.7
scientific_susi7 44 8192 16 -b---- 40.3
centos_susi8 46 8192 16 -b---- 4.4
Am 23.11.2012 12:52, schrieb Pasi Kärkkäinen:
> On Fri, Nov 23, 2012 at 12:35:26PM +0100, Alexander Bienzeisler wrote:
>> Hello,
>>
>> i just tried to add a domU with 16 gigs of ram (maxmem = 16384,
>> memory = 16384) with free_memory : 28969 but got an error:
>>
>> libxl: error: libxl.c:3433:libxl_set_memory_target: new target 0 for
>> dom0 is below the minimum threshold
>>
>> I was able to create it with 8 gigs of ram, ending up with
>> free_memory : 20776
>>
>> Is there something wrong with memory in 4.2? I can't seem to use all of it.
>>
> What exact Xen version are you using? what dom0 kernel version?
>
> Also please pastebin "xl info" and "xl list" before and after starting the VM.
>
> -- Pasi
>
next prev parent reply other threads:[~2012-11-23 12:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-23 11:35 can not use all available memory Alexander Bienzeisler
2012-11-23 11:52 ` Pasi Kärkkäinen
2012-11-23 12:06 ` Alexander Bienzeisler [this message]
2012-11-23 12:21 ` Ian Campbell
2012-11-23 12:28 ` Pasi Kärkkäinen
2012-11-23 12:33 ` Ian Campbell
2012-11-23 12:41 ` Pasi Kärkkäinen
2012-11-23 12:47 ` Ian Campbell
2012-11-23 12:55 ` Pasi Kärkkäinen
2012-11-23 13:15 ` Ian Campbell
2012-11-23 13:29 ` Pasi Kärkkäinen
2012-11-23 13:33 ` Ian Campbell
2012-11-26 16:58 ` Dan Magenheimer
2012-11-26 18:25 ` Sander Eikelenboom
2012-11-26 20:20 ` Dan Magenheimer
2012-11-26 20:24 ` Pasi Kärkkäinen
2012-11-26 20:37 ` Dan Magenheimer
2012-11-26 21:32 ` Tim Deegan
2012-11-26 21:47 ` Dan Magenheimer
2012-11-27 2:52 ` William Pitcock
2012-11-27 10:52 ` Ian Campbell
2012-11-26 20:35 ` Sander Eikelenboom
2012-11-23 12:46 ` Alexander Bienzeisler
-- strict thread matches above, loose matches on Subject: below --
2012-11-23 11:38 Alexander Bienzeisler
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=50AF66C2.6020402@amd.co.at \
--to=chosi@amd.co.at \
--cc=pasik@iki.fi \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.