Re: [libvirt] ZFS backend does fail if used on non top level pools

2018-05-11 Thread Brian Candler
> This one is the "unknown" for me.  What happens if you create > Xzfs/images/vol1 (or your command below) without first creating Xzfs/images? Answer: it fails, unless you give the '-p' flag.    -p    Creates all the non-existing parent datasets. Datasets created in this 

Re: [libvirt] ZFS backend does fail if used on non top level pools

2018-05-04 Thread John Ferlan
On 05/02/2018 03:36 AM, Christian Ehrhardt wrote: > Hi, > by discussing on bug [1] we found an issue in the ZFS storage backend. > When one defines a zfs pool through XML (virsh pool-create --build) a > top level ZFS pool will be created and works fine. The virsh > pool-define-as counterpart to t

Re: [libvirt] ZFS backend does fail if used on non top level pools

2018-05-03 Thread Daniel P . Berrangé
On Wed, May 02, 2018 at 09:36:10AM +0200, Christian Ehrhardt wrote: > Hi, > by discussing on bug [1] we found an issue in the ZFS storage backend. > When one defines a zfs pool through XML (virsh pool-create --build) a top > level ZFS pool will be created and works fine. The virsh pool-define-as >

[libvirt] ZFS backend does fail if used on non top level pools

2018-05-02 Thread Christian Ehrhardt
Hi, by discussing on bug [1] we found an issue in the ZFS storage backend. When one defines a zfs pool through XML (virsh pool-create --build) a top level ZFS pool will be created and works fine. The virsh pool-define-as counterpart to this is: $ fallocate -l 100M /tmp/Mzfs $ sudo zpool create Mzf