All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vadim A. Misbakh-Soloviov" <mva@mva.name>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Problem with growing up dom0 memory
Date: Sat, 27 Oct 2012 18:06:19 +0700	[thread overview]
Message-ID: <508BC02B.5040607@mva.name> (raw)


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

             reply	other threads:[~2012-10-27 11:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-27 11:06 Vadim A. Misbakh-Soloviov [this message]
2012-10-27 11:44 ` Problem with growing up dom0 memory Vadim A. Misbakh-Soloviov
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=508BC02B.5040607@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 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.