On 2012年06月23日 01:30, Dave Allan wrote: Actually not discarded, persistent conf is changed anyway, and the new conf is stored in pool->newDef too, but we don't have an option for pool-dump to dump the inactive pool XML, like "virsh dumpxml --inactive" for a domain. So one would always see the live pool conf, which is without the changes. IMHO it's expected, because if we support the live edit of the objects XML, that may cause much more problems. E.g. one see the live conf is changed, but actually one can't start the pool after destroying it, for the target path is not built yet, however, the pool is still active with the conf. The only problem is we need to support --inactive flag for pool-dumpxml from my p.o.v. Regards, Osier