Re: [libvirt-users] error: internal error: missing backend for pool type 11 (zfs)
On Tue, Oct 03, 2017 at 08:44:10 +0200, Michal Privoznik wrote:
On 10/02/2017 11:42 PM, Nick Gilmour wrote:
[...]
2) storage backends are static. While we have libvirt drivers in
separate modules (.so files) and load them at start up, it's not the
same story with storage driver backends. These are hardcoded into the
storage driver. Might be worth it to have them dynamically loadable too.
This was changed some time ago. Backends are loadable now:
src/.libs/libvirt_storage_backend_disk.so
src/.libs/libvirt_storage_backend_fs.so
src/.libs/libvirt_storage_backend_gluster.so
src/.libs/libvirt_storage_backend_iscsi.so
src/.libs/libvirt_storage_backend_logical.so
src/.libs/libvirt_storage_backend_mpath.so
src/.libs/libvirt_storage_backend_rbd.so
src/.libs/libvirt_storage_backend_scsi.so
src/.libs/libvirt_storage_backend_sheepdog.so
src/.libs/libvirt_storage_backend_vstorage.so
src/.libs/libvirt_storage_backend_zfs.so
Similarly to driver backends they are loaded at start of libvirtd.
Attachments:
- signature.asc (application/pgp-signature — 833 bytes)