-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
virtualbox: --no-vtx-check: host timed out in 120.000000 seconds #6952
Comments
Before this I've not seen a case where Do you mind sharing the output of:
Maybe a VirtualBox expert can step in and suggest how to debug the VM startup here? |
@tstromberg thanks for following up. Here's the output you requested:
|
Hi! Do you mind checking if this updated minikube binary fixes the issue for you? I suggest first running "minikube delete": https://storage.googleapis.com/minikube-builds/7565/minikube-windows-amd64.exe |
Hey, do you mind if we reopen? I am facing the very same issue here on recent Windows 10 Pro. The binary you linked did not help. Still the vtx check fails. And the resulting VM hangs on boot. I can use HyperV just fine, when I enable it and tell minikube to use it. I would prefer using VirtualBox as it seems to allow me to configure it through minikube more than HyperV. So, it's important for me to have the error go away :) This machine is VT-X capable (it's running an i9-10900k and I am not running in a VM, so this is not the nested VM support issue others have). EDIT: The traces below are actually collected with a recent version if minikube, not the binary you provided. Since this version is newer than the binary, I used it to collect the trace. I can use the binary too, if you'd like. Maybe there's gonna be something in the logs. THe end-user behavior is the same, though. It either complains about noVTX or it hangs on booting the kernel :)
Now, with
|
Actually, strike that. I am a dumbo... Turns out, I did not fully uninstall HyperV (even though I believed I did). I removed both the HyperV feature as well as Windows Hypervisor Platform and Virtual Machine Platform. After uninstallling all these (maybe not all of them have to be gone, I wiped all in one go), the vtxCheck is also passing! (I wonder if one could keep HyperV installed, but just disable its startup, such that its quicker to rotate between the two). See https://www.virtualbox.org/ticket/18387 Let this be a warning for the likes of me. When Minikube complains about noVtx and VirtualBox hangs when booting a vtx VM (even a custom one you create using a live SysRescueCd) -- you got HyperV running. Kill it! EDIT: I've been testing this on a different machine over the weekend, and turns out, if you install either Hyper-V or the Virtual Machine Platform, VirtualBox can't access vtx. The problem is, Virtual Machine Platform is required by WSL2. So, if you are into WSL (and recent Windows 10 will force you to use it, even if you only want to use the WSL-1-like Linux distros), you will have to make due with running minikube over Hyper-V. As far as I can tell, it is not that big of a deal ( |
I am having the same issue on a Windows 10 Home machine. Virtualization is enabled, and I am able to run other VMs using VirtualBox.
I have tried using the --no-vtx-check, and I end up getting a timeout. Looking at the VM in VirtualBox, it appears to be stuck at "Booting the kernel."
The exact command to reproduce the issue:
minikube start
The full output of the command that failed:
The output of the
minikube logs
command:The operating system version: Microsoft Windows 10 Home 10.0.19577 Build 19577
The text was updated successfully, but these errors were encountered: