Vbox Windows 11 Pro Host - VM stuck on booth

[dedshaw1612]

I've already browsed around on some other topics and tried to implement those solutions already. I have:

+ Enabled Hyper V
+ Disabled 3D Hardware Acceleration on the VM Settings
+ Uninstalled my instance of VBOX, and ran the installer "As Administrator"

It only fixed my issues of getting an initial error and the VM not even running. But now it gets stuck on boot and does nothing. Screenshot below

Thanks in advance

[scottgus1]

That screenshot is from a theoretically running VM with messages from some sort of OS inside the VM.

Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.

Right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.

Enabled Hyper V

This one is possibly going to make things worse. But the log will show if there are actual issues running the Virtualbox 'hardware' or if the problem might be inside the VM's OS. Frankly, I have never seen a Windows boot program say it is going to start three different windows OS's. So we already have something unusual about the OS inside the VM. And that something unusual might be the cause of the problem.

What OS do you have running in the VM?

[dedshaw1612]

Thank you for your response. My coworker gave me a different VM that was proven to have worked, not sure what was wrong with the other one. I fiddled with the new one quite a bit, but as you stated maybe Hyper V was causing problems. I disabled HyperV and the VM now runs like a champ. I'm curious to what HyperV does exactly as many other forums said to Enable it to solve problems.

Thanks again

[scottgus1]

many other forums said to Enable it to solve problems.

If those other forums weren't the Virtualbox forum, we wouldn't know why they said what they said. But I'd wager the number of times this forum's gurus have told a Windows host user to ENable Hyper-V to fix a VM problem could be counted on one hand, perhaps one finger. Far more common here is to suggest to DISable Hyper-V. See I have a 64bit host, but can't install 64bit guests and HMR3Init: Attempting fall back to NEM (Hyper-V is active).

[scottgus1]

I'm curious to what HyperV does exactly

From "HMR3Init: Attempting fall back to NEM (Hyper-V is active)":

Hyper-V is a type-1 hypervisor, which accesses the hardware first before any OS runs, and therefore interferes with other programs that need "virtualization technology", like Virtualbox, which is a type-2 Hypervisor.

[LinuxDevel]

I have similar issue on windows 11.

If I boot a vm that has more than one CPU defined it's stuck just after bootloader. Black screen with a blinking cursor.
If I use only one CPU, it boots fine.. But is pretty much useless for me since performance is low.

[mpack]

@LinuxDevel: you don't say what version of VirtualBox you are using. However there has been a problem reported for VirtualBox 6.1.32 which has the symptoms you describe and is worked around by reverting to 6.1.30 for now.

[LinuxDevel]

@LinuxDevel: you don't say what version of VirtualBox you are using. However there has been a problem reported for VirtualBox 6.1.32 which has the symptoms you describe and is worked around by reverting to 6.1.30 for now.

Thanks, I was using VirtualBox 6.1.32. Reverted to 6.1.30 and that seems to fix the issue. Really strange though, a friend of mine is having exact same windows version (And hardened by the same company) and is using 6.1.32, he is not facing the same issue.

[scottgus1]

There is more nuance to the issue you're facing than just .32 vs .30. The capabilities of the host, whether Hyper-V is enabled, whether Microsoft Memory Integrity is enabled, all play roles in the issue, and can influence whether .32 will work or or .30 or earlier is required as a workaround.

[LinuxDevel]

There is more nuance to the issue you're facing than just .32 vs .30. The capabilities of the host, whether Hyper-V is enabled, whether Microsoft Memory Integrity is enabled, all play roles in the issue, and can influence whether .32 will work or or .30 or earlier is required as a workaround.

Thanks. Well, on my machine I am not able to deactivate Hyper-V or Memory Integrity protection completely due to company wide polices, so VirtualBox .30 somehow works, but seems to be very laggy and sometimes crashes when running e.g. windows vXX as guest. A linux guest works better but is not 100% either.