From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: "Xen-Devel (xen-devel@lists.xensource.com)"
<xen-devel@lists.xensource.com>
Subject: xl list vs xm list: backwards compatibility vs forward progress?
Date: Tue, 27 Jul 2010 13:43:32 -0700 (PDT) [thread overview]
Message-ID: <6eeab433-fd6e-4fc5-bdfe-c2d56a9a6c37@default> (raw)
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".
Does this matter? Probably not, but I've heard there
are tools that screen-scrape output from the core
xen tools... and I wonder if the other xend interface
(xapi?) gets one rather the other (or maybe both).
Just thought it should be noted, especially if
(IIRC) there are plans to symlink /usr/bin/xm
to /usr/bin/xl.
Dan
next reply other threads:[~2010-07-27 20:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 20:43 Dan Magenheimer [this message]
2010-07-28 13:55 ` xl list vs xm list: backwards compatibility vs forward progress? Ian Jackson
2010-07-28 15:07 ` Dan Magenheimer
2010-07-29 15:29 ` Stefano Stabellini
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=6eeab433-fd6e-4fc5-bdfe-c2d56a9a6c37@default \
--to=dan.magenheimer@oracle.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).