All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: [PATCH] Fix xm list --long
Date: Sat, 13 Aug 2005 14:25:52 -0500	[thread overview]
Message-ID: <42FE4940.1050709@us.ibm.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 199 bytes --]

Currently xm list --long only displays info about the last domain.  The 
attached patch fixes this so it displays info about each domain.

Signed-off-by: Anthony Liguori

Regards,

Anthony Liguori



[-- Attachment #2: xend_xm_list_long.diff --]
[-- Type: text/x-patch, Size: 807 bytes --]

# HG changeset patch
# User Anthony Liguori <aliguori@us.ibm.com>
# Node ID a5e3caa6efbf3a46515c8b4f39219eaed75b2b6c
# Parent  73fccd848200b63230002b2d96df897ab232627a
Fix xm list --long to display info about all domains

diff -r 73fccd848200 -r a5e3caa6efbf tools/python/xen/xm/main.py
--- a/tools/python/xen/xm/main.py	Fri Aug 12 20:06:15 2005
+++ b/tools/python/xen/xm/main.py	Sat Aug 13 19:31:13 2005
@@ -224,8 +224,9 @@
         domsinfo.append(parse_doms_info(info))
                
     if use_long:
-        # this actually seems like a bad idea, as it just dumps sexp out
-        PrettyPrint.prettyprint(info)
+        for dom in doms:
+            info = server.xend_domain(dom)
+            PrettyPrint.prettyprint(info)
     elif show_vcpus:
         xm_show_vcpus(domsinfo)
     elif format:

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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

                 reply	other threads:[~2005-08-13 19:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=42FE4940.1050709@us.ibm.com \
    --to=aliguori@us.ibm.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 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.