I know a solution has been found already, but I wanted to share my experience from tonight:
I commented on the original post but have since read through this post and the other and have reviewed the logs a bit, comparing them to my own. Generally speaking, I'm seeing the same issues from
lelegards logs.
I noted in both of our logs, this was occurring re: Hyper-V:
Code: Select all
00:00:00.691819 NEM: Disable Hyper-V if you need X2APIC for your guests!
00:00:00.691930 NEM:
00:00:00.691930 NEM: NEMR3Init: Snail execution mode is active!
00:00:00.691930 NEM: Note! VirtualBox is not able to run at its full potential in this execution mode.
00:00:00.691931 NEM: To see VirtualBox run at max speed you need to disable all Windows features
00:00:00.691931 NEM: making use of Hyper-V. That is a moving target, so google how and carefully
00:00:00.691931 NEM: consider the consequences of disabling these features.
00:00:00.691931 NEM:
00:00:00.691942 CPUM: No hardware-virtualization capability detected
On the previous ticket, I posted about how simply adjusting the resolution fixes the issue. This does seem to work, although not as reliably as I initially thought. It still seems to fix the issue when the screen does go black for me, but it doesn't seem to always stop it from re-appearing. That said, I haven't had to adjust it in the devstation I'm working from, so take it with a grain of salt.
I'm also using an Intel alder lake processor, more info below:
Code: Select all
OS Name Microsoft Windows 11 Enterprise
Version 10.0.22621 Build 22621
Processor 13th Gen Intel(R) Core(TM) i5-1340P, 1900 Mhz, 12 Core(s), 16 Logical Processor(s)
Installed Physical Memory (RAM) 16.0 GB
I haven't previously enabled Hyper-V on this workstation (it's fairly recently provisioned, I'm the only user), so Hyper-V
should be in the default state on this machine. Also, this being the default outcome for booting into Fedora on VBox using a 13th Gen Intel host is obviously not great.
I found two potential solutions for the Hyper-V problem in an attempt to find something more scalable.
1) Changing the paravirtualization to KVM instead of
Default or
Hyper-V
On boot, I'm not seeing any of the NEM lines mentioned above.
2) Similarly by enabling the Nested VT-x/AMD-V toggle and leaving the paravirtualization on default
There is a very easy to find stackoverflow article that mentions how to easily enable the toggle. I'm fairly new to working with
VBox, but I'm betting this is most likely something that can be set in a config file.
After enabling the toggle for the Nested VT-x/AMD-V for the processor, like the above, the NEM lines from the initial logs weren't
present
I'm not really feeling super confident about these solutions yet, but just wanted to mention my findings in-case someone else can roll with it.