WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Why does xc_domain_getinfolist() think 256 == 244?

To: Xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Why does xc_domain_getinfolist() think 256 == 244?
From: Tim Post <echo@xxxxxxxxxxxx>
Date: Wed, 13 May 2009 17:35:50 +0800
Cc:
Delivery-date: Wed, 13 May 2009 02:36:33 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Reply-to: echo@xxxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

I am using xc_domain_getinfolist() on x86_32 and have noticed something
rather odd.

If a dom-u is allocated 256 MB , xc.curmem thinks its 244.

We take curmem, and divide it by (1024 * 1024). Any other multiple of 1,
2, 4, 8 (and more) is accurate .. however if curmem == 256, we've lost
12 * (1024 * 1024).

To reproduce, start 3 mini-os guests with 256 MB of ram, use
xc_domain_getinfolist() and see what it says :) I'm working with the
current tip of xen-unstable.

Yet, xm list reports the memory accurately.

I'm puzzled.

Regards,
--Tim






_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Why does xc_domain_getinfolist() think 256 == 244?, Tim Post <=