AES module not loading?

[JeGr]

Dev VM before upgrade to latest snapshot:

(QAT is "no" as it's a VM inside a proxmox host and QAT can't be passed through(?) yet(?) so that's normal to not showing up.)

VM still configured to use it:

but shows up as inactive:

Any special things that have to be triggered or considered for that?
Or is that simply because it has been "merged" into the kernel itself and is no longer a loadable kernel module?

kldload: can't load aesni: module already loaded or in kernel

Cheers
\jens

[jimp]

We're still working on that one. AES-NI is now in the kernel, and the output of pciconf changed so it isn't detecting loaded devices properly, so that's all a bit in flux. We haven't decided if we're keeping AES-NI in the kernel or moving it to a module, but either way the dashboard reporting is broken for the time being for everything.

[JeGr]

@jimp said in AES module not loading?:

We're still working on that one. AES-NI is now in the kernel, and the output of pciconf changed so it isn't detecting loaded devices properly, so that's all a bit in flux. We haven't decided if we're keeping AES-NI in the kernel or moving it to a module, but either way the dashboard reporting is broken for the time being for everything.

Alright, had a hunch it's that one :) Thanks to clarify just wanted to report it so it won't go unnoticed ;)