Opened 6 months ago

Closed 4 months ago

#21698 closed defect (duplicate)

Virtualbox stopped working on kernel 6.3.4 Fedora 38

Reported by: pepicheck Owned by:
Component: other Version: VirtualBox-7.0.8
Keywords: Cc:
Guest type: all Host type: Linux


Attachments (2)

VBoxSVC.log (10.3 KB ) - added by pepicheck 6 months ago.
VBox.log (2.1 KB ) - added by pepicheck 6 months ago.

Download all attachments as: .zip

Change History (11)

comment:1 by galitsyn, 6 months ago

Hi pepicheck,

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

Last edited 6 months ago by galitsyn (previous) (diff)

by pepicheck, 6 months ago

Attachment: VBoxSVC.log added

by pepicheck, 6 months ago

Attachment: VBox.log added

comment:2 by galitsyn, 6 months ago

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?

comment:3 by pepicheck, 6 months ago

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

pidof VirtualBoxVM


kill -4 10527

comment:4 by pepicheck, 6 months ago

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

in reply to:  description comment:5 by ebp9fggl3jjy5oiyqcil, 6 months ago

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: (

I also found another bug report on VirtualBox's ticket system that mentions issues regarding IBT: (

I hope this information is helpful and solves your problem!

comment:6 by fth0, 6 months ago

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

comment:7 by pepicheck, 6 months ago

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

comment:8 by tekstryder, 6 months ago

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

comment:9 by galitsyn, 4 months ago

Resolution: duplicate
Status: newclosed
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use