VM Dump when hardware (screen) Idles

[MoinDix]

Hi all,

the following setup:
HW:
Threadripper 3960x 24 core - 256GB ram
Video RX 7800 XT - 5K display

SW
CachyOS Linux - Kernel 7.2.3-1 - X11 - KDE 6.7.4/6.29.0
VB 7.2.16r174877

Guest
Windows 11 PRO - 10 CPU - 32 GB Ram
2 Virt HD 250 GB & 150 GB
Netw bridged paravirt
Graph control VBoxSVGA - no 3D accel

ISSUE:
When the HW ( linux) is idle the VB guest machine abort, until now I only detect this after idle time.
After abort the windows guest start normal
I looked in the windows log and do see anything auspicious - presuming it would be the windows itself
looking at the VBlog, i'm not an expert (far from it) i do no see anything in these logs either.
I attach the zip file with the VBlog files + Linux Log files
--
after some additional digging ... I found VM core dump for each Windows 11 abort

(full details in attach file)

Sep 07 19:23:33 dracarys-cos systemd-coredump[301357]: [🡕] Process 168157 (VirtualBoxVM) of user 1000 dumped core.

Stack trace of thread 168157:
#0 0x00007f74b6a49671 _ZNK17QAccessibleWidget4textEN11QAccessible4TextE (libQt6Widgets.so.6 + 0x449671)
#1 0x00007f74b675150e _ZN14QWidgetPrivate18setWindowTitle_sysERK7QString (libQt6Widgets.so.6 + 0x15150e)
#2 0x00007f74b675208b _ZN14QWidgetPrivate21setWindowTitle_helperERK7QString (libQt6Widgets.so.6 + 0x15208b)
#3 0x00007f74b676a092 _ZN14QWidgetPrivate24setWindowModified_helperEv (libQt6Widgets.so.6 + 0x16a092)
#4 0x00007f74b674fa09 _ZN14QWidgetPrivate6createEv (libQt6Widgets.so.6 + 0x14fa09)
#5 0x00007f74b674ee20 _ZN7QWidget6createEybb (libQt6Widgets.so.6 + 0x14ee20)
#6 0x00007f74b6753511 _ZN7QWidget14setWindowStateE6QFlagsIN2Qt11WindowStateEE (libQt6Widgets.so.6 + 0x153511)
#7 0x00007f74b67536d3 _ZN7QWidget13showMaximizedEv (libQt6Widgets.so.6 + 0x1536d3)
#8 0x00007f74bc974fed _ZN23UIDesktopWidgetWatchdog29updateHostScreenConfigurationEi (UICommon.so + 0x374fed)
#9 0x00007f74bc9752bd _ZN23UIDesktopWidgetWatchdog18sltHostScreenAddedEP7QScreen (UICommon.so + 0x3752bd)
#10 0x00007f74b7a0f13b n/a (libQt6Core.so.6 + 0x20f13b)
#11 0x00007f74b704d951 _ZN22QWindowSystemInterface17handleScreenAddedEP15QPlatformScreenb (libQt6Gui.so.6 + 0x24d951)
#12 0x00007f74b5bbcab7 _ZN14QXcbConnection28initializeScreensFromMonitorEP21xcb_screen_iterator_tiPP10QXcbScreenb (libQt6XcbQpa.so.6 + 0x3fab7)
#13 0x00007f74b5bbd7ca _ZN14QXcbConnection17initializeScreensEb (libQt6XcbQpa.so.6 + 0x407ca)
#14 0x00007f74b5bb3f81 _ZN14QXcbConnection14handleXcbEventEP19xcb_generic_event_t (libQt6XcbQpa.so.6 + 0x36f81)
#15 0x00007f74b5bb5af3 _ZN14QXcbConnection16processXcbEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6XcbQpa.so.6 + 0x38af3)
#16 0x00007f74b5bd77f7 n/a (libQt6XcbQpa.so.6 + 0x5a7f7)
#17 0x00007f74bc1f3f4d n/a (libglib-2.0.so.0 + 0x6bf4d)
#18 0x00007f74bc1f5478 n/a (libglib-2.0.so.0 + 0x6d478)
#19 0x00007f74bc1f55d2 g_main_context_iteration (libglib-2.0.so.0 + 0x6d5d2)
#20 0x00007f74b7cecb0b _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x4ecb0b)
#21 0x00007f74b79a4c54 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x1a4c54)
#22 0x00007f74b79999e4 _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x1999e4)
#23 0x00007f74be4d35e2 TrustedMain (VirtualBoxVM.so + 0x5b5e2)
#24 0x00007f74c3627d0e n/a (libc.so.6 + 0x27d0e)
#25 0x00007f74c3627e4b __libc_start_main (libc.so.6 + 0x27e4b)
#26 0x000055f8be518335 n/a (VirtualBoxVM + 0x3335)


If anyone could have a look at this , logs i would appreciate this
-----

Wim

[MoinDix]

All,

Additional info, I did the following test.

- when I logout of the guest VM (windows 11), the issue does not happen when the screen becomes ideal

- when logged in the VM guest session abort after the screen becomes ideal

I discovered this the past days that my guest VM (Win11) was still running one morning, but with an initial login screen, Win 11 updated during the night and rebooted
Yesterday evening I logged out from the Win11 this morning Win11 is still running

Wim

[MoinDix]

All,

The issue is longer happening, resolved(!?)

What I changed, reading thoroughly through the log etc, I deducted that it had to do with my display, the fact that is goes off(??).
I changed, disabled the "smart energy mode" and just keep the display on 'stand-by'

since I did this, the VMs are still running in the morning.

Somehow QT framework is unable to handle this.

Wim