An odd thought from me … I use “Apparmor”.
So, @THN … do you use SELinux or Apparmor?
( I can’t imagine that has an influence on VBox )
@myswtest
As @Sauerland commented, you probably had VirtualBox installed when you were on kernel 43, and now it’s being carried forward to the newer kernels by means of backlinking.
My case is different: I want to newly install VirtualBox while being already on kernel 47. If you would uninstall VirtualBox now, I bet you wouldn’t be able to bring it back.
How can I know?
I think, Leap 16.1 betas has some problems, I can not rebuild virtualbox-kmp-default from src.rpm because of missing acpica…
So, as @malcolmlewis pointed ou, maybe qemu/kvm is the alternative.
PS
My Leap16.1 is running inside a qem/kvm virtualazation.
One way is as I show in my previous reply:
# more /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-6.12.0-160099.47-default root=UUID=xxxxx... mitigations=auto security=apparmor
#
See where it shows “security=…”
The ksym Problem is a kernel problem.
The new kernel has other symbols as the kmp needs.
Has nothing to do with selinux or apparmor.
There are problems with Leap 16.1, see my last post.
1 Like
You know WHY? Because 16.1 is Beta. Why would a 3rd party vendor fight with supporting a Linux distro that is in Alpha / Beta??
Anyway, keep reading … you will see I did install the 16.0 version of the latest Oracle-specific VBox on my 16.1. 
rwong 
I did un-install the openSUSE VBox, then installed it afresh. No issue(s).
Then guess what? I downloaded the most current Oracle-specific VBox (yea, it’s dedicated for 16.0) from their web and installed it … which also added the Oracle VBox repo. It installed with absolutely ZERO errors.
So, as usual, I’ll run the VBox directly from Oracle
.
Removal of VBox from openSUSE-dedicated:
# zypper rm virtualbox virtualbox-kmp-default virtualbox-qt virtualbox-qt libQt6Help6 libQt6StateMachine6
Reading installed packages...
Resolving package dependencies...
The following 5 packages are going to be REMOVED:
libQt6Help6 libQt6StateMachine6 virtualbox virtualbox-kmp-default virtualbox-qt
5 packages to remove.
Package install size change:
| 0 B required by packages that will be installed
-138.3 MiB | - 138.3 MiB released by packages that will be removed
Backend: classic_rpmtrans
Continue? [y/n/v/...? shows all options] (y): y
(1/5) Removing: virtualbox-qt-7.2.6-lp161.1.14.x86_64 .....[done]
(2/5) Removing: virtualbox-7.2.6-lp161.1.14.x86_64 ......[done]
(3/5) Removing: virtualbox-kmp-default-7.2.6_k6.12.0_160099.43-lp161.1.6.x86_64 .[done]
(4/5) Removing: libQt6StateMachine6-6.11.0-160099.1.3.x86_64 .........[done]
(5/5) Removing: libQt6Help6-6.11.0-160099.1.1.x86_64 ......[done]
Running post-transaction scripts .....[done]
#
.
Okay, so after downloading RPM from Oracle … let’s install it :
# zypper in VirtualBox-7.2-7.2.14_174565_openSUSE160-1.x86_64.rpm
'VirtualBox-7.2-7.2.14_174565_openSUSE160-1.x86_64.rpm' looks like an RPM file. Will try to use it.
Refreshing service 'openSUSE'.
Looking for gpg keys in repository virtualbox-oracle.
gpgkey=http://download.virtualbox.org/virtualbox/rpm/opensuse/16.0/x86_64/repodata/repomd.xml.key
Retrieving repository 'virtualbox-oracle' metadata ...[done]
Building repository 'virtualbox-oracle' cache ...[done]
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following 3 NEW packages are going to be installed:
libQt6Help6 libQt6StateMachine6 VirtualBox-7.2
3 new packages to install.
[...]
Checking for file conflicts: .. .[done]
(1/3) Installing: libQt6Help6-6.11.0-160099.1.1.x86_64 ...[done]
(2/3) Installing: libQt6StateMachine6-6.11.0-160099.1.3.x86_64..[done]
(3/3) Installing: VirtualBox-7.2-7.2.14_174565_openSUSE160-1.x86_64 ......[done]
Running post-transaction scripts ..[done]
#
.
