Based on the error message while I tried to create a pool with ZFS the openmediavault-kvm package has been compiled without zfs support
https://libvirt-users.redhat.n…kend-for-pool-type-11-zfs
it is true ?
Code
Error creating pool: Could not define storage pool: internal error: missing backend for pool type 12 (zfs)
Traceback (most recent call last):
File "/usr/share/virt-manager/virtinst/storage.py", line 385, in install
pool = self.conn.storagePoolDefineXML(xml, 0)
File "/usr/lib/python3/dist-packages/libvirt.py", line 5007, in storagePoolDefineXML
if ret is None:raise libvirtError('virStoragePoolDefineXML() failed', conn=self)
libvirt.libvirtError: internal error: missing backend for pool type 12 (zfs)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/createpool.py", line 378, in _async_pool_create
poolobj = pool.install(create=True, meter=meter, build=build)
File "/usr/share/virt-manager/virtinst/storage.py", line 387, in install
raise RuntimeError(_("Could not define storage pool: %s") % str(e))
RuntimeError: Could not define storage pool: internal error: missing backend for pool type 12 (zfs)While I could mount the zfspool mountpoint as a file directory, I think it loose some ZFS superpower such as doing snapshot at ZFS level.
