[ISSUE] VirtualBox DKMS modules don't load on Linux 6.5

[ISSUE] VirtualBox DKMS modules don't load on Linux 6.5

[too-vague]

[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]

New issue by too-vague on void-packages repository

https://github.com/void-linux/void-packages/issues/46912

Description:
### Is this a new report?

Yes

### System Info

Void 6.5.9_1 x86_64 AuthenticAMD uptodate FF

### Package(s) Affected

virtualbox-ose-dkms-7.0.10_4, linux6.5-6.5.9_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

Compile and load Virtualbox DKMS modules (vboxdrv, vboxnetadp, vboxnetflt), as seen in linux6.4 and below

### Actual behaviour

DKMS modules compile properly but fail to load both during boot and manually

modprobe:
```
modprobe: ERROR: could not insert 'vboxdrv': Key was rejected by service
modprobe: ERROR: could not insert 'vboxnetadp': Key was rejected by service
modprobe: ERROR: could not insert 'vboxnetflt': Key was rejected by service
```

dmesg:
```
[ 1168.956122] Loading of module with unavailable key is rejected
[ 1168.961298] Loading of module with unavailable key is rejected
[ 1168.966354] Loading of module with unavailable key is rejected
```

### Steps to reproduce

1. Install linux6.5 and virtualbox-ose
2. Run virtualbox on new kernel

Re: VirtualBox DKMS modules don't load on Linux 6.5

[nezos]

[-- Attachment #1: Type: text/plain, Size: 460 bytes --]

New comment by nezos on void-packages repository

https://github.com/void-linux/void-packages/issues/46912#issuecomment-1782897666

Comment:
For me:

Building DKMS module: virtualbox-ose-guest-7.0.10... FAILED!

for kernel 6.5.8

According to the recent changelog (https://www.virtualbox.org/wiki/Changelog):

Since version 7.0.12...
"Linux Guest Additions: Added initial support for kernels 6.5 and 6.6" 

An update would probably solve the issue.

Re: VirtualBox DKMS modules don't load on Linux 6.5

[nezos]

[-- Attachment #1: Type: text/plain, Size: 480 bytes --]

New comment by nezos on void-packages repository

https://github.com/void-linux/void-packages/issues/46912#issuecomment-1782897666

Comment:
For me:

Building DKMS module: virtualbox-ose-guest-7.0.10... FAILED!

for kernel 6.5.8

According to the recent changelog (https://www.virtualbox.org/wiki/Changelog):

Since version 7.0.12...
"Linux Guest Additions: Added initial support for kernels 6.5 and 6.6" 

Updating virtualbox to 7.0.12 would probably solve the issue.

Re: [ISSUE] [CLOSED] VirtualBox DKMS modules don't load on Linux 6.5

[classabbyamp]

[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]

Closed issue by too-vague on void-packages repository

https://github.com/void-linux/void-packages/issues/46912

Description:
### Is this a new report?

Yes

### System Info

Void 6.5.9_1 x86_64 AuthenticAMD uptodate FF

### Package(s) Affected

virtualbox-ose-dkms-7.0.10_4, linux6.5-6.5.9_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

Compile and load Virtualbox DKMS modules (vboxdrv, vboxnetadp, vboxnetflt), as seen in linux6.4 and below

### Actual behaviour

DKMS modules compile properly but fail to load both during boot and manually

modprobe:
```
modprobe: ERROR: could not insert 'vboxdrv': Key was rejected by service
modprobe: ERROR: could not insert 'vboxnetadp': Key was rejected by service
modprobe: ERROR: could not insert 'vboxnetflt': Key was rejected by service
```

dmesg:
```
[ 1168.956122] Loading of module with unavailable key is rejected
[ 1168.961298] Loading of module with unavailable key is rejected
[ 1168.966354] Loading of module with unavailable key is rejected
```

### Steps to reproduce

1. Install linux6.5 and virtualbox-ose
2. Run virtualbox on new kernel

Re: VirtualBox DKMS modules don't load on Linux 6.5

[classabbyamp]

[-- Attachment #1: Type: text/plain, Size: 156 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/issues/46912#issuecomment-1807478669

Comment:
#47037