From: Olivier Bonvalet <xen.list@daevel.fr>
To: xen-devel@lists.xen.org
Cc: "xen-users@lists.xen.org" <xen-users@lists.xen.org>
Subject: "xl list --long" bug with only 1 CPU pool
Date: Thu, 11 Sep 2014 23:48:23 +0200 [thread overview]
Message-ID: <1410472103.32481.1.camel@daevel.fr> (raw)
Hi,
on Xen 4.4, if you have only one CPU pool, "xl list --long" doesn't work
anymore, throwing error "Illegal pool specified" :
murmillia:~# xl cpupool-numa-split
murmillia:~#
murmillia:~# xl cpupool-list
Name CPUs Sched Active Domain count
Pool-node0 16 credit y 39
Pool-node1 16 credit y 0
murmillia:~#
murmillia:~# xl list --long | wc -l
8040
Here, it works fine.
Then I remove one cpupool :
murmillia:~#
murmillia:~# xl cpupool-destroy Pool-node1
murmillia:~#
murmillia:~# xl cpupool-list
Name CPUs Sched Active Domain count
Pool-node0 16 credit y 39
murmillia:~#
murmillia:~# xl list --long | wc -l
Illegal pool specified
0
Now, it doesn't work anymore.
Thanks for your work,
Olivier
next reply other threads:[~2014-09-11 21:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 21:48 Olivier Bonvalet [this message]
2014-09-12 8:35 ` "xl list --long" bug with only 1 CPU pool Wei Liu
2014-09-12 9:11 ` Wei Liu
2014-09-12 9:29 ` Ian Campbell
2014-09-12 9:31 ` Wei Liu
2014-09-12 9:50 ` Ian Campbell
2014-09-12 9:59 ` Wei Liu
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=1410472103.32481.1.camel@daevel.fr \
--to=xen.list@daevel.fr \
--cc=xen-devel@lists.xen.org \
--cc=xen-users@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).