* "xl list --long" bug with only 1 CPU pool @ 2014-09-11 21:48 Olivier Bonvalet 2014-09-12 8:35 ` Wei Liu 0 siblings, 1 reply; 7+ messages in thread From: Olivier Bonvalet @ 2014-09-11 21:48 UTC (permalink / raw) To: xen-devel; +Cc: xen-users@lists.xen.org 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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: "xl list --long" bug with only 1 CPU pool 2014-09-11 21:48 "xl list --long" bug with only 1 CPU pool Olivier Bonvalet @ 2014-09-12 8:35 ` Wei Liu 2014-09-12 9:11 ` Wei Liu 0 siblings, 1 reply; 7+ messages in thread From: Wei Liu @ 2014-09-12 8:35 UTC (permalink / raw) To: Olivier Bonvalet; +Cc: xen-users@lists.xen.org, wei.liu2, xen-devel 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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: "xl list --long" bug with only 1 CPU pool 2014-09-12 8:35 ` Wei Liu @ 2014-09-12 9:11 ` Wei Liu 2014-09-12 9:29 ` Ian Campbell 0 siblings, 1 reply; 7+ messages in thread From: Wei Liu @ 2014-09-12 9:11 UTC (permalink / raw) To: Olivier Bonvalet; +Cc: xen-users@lists.xen.org, wei.liu2, xen-devel On Fri, Sep 12, 2014 at 09:35:22AM +0100, Wei Liu wrote: [...] > 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. > Actually no. In the end we still need a way to transform a pool name a pool id. Without a daemon keeping track of the change it's not likely to be fixed in the future. Does this ever work with xend? What's the last version of Xen you see it working? So in short, do change the pool name after you've created VMs in it. ;-) Wei. > Wei. > > > Thanks for your work, > > Olivier > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xen.org > > http://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: "xl list --long" bug with only 1 CPU pool 2014-09-12 9:11 ` Wei Liu @ 2014-09-12 9:29 ` Ian Campbell 2014-09-12 9:31 ` Wei Liu 0 siblings, 1 reply; 7+ messages in thread From: Ian Campbell @ 2014-09-12 9:29 UTC (permalink / raw) To: Wei Liu; +Cc: Olivier Bonvalet, xen-users@lists.xen.org, xen-devel On Fri, 2014-09-12 at 10:11 +0100, Wei Liu wrote: > On Fri, Sep 12, 2014 at 09:35:22AM +0100, Wei Liu wrote: > [...] > > 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. > > > > Actually no. In the end we still need a way to transform a pool name a > pool id. Without a daemon keeping track of the change it's not likely to > be fixed in the future. I thought the pool name was stored in xenstore, in which case it should be updated when the pol is renamed, shouldn't it? Ian. ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: "xl list --long" bug with only 1 CPU pool 2014-09-12 9:29 ` Ian Campbell @ 2014-09-12 9:31 ` Wei Liu 2014-09-12 9:50 ` Ian Campbell 0 siblings, 1 reply; 7+ messages in thread From: Wei Liu @ 2014-09-12 9:31 UTC (permalink / raw) To: Ian Campbell Cc: Olivier Bonvalet, xen-users@lists.xen.org, Wei Liu, xen-devel On Fri, Sep 12, 2014 at 10:29:09AM +0100, Ian Campbell wrote: > On Fri, 2014-09-12 at 10:11 +0100, Wei Liu wrote: > > On Fri, Sep 12, 2014 at 09:35:22AM +0100, Wei Liu wrote: > > [...] > > > 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. > > > > > > > Actually no. In the end we still need a way to transform a pool name a > > pool id. Without a daemon keeping track of the change it's not likely to > > be fixed in the future. > > I thought the pool name was stored in xenstore, in which case it should > be updated when the pol is renamed, shouldn't it? > The culprit is that pool name stored in guest config is not updated... Wei. > Ian. ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: "xl list --long" bug with only 1 CPU pool 2014-09-12 9:31 ` Wei Liu @ 2014-09-12 9:50 ` Ian Campbell 2014-09-12 9:59 ` Wei Liu 0 siblings, 1 reply; 7+ messages in thread From: Ian Campbell @ 2014-09-12 9:50 UTC (permalink / raw) To: Wei Liu; +Cc: Olivier Bonvalet, xen-users@lists.xen.org, xen-devel On Fri, 2014-09-12 at 10:31 +0100, Wei Liu wrote: > On Fri, Sep 12, 2014 at 10:29:09AM +0100, Ian Campbell wrote: > > On Fri, 2014-09-12 at 10:11 +0100, Wei Liu wrote: > > > On Fri, Sep 12, 2014 at 09:35:22AM +0100, Wei Liu wrote: > > > [...] > > > > 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. > > > > > > > > > > Actually no. In the end we still need a way to transform a pool name a > > > pool id. Without a daemon keeping track of the change it's not likely to > > > be fixed in the future. > > > > I thought the pool name was stored in xenstore, in which case it should > > be updated when the pol is renamed, shouldn't it? > > > > The culprit is that pool name stored in guest config is not updated... Oh right. That's a tricky one to resolve. In theory we could arrange to store the pool-id in the stashed config (e.g. after your json stuff), but then that probably doesn't work with migration (since poolname->poolid is per host, I think?). Iterating over all saved configs updating their pool-name doesn't sounds very nice either. Ian. ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: "xl list --long" bug with only 1 CPU pool 2014-09-12 9:50 ` Ian Campbell @ 2014-09-12 9:59 ` Wei Liu 0 siblings, 0 replies; 7+ messages in thread From: Wei Liu @ 2014-09-12 9:59 UTC (permalink / raw) To: Ian Campbell Cc: Olivier Bonvalet, xen-users@lists.xen.org, Wei Liu, xen-devel On Fri, Sep 12, 2014 at 10:50:18AM +0100, Ian Campbell wrote: > On Fri, 2014-09-12 at 10:31 +0100, Wei Liu wrote: > > On Fri, Sep 12, 2014 at 10:29:09AM +0100, Ian Campbell wrote: > > > On Fri, 2014-09-12 at 10:11 +0100, Wei Liu wrote: > > > > On Fri, Sep 12, 2014 at 09:35:22AM +0100, Wei Liu wrote: > > > > [...] > > > > > 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. > > > > > > > > > > > > > Actually no. In the end we still need a way to transform a pool name a > > > > pool id. Without a daemon keeping track of the change it's not likely to > > > > be fixed in the future. > > > > > > I thought the pool name was stored in xenstore, in which case it should > > > be updated when the pol is renamed, shouldn't it? > > > > > > > The culprit is that pool name stored in guest config is not updated... > > Oh right. That's a tricky one to resolve. > > In theory we could arrange to store the pool-id in the stashed config > (e.g. after your json stuff), but then that probably doesn't work with > migration (since poolname->poolid is per host, I think?). > The remote host will still use pool name to identify what pool to use. > Iterating over all saved configs updating their pool-name doesn't sounds > very nice either. > This is my thought as well. I'm now trying to figure out if this is a functional regression or something never worked (hence the question to ask about "last working version"). If that's a functional regression and users are very eager to get it fixed, we can figure out a way to fix it or workaround it. Wei. > Ian. ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2014-09-12 9:59 UTC | newest] Thread overview: 7+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2014-09-11 21:48 "xl list --long" bug with only 1 CPU pool Olivier Bonvalet 2014-09-12 8:35 ` 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
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).