> I don't know when we'll get to supporting ZFS properly. But we'll get to it eventually.
To clarify, ZFS and virtual block devices support are two separate things.
While full ZFS support is desirable, supporting virtual block devices (*independently of ZFS*) is enough for ZFS users to perform an installation.
I've just tested an Ubuntu Server 18.04.3 installation on a virtual block device and everything works fine. The only thing that needed to be changed in Subiquity, besides making it show the required virtual device, was to correctly add the `p` suffix for `zd` devices:
```
patch -p1 "lib/python3.6/site-packages/curtin/block/__init__.py" << 'DIFF'
116c116
< for dev_type in ['bcache', 'nvme', 'mmcblk', 'cciss', 'mpath', 'md']:
---
> for dev_type in ['bcache', 'nvme', 'mmcblk', 'cciss', 'mpath', 'md', 'zd']:
DIFF
```
> I don't know when we'll get to supporting ZFS properly. But we'll get to it eventually.
To clarify, ZFS and virtual block devices support are two separate things.
While full ZFS support is desirable, supporting virtual block devices (*independently of ZFS*) is enough for ZFS users to perform an installation.
I've just tested an Ubuntu Server 18.04.3 installation on a virtual block device and everything works fine. The only thing that needed to be changed in Subiquity, besides making it show the required virtual device, was to correctly add the `p` suffix for `zd` devices:
``` 6/site- packages/ curtin/ block/_ _init__ .py" << 'DIFF'
patch -p1 "lib/python3.
116c116
< for dev_type in ['bcache', 'nvme', 'mmcblk', 'cciss', 'mpath', 'md']:
---
> for dev_type in ['bcache', 'nvme', 'mmcblk', 'cciss', 'mpath', 'md', 'zd']:
DIFF
```
That was all :-)