no "kernel-devel" for fedora 26 (any kernel), can't update one of my boxes's netvm :( need help building kernel module for new fedora

[tonsimple]

Qubes OS version:

R 3.2

Affected component(s):

Fedora 26 templates (but this is continuation of an old and terrible issue)

---

Steps to reproduce the behavior:

Try finding a way to build a kernel module for VMs that use Fedora 26 based templates

Expected behavior:

Kernel-devel package present for most recent VM kernel, install it and do a build, use the resulting module to get wireless dongle going

Actual behavior:

no kernel-devel for fedora 26, means the netvm on one of my Qubes boxes will have to stay on fedora 25 (and kernel 4.4.31-11 because that's the latest kernel-devel supported on F25 :( )

General notes:

There seems to be a long going, persistent issue with kernel-devel being available for qubes VMs.

It is... disconcerting.

Is there a way to get a kernel module build for Fedora 26 and recent kernel version that does not rely on kernel-devel (maybe debian, because frankly I'd rather use a debian-based VM) ?

if not, is kernel-devel going to be provided?

I am very unhappy with having a F25, old kernel VM running as sys-net but so far I have no other choice.

---

Related issues:

There seems to be a "thing" with kernel-devel. :(
#3158

[mtalexan]

#2844 Talks about this issue extensively.
The summary of that thread is that the TemplateVMs fedora-* and debian-* are based on the kernel from dom0 by default, but that's a very old kernel and most of the development tools won't match or be available for building on modern fedora and debian distributions. There's no good solution to this. Instead you're better off creating a clone of the templateVM you need the kernel-devel package in, switching it to use the modern kernel provided by the distribution (e.g. Fedora-26's kernel package), and then using this new "unsafe" VM wherever you might need kernel modules that aren't provided as part of Qubes.
Directions for doing this are available here: https://www.qubes-os.org/doc/managing-vm-kernel/#using-kernel-installed-in-the-vm
Briefly, the instructions say that you need to set the new copy of the template VM to be an HVM, you need to clear the kernel version selection to be '', and then you should install the standard packages within the TemplateVM.

[mtalexan]

#2844 Talks about this issue extensively.
The summary of that thread is that the TemplateVMs fedora-* and debian-* are based on the kernel from dom0 by default, but that's a very old kernel and most of the development tools won't match or be available for building on modern fedora and debian distributions. There's no good solution to this. Instead you're better off creating a clone of the templateVM you need the kernel-devel package in, switching it to use the modern kernel provided by the distribution (e.g. Fedora-26's kernel package), and then using this new "unsafe" VM wherever you might need kernel modules that aren't provided as part of Qubes.
Directions for doing this are available here: https://www.qubes-os.org/doc/managing-vm-kernel/#using-kernel-installed-in-the-vm
Briefly, the instructions say that you need to set the new copy of the template VM to be an HVM, you need to clear the kernel version selection to be '', and then you should install the standard packages within the TemplateVM.