VirtualBox 7.2.4 [still] segfault in Fedora 43 on libQt6Widgets

Ask Fedora
, , ,
1

This issue seems to have been around, at least since Virtualbox 7.1 and libQt6 6.9. I started experiencing it at least since I upgraded to Fedora 43.

Here’s the details of what I’m running:

  • VirtualBox 7.2.4.r170995
  • Fedora 43, currently running kernel 6.17.7-300.fc43.x86_64
  • Cinnamon display manager (with X11, not Wayland, I think. $XDG_SESSION_TYPE contains “x11” & $WAYLAND_DISPLAY isn’t set)
  • Thinkpad P14s Gen 5 with AMD Ryzen 7 PRO 8840HS & 64GB RAM
  • External 4K monitor is primary, laptop lid is usually closed

I have two VMs running, one Mint Linux, one Windows. Both have 3D acceleration enabled with 256MB VM (issue persists with 3D disabled & 128MB VM).

AFAIK, I’ve fully disabled suspend by:

$ sudo systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target
$ cat /etc/systemd/sleep.conf.d/nosuspend.conf
[Sleep]
AllowSuspend=no
AllowHibernation=no
AllowSuspendThenHibernate=no
AllowHybridSleep=no
$ xset s off
$ xset -display :0.0 dpms 0 0 0

…though something is still trying to trigger it as “Requested suspend operation not supported, ignoring.” shows in the logs when I turn off the external monitor.

More times than not, when I turn off the monitor, VirtualBox & the two VMs and the main process crash with a segfault in libQt6Widgets.so.6.10.0:

