VirtualBox 6.1 and Hyper-V - vbox unusable

Discussions related to using VirtualBox on Windows hosts.
Post Reply
kcris
Posts: 8
Joined: 7. May 2021, 10:33

VirtualBox 6.1 and Hyper-V - vbox unusable

Post by kcris »

Hi,

I have a system with WSL2 enabled.
Virtualbox is able to boot, but apart from that, it is practically unusable.
Performace is terrible, a click sometimes takes seconds, same for keys being pressed.

Disabling WSL2 and using WSL1 (no hypervisor) fixes all this.
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: VirtualBox 6.1 and Hyper-V - vbox unusable

Post by mpack »

Yes. VirtualBox and Hyper-v compete for the same resources. What is your question?
kcris
Posts: 8
Joined: 7. May 2021, 10:33

Re: VirtualBox 6.1 and Hyper-V - vbox unusable

Post by kcris »

While trying to use VirtualBox, there was a single, IDLE wsl machine started, so no resources competing with VirtualBox.

no question, I was just hoping this was fixed since 2018
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: VirtualBox 6.1 and Hyper-V - vbox unusable

Post by scottgus1 »

kcris wrote:no resources competing with VirtualBox.
Not exactly true. Hyper-V is a type-1 hypervisor, meaning it touches the hardware even before the host OS and definitely before Virtualbox, which is a type-2 hypervisor. So when a service requiring Hyper-V is active, even if that service is not taking CPU cycles, Hyper-V is active and in constant interference with Virtualbox.

The capability of running Virtualbox on top of Hyper-V is an ongoing dev project and is not there yet with your host and VM OS's.
kcris
Posts: 8
Joined: 7. May 2021, 10:33

Re: VirtualBox 6.1 and Hyper-V - vbox unusable

Post by kcris »

The capability of running Virtualbox on top of Hyper-V is an ongoing dev project and is not there yet with your host and VM OS's.
thank you! all clear now!

ps: I have migrated my VB machine to win10's own Hyper-V (gen1). The new vm works without issues.
Post Reply