Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warning: Using VirtualBox, WSL2 and Vagrant together causes BSOD on Windows 11 #109

Open
Xaeco opened this issue Dec 21, 2021 · 0 comments

Comments

@Xaeco
Copy link

Xaeco commented Dec 21, 2021

This is more of a note for other people in the same boat.

Apparently there are issues running VirtualBox, WSL2 and Vagrant together on Windows 11.
I'm getting BSOD very consistently when I use Vagrant destroy and then Vagrant up from within WSL2.
Note:

  • Unsure on the exact combination or point where it fails.
  • Haven't tried creating VMs with different settings.
  • Some articles say you can disable the Windows Hyper-V feature and VirtualBox will be ok, however WSL2 requires that feature to be on.
  • Need to test creating/deleting VMs from within Windows to see if it causes VirtualBox to crash the PC.

I see recently Windows 11 guest support was added but Windows 11 host is not officially supported.
Some threads of issues people have been experiencing.
MicrosoftDocs/WSL#798
https://www.virtualbox.org/ticket/20536

Using:

Windows 11 Pro (Version 21H2 Build 22000.376)
VirtualBox Version 6.1.30 r148432 (Qt5.6.2)
WSL2 running Ubuntu 20.04
Vagrant 2.2.19 installed within WSL2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant