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.
VirtualBox 6.1 and Hyper-V - vbox unusable
-
- Site Moderator
- Posts: 39134
- 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
Yes. VirtualBox and Hyper-v compete for the same resources. What is your question?
Re: VirtualBox 6.1 and Hyper-V - vbox unusable
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
no question, I was just hoping this was fixed since 2018
-
- Site Moderator
- Posts: 20945
- 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
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.kcris wrote:no resources competing 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.
Re: VirtualBox 6.1 and Hyper-V - vbox unusable
thank you! all clear now!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.
ps: I have migrated my VB machine to win10's own Hyper-V (gen1). The new vm works without issues.