Unfortunately I currently don't have the possibility to run this kind of setup because my root is on zfs and I'm working on some other nasty issue.
In general the key to get QAT acceleration for zfs 0.7.12 working is to have the qat driver loaded and initialized before the zfs kernel modules.
I would expect that the dependency on qat_api shown by 'modinfo zfs' should in theory be sufficient to accomplish this. Only in the case of root on zfs the kernel doesn't have any other choice than to load the zfs kernel modules before the qat driver becomes available because there is no QAT support present in the initramfs.
However, maybe it helps to put a 'softdep' command into zfs.conf which specifies the qat driver as a 'pre' dependency.
What's the objective of the two 'blacklist' commands in yours ?
In general the key to get QAT acceleration for zfs 0.7.12 working is to have the qat driver loaded and initialized before the zfs kernel modules.
I would expect that the dependency on qat_api shown by 'modinfo zfs' should in theory be sufficient to accomplish this. Only in the case of root on zfs the kernel doesn't have any other choice than to load the zfs kernel modules before the qat driver becomes available because there is no QAT support present in the initramfs.
However, maybe it helps to put a 'softdep' command into zfs.conf which specifies the qat driver as a 'pre' dependency.
What's the objective of the two 'blacklist' commands in yours ?