Virtualbox stopped working on kernel 6.3.4 Fedora 38

[pepicheck]

more details in ​https://forums.virtualbox.org/viewtopic.php?f=7&t=109439

[galitsyn]

Hi pepicheck,

I do not see the issue you are observing on my end. Could you please try to get a core dump (https://www.virtualbox.org/wiki/Core_dump) and attach it here (specifying exact installation package name)? Please also attach VBox.log here.

[galitsyn]

Hi pepicheck,

The following line in VBoxSVC.log looks suspicious:

00:02:42.269417 Watcher  Reaper: Pid 10527 (0x291f) was signalled: SIGILL (4 / 0x4)

Could you please check in system logs (journalctl) if process was killed due to SE Linux policy?

[pepicheck]

Well, this one I killed by myself because it was hanging.

pidof VirtualBoxVM

10527

kill -4 10527

[pepicheck]

So the issue seems like with module vboxdrv and vboxnetflt, as after this, they cannot be even unloaded.

[ebp9fggl3jjy5oiyqcil]

Hello there,

I recently came across this bug on my system when I upgraded from kernel 6.2.x to kernel 6.3.4 in Fedora 38. After some searching, I discovered that the issue was related to changes regarding IBT (Indirect Branch Tracking) in kernel 6.3.4.

Here is the link: (​https://bodhi.fedoraproject.org/updates/FEDORA-2023-514965dd8a#comment-3044537)

I also found another bug report on VirtualBox's ticket system that mentions issues regarding IBT: (https://www.virtualbox.org/ticket/21435)

I hope this information is helpful and solves your problem!

[fth0]

@pepicheck: Start your host OS with "ibt=off" to work around the issue.

[pepicheck]

Great, that works. Now we just need to wait for Oracle developers to fix this.

[tekstryder]

This bug report appears to be a duplicate of the original IBT ticket:

https://www.virtualbox.org/ticket/21435