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

RE: [Xen-devel] xl list vs xm list: backwards compatibility vs forward p

To: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Subject: RE: [Xen-devel] xl list vs xm list: backwards compatibility vs forward progress?
From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Date: Thu, 29 Jul 2010 16:29:34 +0100
Cc: "Xen-Devel \(xen-devel@xxxxxxxxxxxxxxxxxxx\)" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Delivery-date: Thu, 29 Jul 2010 08:29:39 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <47b78d88-2d7d-423e-9c07-c441a4eeb3a5@default>
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>
References: <6eeab433-fd6e-4fc5-bdfe-c2d56a9a6c37@default 19536.14036.365209.581219@xxxxxxxxxxxxxxxxxxxxxxxx> <47b78d88-2d7d-423e-9c07-c441a4eeb3a5@default>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Alpine 2.00 (DEB 1167 2008-08-23)
On Wed, 28 Jul 2010, Dan Magenheimer wrote:
> > From: Ian Jackson [mailto:Ian.Jackson@xxxxxxxxxxxxx]
> > Sent: Wednesday, July 28, 2010 7:56 AM
> > To: Dan Magenheimer
> > Cc: Xen-Devel (xen-devel@xxxxxxxxxxxxxxxxxxx)
> > Subject: Re: [Xen-devel] xl list vs xm list: backwards compatibility vs
> > forward progress?
> > 
> > Dan Magenheimer writes ("[Xen-devel] xl list vs xm list: backwards
> > compatibility vs forward progress?"):
> > > I was pleased to find out that "xl list" shows the
> > > current amount of physical memory in use by a domain
> > > rather than the start amount.  This is very useful
> > > for monitoring self-ballooning!  I like it!
> > >
> > > But... it is not backwards compatible with "xm list".
> > 
> > Isn't it ?
> > 
> > I'm pretty sure I've written a program which does "xm mem-set" and
> > then polls the output from "xm list" to wait for the target domain to
> > balloon down.
> 
> Hmmm... perhaps xm keeps track of xm mem-set commands... but a
> domain can do ballooning without involvement of the toolchain.
> Self-ballooning (see xen.hg/tools/xenballoon, in tree for about
> two years now) does that in-guest-userland and I have kernel rpms
> for EL5u5 and RHEL6b2 that do it in-guest-kernel.  (The latter
> will be the preferred guest deployment method for Xen systems
> running tmem to optimize memory utilization.)
> 
> With self-ballooning in a guest, xl list and xm list
> very definitely show different values for memory.
> 
> Dan
> 
> P.S. Frankly, I think the xm list behavior is a bug, but
> backwards compatibility -- plus my poor parseltongue --
> stopped me from trying to fix it.
> 

I agree, xm list should be the one to be fixed.

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

<Prev in Thread] Current Thread [Next in Thread>