Maybe this? From Reddit: I had the same problem, with VirtualBox 7.0.2 running under macOS Ventura on a MacBook Pro 16 (2019) and Windows 11 (22H2) as guest. My **workaround** is **manually setting the virtual graphics controller to VBoxVGA** (instead of VBoxSVGA). https://www.reddit.com/r/virtualbox/comments/yh4dad/windows_11_guest_os_keep... Robin Klitscher <robin.klitscher@gmail.com> skrev: (25 december 2022 08:34:36 CET)
openSUSE Leap 15.4 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 5.14.21-150400.24.38-default (64-bit)
VirtualBox 7.0.4. I'd been running Windows 10 as guest for several years, successful and solid. Recently upgraded to Windows 11 as guest, also successfully.
Now, all of a sudden and for no reason I can account for, VBox flatly refuses to run. I can't even start it to re-install guest(s). Calling it from a commandline produces this (sorry about the line wrap):
Qt WARNING: QObject::connect: No such signal UITabBar::currentChanged(int) Qt WARNING: QObject::connect: No such signal UITabBar::tabMoved(int,int) Qt WARNING: QObject::connect: No such signal UITabBar::tabBarClicked(int) Qt WARNING: QObject::connect: No such signal UITabBar::tabBarDoubleClicked(int) /usr/bin/VirtualBox: line 70: 15387 Segmentation fault (core dumped) LD_LIBRARY_PATH="/usr/lib/virtualbox${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}" /usr/lib/virtualbox/VirtualBox6 $@
Is there anything (simple!) I can do about that?
-- Robin K Wellington "Harbour City" New Zealand
-- Skickat från min Android-enhet med K-9 Mail. Ursäkta min fåordighet.