Problem with growing up dom0 memory

Problem with growing up dom0 memory

[Vadim A. Misbakh-Soloviov]

[-- Attachment #1.1: Type: text/plain, Size: 1166 bytes --]

Hello there!
I know, that it is "not so good practice", but anyway when I try to grow
up dom0 memory with xm — I get following thing:

node1 mva % xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 14287 8 r----- 255128.8
node1 mva % xm mem-set Domain-0 24G
node1 mva % xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 13957 8 r----- 255131.4
node1 mva % xm mem-set Domain-0 24G
node1 mva % xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 13626 8 r----- 255138.9

And it shrinks more and more every time.

When I try to do it with xl — i get following:

node1 ~mva % xl mem-set Domain-0 24g
libxl: error: libxl.c:2125:libxl_set_memory_target cannot get memory
info from /local/domain/0/memory/static-max
: No such file or directory



And, by the way, on another node I also have following issue:
node1 ~mva % xl cpupool-list
libxl: error: libxl.c:596:cpupool_info: failed to get info for cpupool1
: No such file or directory
Name               CPUs   Sched     Active   Domain count
Pool-0              12    credit       y         13


And it is some more places where I get errors with xl.

--
Best regards,
mva


[-- 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

Re: Problem with growing up dom0 memory

[Vadim A. Misbakh-Soloviov]

[-- 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

Re: Problem with growing up dom0 memory

[Vadim A. Misbakh-Soloviov]

[-- Attachment #1.1: Type: text/plain, Size: 816 bytes --]

Uhm. It seems, it is 4.1.3 (as you can see from xl info) on 3.5.3-kernel
node, but I have all following issues even on 3.6.3-kernel node with 4.2.0.

P.S.:
By the way, I also has some network speed issues with domUs:

one_node ~mva % scp bkp.txz domU_on_another_node:/home/mva
bkp.txz

                                      3%  592KB 259.7KB/s   0.0KB/s
01:12 ETA^CKilled by signal 2.
one_node ~mva % scp bkp.txz another_node_itself:/home/mva
bkp.txz

                                    100%   19MB   3.8MB/s   6.2MB/s
00:05

almost the same for reversed process (downloading from that places)
it is rt8169 ethernet driver on "one_node", e1000e on "another_node" and
I dunno which driver Xen uses for domUs, but:
domU ~mva % dmesg|grep -i 'Xen.*eth'
Initialising Xen virtual ethernet driver


[-- 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

Re: Problem with growing up dom0 memory

[Konrad Rzeszutek Wilk]

On Sat, Oct 27, 2012 at 06:59:50PM +0700, Vadim A. Misbakh-Soloviov wrote:
> Uhm. It seems, it is 4.1.3 (as you can see from xl info) on 3.5.3-kernel
> node, but I have all following issues even on 3.6.3-kernel node with 4.2.0.

I believe that might be related to the autoballon functionality. Have
you tried disabling it.
> 
> P.S.:
> By the way, I also has some network speed issues with domUs:
> 
> one_node ~mva % scp bkp.txz domU_on_another_node:/home/mva
> bkp.txz
> 
>                                       3%  592KB 259.7KB/s   0.0KB/s
> 01:12 ETA^CKilled by signal 2.
> one_node ~mva % scp bkp.txz another_node_itself:/home/mva
> bkp.txz
> 
>                                     100%   19MB   3.8MB/s   6.2MB/s
> 00:05
> 
> almost the same for reversed process (downloading from that places)
> it is rt8169 ethernet driver on "one_node", e1000e on "another_node" and
> I dunno which driver Xen uses for domUs, but:
> domU ~mva % dmesg|grep -i 'Xen.*eth'
> Initialising Xen virtual ethernet driver

There is a Wiki that explains this( Google for Network Xen Wiki). I think you need to set an
TSO (or maybe it is another flag) off on the guest's adapter.