ERROR: could not insert 'zfs': Invalid argument ← This makes me highly-suspicious of a kABI mismatch in the DKMS-compiled kmods because it was built against kernel-devel and kernel-headers versions that aren’t close enough to the VM’s fedora-34 default kernel at /lib/modules/$(uname -r).
As a hackaround that didn’t make it to my notes (Murphy’s Law), I installed headers and devel in a VM from 5.11 that was close enough to 5.10 to “work.” I don’t trust that.
I’m open to suggestions, as detailed as possible, to making this to work reliably should kernels get swapped. Ultimately, I’m scripting the creation of this VM for cfg mgmt reasons. What I have so far is trivial from the Fedora install instructions above.
Mainly, I’d like to know: which repo and under what names are the headers for the fedora 32 qubes kernel RPMs? I’m guessing I’ll need to re-run dkms autoinstall ... with the the path to more appropriate kernel headers.
You could try to use the template kernel instead of the one provided by Qubes and dom0. I’m assuming that you are installing ZFS in the template. Approximate steps:
Clone the template to fedora-34-zfs.
Make sure grub2-xen-pvh is installed in dom0.
Set the kernel in fedora-34-zfs to pvgrub2-pvh. In dom0, run qvm-prefs fedora-34-zfs kernel pvgrub2-pvh
Now when you start fedora-34-zfs, it should use the kernel from the template, not from dom0.
Make sure the kernel in each VM that uses this template is also set to the same thing.
I don’t know potential security implications of this.