xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Robert Urban <urban@unix-beratung.de>
Cc: Wei Liu <wei.liu2@citrix.com>, xen-devel@lists.xen.org
Subject: Re: JSON format of >xl list< does not provide state information
Date: Mon, 20 Feb 2017 17:30:55 +0000	[thread overview]
Message-ID: <20170220173055.4ryuaoftaai2756x@citrix.com> (raw)
In-Reply-To: <fc5580b5-d9c0-5288-3530-78cd92198945@unix-beratung.de>

On Fri, Feb 17, 2017 at 04:37:10AM +0100, Robert Urban wrote:
> Hello Folks,
> 
> Sorry, forgot to mention the version:
> 
> > # xl info
> > [...]
> > release                : 4.9.3-200.186.fc25.x86_64
> 

This is for Linux kernel, not Xen. To get Xen version:

  xl info | egrep  'major|minor|extra'

 
> plain "xl list" produces:
> 
> > # xl list
> > Name                                        ID   Mem VCPUs    State    Time(s)
> > Domain-0                                     0  2048     1     r-----     108.2
> 
> and "xl list -l" produces:
> 
> > # xl list -l
> > [
> >     {
> >         "domid": 0,
> >         "config": {
> >             "c_info": {
> >                 "type": "pv",
> >                 "name": "Domain-0"
> >             },
> >             "b_info": {
> >                 "max_memkb": 2097152,
> >                 "target_memkb": 2097151,
> >                 "sched_params": {
> >
> >                 },
> >                 "type.pv": {
> >
> >                 },
> >                 "arch_arm": {
> >
> >                 }
> >             }
> >         }
> >     }
> > ]
> 
> why doesn't "xl list -l" provide the "State" information that the plain "xl
> list" provides? I would have thought the JSON output would be complete.
> 

Because for reasons I don't know the long output format is actually
printing out the domain configuration.

It wouldn't be too difficult to add a new option to generate JSON output
according to short output, but unfortunately I don't have time to work
on this at the moment.

Wei.


> cheers,
> 
> Robert Urban
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-02-20 17:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-17  3:37 JSON format of >xl list< does not provide state information Robert Urban
2017-02-20 17:30 ` Wei Liu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-02-17  3:34 Robert Urban

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=20170220173055.4ryuaoftaai2756x@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=urban@unix-beratung.de \
    --cc=xen-devel@lists.xen.org \
    /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).