VirtualBox behaves suspiciously after Docker on Win10-Home
Disable Hyper-V for coexistence of Docker and VirtualBox on Windows10-Home.
I will leave the progress and procedure here.
The point
-When using Docker, Hyper-V is enabled and VirtualBox does not work properly (sometimes).
-Hyper-V can be used even on Win10-Home. ---- However, the settings cannot be changed from "Windows Features" ---- Can be set from the command line
-Originally, there is a story that VirtualBox 6 or later can coexist with Hyper-V.
・ (Hyper-V switching does not seem to be in BIOS / UEFI)
environment
Win10-Home VirtualBox 6.1
- Linux shell (WSL2) has been installed on Win10 Confusingly, VirtualBox and Windows Subsystem for Linux (probably WSL2) Environment using both
Other versions are omitted
Symptoms and course
I used Ubuntu 20.04 with VirtualBox.
After that, I newly introduced Docker on the host OS side (that is, Win10).
→ The behavior of Ubuntu20.04 on VirtualBox is strange. (The OS goes down when you operate make or something on the terminal. For details, wasureta)
"By the way, I remember hearing that'Hyper-V is enabled when Docker is installed ...'"
Anyway, disable Hyper-V → VirtualBox Ubuntu 20.04 is stable again.
Precautions
You will find false information (?) That "Hyper-V cannot be used on Win10-Home (?)".
Probably because of the balance with WSL, I think that it changed later so that Hyper-V can be used even on Win10-Home. (* It is possible that Hyper-V can be used because WSL is enabled.)
However, as of October 2020, Hyper-V could not be set from the GUI.
↓ For Windows10 Professional
↑ As you can see, the Hyper-V checkbox appears in Win10-Pro, but it doesn't seem to appear in Win10-Home.
Therefore, it needs to be set from the command line.
Command to turn off Hyper-V
PowerShell(Administrator run)
bcdedit /set hypervisorlaunchtype off
Reboot
Wasn't there a Hyper-V setting field in UEFI?
In the old days, I feel that I used to switch between enable / disable with BIOS or UEFI. Is it a misunderstanding?
Recommended Posts