Closed pugege closed 5 years ago
No. I've tried setting vm prefs kernel
to '' (empty) to make it boot the template's kernel -- this is supposed to resolve the version conflicts. But with that setting the vms no longer start.
May need to open a Qubes issue.
Following wireguard wiki but failing on step 5. I have /lib/modules, but there is no extra directory with which to contain a wireguard.ko Ran qvm-prefs sys-wireguard kernel It returned the kernel used by the template, 4.14.35-1 Qubes 4, Fedora 28 minimal template.
I didn't have time to try the instructions with the Qubes default kernel. But it appears to at least boot and build under these conditions:
Then install wireguard packages and configure.
Updated with HVM instructions.
Wireguard via Mullvad is not functional with the current R4.0 kernel (also apparmor). Have tried the new wireguard update using the current wiki unsuccessfully. Have you been able run the program with the new kernel? Is there a bug attaching modules to 4.14.13-3? Using debian-9 template for vpn and fedora-26 for the .ko file.