I'm trying to setup a Kubernetes cluster in local machine using minikube in Windows environment and I'm getting this error
Any idea why I get this error?
Please enable VT-x on your computer BIOS.
For reference:
https://kubernetes.io/docs/tasks/tools/install-minikube/
Enable VT-x in your BIOS security settings (refer to documentation for your computer)
Related
! StartHost failed, but will try again: creating host: create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory
I am getting this issue when I am executing the [minikube start --driver=virtualbox] command in my windows machine. I have already enable the VT-X/AMD-v in my machine.
minikube start --no-vtx-check
This command create the kubertenes cluster with out any error.
If you have already enabled the feature in the BIOS, make sure you did not enable the Windows Hyper-V feature as well. Otherwise VirtualBox will not run.
I am following the instructions on this page(https://kubernetes.io/docs/tasks/tools/install-minikube/) to install kubernetes on windows 10. I have enabled virtualzation on my system and have installed virtualbox. When i try to start the minikube, it fails with this error:
>minikube start
* minikube v1.9.2 on Microsoft Windows 10 Home 10.0.18362 Build 18362
* Using the virtualbox driver based on existing profile
* Starting control plane node m01 in cluster minikube
* Creating virtualbox VM (CPUs=2, Memory=2200MB, Disk=20000MB) ...
! StartHost failed, but will try again: creating host: create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory
* Creating virtualbox VM (CPUs=2, Memory=2200MB, Disk=20000MB) ...
*
* [VBOX_VTX_DISABLED] Failed to start virtualbox VM. "minikube start" may fix it. creating host: create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory
* Suggestion: Virtualization support is disabled on your computer. If you are running minikube within a VM, try '--driver=docker'. Otherwise, consult your systems BIOS manual for how to enable virtualization.
* Related issues:
- https://github.com/kubernetes/minikube/issues/3900
- https://github.com/kubernetes/minikube/issues/4730
This is what i get when i do systeminfo from command prompt:
[03]: VirtualBox Host-Only Ethernet Adapter
Connection Name: VirtualBox Host-Only Network
DHCP Enabled: No
IP address(es)
[01]: ***.***.**.*
[02]: ****::****:****:****:****
[04]: VirtualBox Host-Only Ethernet Adapter
Connection Name: VirtualBox Host-Only Network #2
DHCP Enabled: No
IP address(es)
[01]: ***.***.**.*
[02]: ****::****:****:****:****
Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed.
Does anyone know how to fix this?
Thanks
[VBOX_VTX_DISABLED] can means that either virtualization is not enabled in BIOS or Hyper-V is running and not allowing to access to VMX.
Assuming that you have enabled the virtualization it is worth checking out the second option and try to disable the Hyper-V.
You can do that by using this command in powershell:
`bcdedit /set hypervisorlaunchtype off`
You may also want to disable those two features:
Virtual Machine Platform and Windows Subsystem for Linux
Both can be found at Turn Windows Features on/off
Please also note that Microsoft is constantly adding features that are enabling hyper-v and prevent virtualbox from using vtx. Depending on system version some of them could be missing in your system but its worth checking them out and disabling them.
Application Guard
Credential Guard
Device Guard
Containers
Hyper-V
Virtual Machine Platform
Windows Hypervisor Platform
Windows Sandbox
Windows Server Containers
Windows Subsystem for Linux 2 (WSL2)
Remember to do do a cold boot (shut down for 10 seconds and start it up)
I get an error :" Error starting host: Temporary Error: Error configuring auth on host: OS type not recognized" when trying to start minikube on windows 10. I have checked VT-x is enabled and I still can't run minikube, can any one help please
minikube delete
Delete C:\Users\username\.minikube folder.
minikube start again.
If this will not help I can advice you install minikube or kubernetes-cli using chocolatey.
I am trying to install Kubernetes on windows server 2016.
I tried to install minikube, and got some errors.
This is the tutorial that I followed:
https://www.assistanz.com/installing-minikube-on-windows-2016-server/
This is the command + error that I got:
PS C:\Windows\system32> minikube start –vm-driver=hyperv –hyperv-virtual-switch=Minikube
Starting local Kubernetes v1.10.0 cluster...
Starting VM... Downloading Minikube ISO
170.78 MB / 170.78 MB [============================================] 100.00% 0s
E1106 19:29:10.616564 11852 start.go:168] Error starting host: Error creating host: Error executing step: Running precreate checks.
: VBoxManage not found. Make sure VirtualBox is installed and VBoxManage is in the path.
Retrying.
E1106 19:29:10.689675 11852 start.go:174] Error starting host: Error creating host: Error executing step: Running precreate checks.
: VBoxManage not found. Make sure VirtualBox is installed and VBoxManage is in the path
================================================================================
An error has occurred. Would you like to opt in to sending anonymized crash
information to minikube to help prevent future errors?
To opt out of these messages, run the command:
minikube config set WantReportErrorPrompt false
================================================================================
Please enter your response [Y/n]:
Someone knows how to solve it?
I googled it, but no luck.
Thanks!
I was never able to get the config parameters to work with minikube start.
I was able to get past this error using the minikube config commands in PowerShell (should also work at a command prompt):
minikube config set vm-driver hyperv
minikube config set hyperv-virtual-switch ExternalSwitch
minikube config view
minikube delete
minikube start
For more information on the command run: minikube config -h
Looking at the documentation you have provided, I have noticed that the screenshot shows a slight difference to the one they've quote.
I have also found this command in another piece of documentation from kubernetes here, showing the same command as that from the screenshot.
I suggest you try the following command;
minikube start --vm-driver=hyperv --hyperv-virtual-switch=Minikube
It is true that OP has pasted the incorrect command, because there is - instead of --. I tried to pass this arguments to minikube and all you get is an instant error. So the issue must be somewhere else. I remember having similar issue and it got resolved after deleting the .kube and .minikube folders and trying to run it again.
After taking a closer look this tutorial is destined for installation of minikube inside of a Windows Server 2016 Virtual Machine, so you have to have a Nested Virtualization able hardware:
Prerequisites The Hyper-V host and guest must both be Windows Server
2016/Windows 10 Anniversary Update or later. VM configuration version
8.0 or greater. An Intel processor with VT-x and EPT technology -- nesting is currently Intel-only. There are some differences with
virtual networking for second-level virtual machines. See "Nested
Virtual Machine Networking".
So the main question is, is that true in your scenario? Are you trying to perform your steps on Windows Server Hyper-V virtual machine with nested virtualization feature?
If you confirm that I have technical possibilities to check it in that scenario.
Otherwise I recommend using the "traditional way" of running minikube in Windows, according for example to this tutorial.
I am a beginner to Kubernetes and starting off with this tutorial. I installed VM and expected to be able to start a cluster by using the command:
minikube start
But I get the error:
Starting local Kubernetes v1.10.0 cluster...
Starting VM...
E0911 13:34:45.394430 41676 start.go:174] Error starting host: Error
creating host: Error executing step: Creating VM.
: Error setting up host only network on machine start: The host-only
adapter we just created is not visible. This is a well known
VirtualBox bug. You might want to uninstall it and reinstall at least
version 5.0.12 that is is supposed to fix this issue.
It says that it is a well known bug in Virtualbox but I installed its latest version. Any ideas?
Figured out the issue. VirtualBox was not installed correctly as Mac had blocked it. It wasn't obvious at first.
Restarting won't work if VirtualBox isn't installed correctly.
System Preferences -> Security & Privacy -> Allow -> Then allow the software corporation (in this case Oracle)
Restart
Now it worked as expected.
Have you tried restarting your computer after installing the VirtualBox ?
(seems to be also a known bug to docker-machine which is used by minikube to initialize you local env)
This definitely worked for me, starting minikube by specifying vm-driver and kubernetes-version
minikube start --vm-driver=hyperkit --kubernetes-version v1.16.0
Faced a similar issue in Mac after upgrading to big sur. The running minikube instance started giving the same error.
The solution that worked for me was to run a minikube delete, followed by a minikube start.
More combination of this option can be found in the thread below -
https://github.com/kubernetes/minikube/issues/3614