Slow boot up and Guest seems to be unresponsive (6.1.32)

Discussions related to using VirtualBox on Windows hosts.
Post Reply
vbuser100
Posts: 3
Joined: 25. Feb 2022, 21:04

Slow boot up and Guest seems to be unresponsive (6.1.32)

Post by vbuser100 »

I see that the VM takes about 6 minutes to boot.

Additionally the CPU of the host some times gets really high due to the VM.

And additionally I see in the logs something like this: Guest seems to be unresponsive

I can not see where is the problem.

Any help would be appreciated.

Thanks in advance.
Attachments
vbox.zip
(39.63 KiB) Downloaded 6 times
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows, Linux

Re: Slow boot up and Guest seems to be unresponsive (6.1.32)

Post by scottgus1 »

You have the 6.1.32 Hyper-V bug.

Our forum guru 'fth0' has done some troubleshooting and pins down these possibilities to try (HCVI = Microsoft 'Memory Integrity'):
6.1.32 without Hyper-V
6.1.30 with Hyper-V but without HVCI
6.1.26 with Hyper-V and HVCI.

To disable Hyper-V, see HMR3Init: Attempting fall back to NEM (Hyper-V is active)
vbuser100
Posts: 3
Joined: 25. Feb 2022, 21:04

Re: Slow boot up and Guest seems to be unresponsive (6.1.32)

Post by vbuser100 »

Thanks for the answer.

I have disabled Hyper-V as mentioned in the pointed thread and it seems the VM boots up faster.

However, the drawback is that I cannot use WSL2.

Is there anywy VB and WSL can coexist?
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows, Linux

Re: Slow boot up and Guest seems to be unresponsive (6.1.32)

Post by scottgus1 »

WSL2 does require Hyper-V.
vbuser100 wrote:Is there anywy VB and WSL can coexist?
scottgus1 wrote:6.1.30 with Hyper-V but without HVCI
6.1.26 with Hyper-V and HVCI.
vbuser100
Posts: 3
Joined: 25. Feb 2022, 21:04

Re: Slow boot up and Guest seems to be unresponsive (6.1.32)

Post by vbuser100 »

Understood, thanks.

I hope next release will come up soon with this bugfix and working with Hyper-V.
Post Reply