All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans-Christian Armingeon <johnny@wh-netz.de>
To: xen-devel@lists.xensource.com
Subject: xm info showing too much free ram
Date: Thu, 30 Mar 2006 20:43:06 +0200	[thread overview]
Message-ID: <200603302043.06923.johnny@wh-netz.de> (raw)

Hi,

My dom0 has 2g ram allocated, and I have 2.5 G Ram physically in my machine.
I needed more Ram in domU so I did a

# xm mem-set 0 1000

# xm list
Name                              ID Mem(MiB) VCPUs State  Time(s)
Domain-0                           0     1000     1 r-----   471.8
gentoo64-xen                       2      453     1 ------ 29318.7

Looks Ok.

Increasing the Ram of domU

# xm mem-set 2 1453

root@jam:~# xm list
Name                              ID Mem(MiB) VCPUs State  Time(s)
Domain-0                           0     1000     1 r-----   472.5
gentoo64-xen                       2     1453     1 ------ 29336.7

Lokks OK.

Look at the line where it says:
free_memory            : 1064

root@jam:~# xm info
host                   : jam
release                : 2.6.16-20060326.1-xen0
version                : #1 SMP Sun Mar 26 21:41:31 CEST 2006
machine                : x86_64
nr_cpus                : 1
nr_nodes               : 1
sockets_per_node       : 1
cores_per_socket       : 1
threads_per_core       : 1
cpu_mhz                : 2200
hw_caps                : 078bfbff:e3d3fbff:00000000:00000010:00000001:00000001:00000001
total_memory           : 2559
free_memory            : 1064
xen_major              : 3
xen_minor              : 0
xen_extra              : -unstable
xen_caps               : xen-3.0-x86_64
platform_params        : virt_start=0xffff800000000000
xen_changeset          : Fri Mar 24 17:48:03 2006 +0100 9435:11fee62328cc
cc_compiler            : gcc-Version 4.0.2 20050808 (prerelease) (Ubuntu 4.0.1-4ubuntu9)
cc_compile_by          : root
cc_compile_domain      : localdomain
cc_compile_date        : Fr Mär 24 23:14:02 CET 2006
root@jam:~# xm info
host                   : jam
release                : 2.6.16-20060326.1-xen0
version                : #1 SMP Sun Mar 26 21:41:31 CEST 2006
machine                : x86_64
nr_cpus                : 1
nr_nodes               : 1
sockets_per_node       : 1
cores_per_socket       : 1
threads_per_core       : 1
cpu_mhz                : 2200
hw_caps                : 078bfbff:e3d3fbff:00000000:00000010:00000001:00000001:00000001
total_memory           : 2559
free_memory            : 1064
xen_major              : 3
xen_minor              : 0
xen_extra              : -unstable
xen_caps               : xen-3.0-x86_64
platform_params        : virt_start=0xffff800000000000
xen_changeset          : Fri Mar 24 17:48:03 2006 +0100 9435:11fee62328cc
cc_compiler            : gcc-Version 4.0.2 20050808 (prerelease) (Ubuntu 4.0.1-4ubuntu9)
cc_compile_by          : root
cc_compile_domain      : localdomain
cc_compile_date        : Fr Mär 24 23:14:02 CET 2006

Is that correct?

I don't think so.

Johnny

             reply	other threads:[~2006-03-30 18:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-30 18:43 Hans-Christian Armingeon [this message]
2006-04-03 16:45 ` xm info showing too much free ram Keir Fraser
2006-04-03 17:10   ` Ewan Mellor
2006-04-04 10:44     ` Hans-Christian Armingeon
2006-04-04 12:41       ` Keir Fraser

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=200603302043.06923.johnny@wh-netz.de \
    --to=johnny@wh-netz.de \
    --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.