From: Wei Liu <wei.liu2@citrix.com>
To: Olivier Bonvalet <xen.list@daevel.fr>
Cc: "xen-users@lists.xen.org" <xen-users@lists.xen.org>,
wei.liu2@citrix.com, xen-devel@lists.xen.org
Subject: Re: "xl list --long" bug with only 1 CPU pool
Date: Fri, 12 Sep 2014 09:35:22 +0100 [thread overview]
Message-ID: <20140912083522.GA31343@zion.uk.xensource.com> (raw)
In-Reply-To: <1410472103.32481.1.camel@daevel.fr>
On Thu, Sep 11, 2014 at 11:48:23PM +0200, Olivier Bonvalet wrote:
> 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.
>
I presume the pool name changed after the split and you once speficied a
pool name in your VM config file. If so:
This is a limitation of xl. You can rename the pool name to its original
name (presumably "Pool-0") and try again. I think this will be fixed in
4.5.
Wei.
> Thanks for your work,
> Olivier
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-09-12 8:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 21:48 "xl list --long" bug with only 1 CPU pool Olivier Bonvalet
2014-09-12 8:35 ` Wei Liu [this message]
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=20140912083522.GA31343@zion.uk.xensource.com \
--to=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=xen-users@lists.xen.org \
--cc=xen.list@daevel.fr \
/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).