Re: "xl list --long" bug with only 1 CPU pool

[Wei Liu <wei.liu2@citrix.com>]

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.