Nov 16 08:15:49 myhostname systemd[1]: net-syn-docs.mount: Deactivated successfully.
Nov 16 08:15:49 myhostname systemd-logind[2189]: Requested suspend operation not supported, ignoring.
Nov 16 08:15:49 myhostname nfsrahead[1977542]: setting /net/nfs/mymount readahead to 128
Nov 16 08:15:49 myhostname systemd-logind[2189]: Requested suspend operation not supported, ignoring.
Nov 16 08:15:49 myhostname systemd-logind[2189]: Requested suspend operation not supported, ignoring.
Nov 16 08:16:25 myhostname systemd-logind[2189]: Requested suspend operation not supported, ignoring.
Nov 16 08:16:25 myhostname Deskflow[9056]: [2025-11-16T08:16:25] INFO: either XRRScreenChangeNotifyEvent or RRNotify_CrtcChange received
Nov 16 08:16:25 myhostname Deskflow[9056]: [2025-11-16T08:16:25] INFO: either XRRScreenChangeNotifyEvent or RRNotify_CrtcChange received
Nov 16 08:16:26 myhostname Deskflow[9056]: [2025-11-16T08:16:26] INFO: either XRRScreenChangeNotifyEvent or RRNotify_CrtcChange received
Nov 16 08:16:26 myhostname Deskflow[9056]: [2025-11-16T08:16:26] INFO: either XRRScreenChangeNotifyEvent or RRNotify_CrtcChange received
Nov 16 08:16:26 myhostname Deskflow[9056]: [2025-11-16T08:16:26] INFO: either XRRScreenChangeNotifyEvent or RRNotify_CrtcChange received
Nov 16 08:16:26 myhostname audit[296174]: ANOM_ABEND auid=501 uid=501 gid=501 ses=3 subj=kernel pid=296174 comm="VirtualBox" exe="/usr/lib/virtualbox/VirtualBox" sig=11 res=1
Nov 16 08:16:26 myhostname kernel: VirtualBox[296174]: segfault at 8 ip 00007f0569e8dd94 sp 00007fff8d875ab8 error 4 in libQt6Widgets.so.6.10.0[8dd94,7f0569e00000+50b000] likely on CPU 0 (core 0, socket 0)
Nov 16 08:16:26 myhostname audit[296287]: ANOM_ABEND auid=501 uid=501 gid=501 ses=3 subj=kernel pid=296287 comm="VirtualBoxVM" exe="/usr/lib/virtualbox/VirtualBoxVM" sig=11 res=1
Nov 16 08:16:26 myhostname kernel: Code: f9 ff 4c 8b 55 b8 4c 8b 45 b0 84 c0 75 c0 e9 76 ff ff ff e8 0e ee f8 ff 0f 1f 00 66 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa <48> 8b 4e 08 48 89 f8 f3 0f 6f 81 38 01 00 00 48 8b 89 48 01 00 00
Nov 16 08:16:26 myhostname kernel: VirtualBoxVM[296287]: segfault at 8 ip 00007f97f8e8dd94 sp 00007ffedd58fdc8 error 4 in libQt6Widgets.so.6.10.0[8dd94,7f97f8e00000+50b000] likely on CPU 7 (core 3, socket 0)
Nov 16 08:16:26 myhostname kernel: Code: f9 ff 4c 8b 55 b8 4c 8b 45 b0 84 c0 75 c0 e9 76 ff ff ff e8 0e ee f8 ff 0f 1f 00 66 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa <48> 8b 4e 08 48 89 f8 f3 0f 6f 81 38 01 00 00 48 8b 89 48 01 00 00
Nov 16 08:16:26 myhostname systemd-coredump[1977759]: Process 296174 (VirtualBox) of user 501 terminated abnormally with signal 11/SEGV, processing...
Nov 16 08:16:26 myhostname audit: BPF prog-id=408 op=LOAD
Nov 16 08:16:26 myhostname audit: BPF prog-id=409 op=LOAD
Nov 16 08:16:26 myhostname audit: BPF prog-id=410 op=LOAD
Nov 16 08:16:26 myhostname systemd-coredump[1977760]: Process 296287 (VirtualBoxVM) of user 501 terminated abnormally with signal 11/SEGV, processing...
Nov 16 08:16:26 myhostname audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-coredump@4-4098-1977759_1977760-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 16 08:16:26 myhostname systemd[1]: Started systemd-coredump@4-4098-1977759_1977760-0.service - Process Core Dump (PID 1977759/UID 0).
Nov 16 08:16:26 myhostname audit: BPF prog-id=411 op=LOAD
Nov 16 08:16:26 myhostname audit: BPF prog-id=412 op=LOAD
Nov 16 08:16:26 myhostname audit: BPF prog-id=413 op=LOAD
Nov 16 08:16:26 myhostname systemd[1]: Started systemd-coredump@5-4099-1977760_1977761-0.service - Process Core Dump (PID 1977760/UID 0).
Nov 16 08:16:26 myhostname audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-coredump@5-4099-1977760_1977761-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 16 08:16:26 myhostname systemd-coredump[1977761]: Resource limits disable core dumping for process 296174 (VirtualBox).
Nov 16 08:16:26 myhostname systemd-coredump[1977761]: Process 296174 (VirtualBox) of user 501 terminated abnormally without generating a coredump.
Nov 16 08:16:26 myhostname systemd[1]: systemd-coredump@4-4098-1977759_1977760-0.service: Deactivated successfully.
Nov 16 08:16:26 myhostname audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-coredump@4-4098-1977759_1977760-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 16 08:16:26 myhostname audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-coredump@5-4099-1977760_1977761-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 16 08:16:26 myhostname systemd-coredump[1977763]: Resource limits disable core dumping for process 296287 (VirtualBoxVM).
Nov 16 08:16:26 myhostname systemd-coredump[1977763]: Process 296287 (VirtualBoxVM) of user 501 terminated abnormally without generating a coredump.
Nov 16 08:16:26 myhostname systemd[1]: systemd-coredump@5-4099-1977760_1977761-0.service: Deactivated successfully.
Nov 16 08:16:26 myhostname audit: BPF prog-id=410 op=UNLOAD
Nov 16 08:16:26 myhostname audit: BPF prog-id=409 op=UNLOAD
Nov 16 08:16:26 myhostname audit: BPF prog-id=408 op=UNLOAD
Nov 16 08:16:26 myhostname audit: BPF prog-id=413 op=UNLOAD
Nov 16 08:16:26 myhostname audit: BPF prog-id=412 op=UNLOAD
Nov 16 08:16:26 myhostname audit: BPF prog-id=411 op=UNLOAD
Nov 16 08:16:26 myhostname audit: ANOM_PROMISCUOUS dev=enp1s0f0 prom=0 old_prom=256 auid=501 uid=501 gid=501 ses=3
Nov 16 08:16:26 myhostname kernel: r8169 0000:01:00.0 enp1s0f0: left promiscuous mode
Nov 16 08:16:26 myhostname kernel: vboxnetflt: 128977 out of 35818704 packets were not sent (directed to host)
Nov 16 08:16:26 myhostname abrt-dump-journal-core[2372]: Failed to obtain all required information from journald
Nov 16 08:16:26 myhostname abrt-dump-journal-core[2372]: Failed to obtain all required information from journald
Nov 16 08:16:26 myhostname abrt-dump-journal-core[2372]: Failed to obtain all required information from journald
Nov 16 08:16:26 myhostname abrt-dump-journal-core[2372]: Failed to save detect problem data in abrt database
Nov 16 08:16:26 myhostname abrt-dump-journal-core[2372]: Failed to obtain all required information from journald
Nov 16 08:16:26 myhostname abrt-dump-journal-core[2372]: Failed to save detect problem data in abrt database
Nov 16 08:16:54 myhostname Deskflow[9056]: [2025-11-16T08:16:54] INFO: leaving screen

Any suggestions as to a workaround (other than leaving my monitor on all the time) until a permanent fix is implemented?

Thanks

2

This looks like a known issue:
Issues - VirtualBox+libQt6Widgets - GitHub

As an alternative, I strongly recommend virt-manager.

1 Like
3

Hi Vladislav,

You’re not the first to recommend that. I’m going to start looking into it today as it crashed again.

1 Like
4

I don’t have the same problem with libQt, but recently, with virtualbox 7.2.4 and a previous version, my Windows guest started bootlooping and being very unstable.

I thought my .vdi disk image got corrupted, so I tried half a dozen earlier versions of backups but they all seemed bad.

Then in desperation I tried using the same .vdi with a vm in virt-manager, and the image and vm have no problems, totally stable.

I have no idea what the issue is, but with the amount of time I’ve already spent trying to solve it, this might very well be the last straw that pushes me to abandon virtualbox and use virt-manager going forward.

virt-manager configuration is rather intimidating and time consuming to get right compared to how virtualbox “just works” but it seems worth the effort. Or in my case, I don’t even currently have a choice with virtualbox being completely unusable.