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)
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.
When I am not connected to the VPN, minikube is starting as expected:
PS C:\Windows\system32> minikube start
* minikube v1.9.2 on Microsoft Windows 10 Enterprise 10.0.18363 Build 18363
* Using the hyperv driver based on existing profile
* Starting control plane node m01 in cluster minikube
* Updating the running hyperv "minikube" VM ...
* Preparing Kubernetes v1.18.0 on Docker 19.03.8 ...
E0408 01:00:31.223159 17528 kubeadm.go:331] Overriding stale ClientConfig host https://192.168.137.249:8443 with https://172.17.118.34:8443
* Enabling addons: default-storageclass, storage-provisioner
* Done! kubectl is now configured to use "minikube"
Once I am connectong to the VPN antri triing to start the minikube, it fails with an error:
PS C:\Windows\system32> minikube start
* minikube v1.9.2 on Microsoft Windows 10 Enterprise 10.0.18363 Build 18363
* Using the hyperv driver based on existing profile
* Starting control plane node m01 in cluster minikube
* Updating the running hyperv "minikube" VM ...
! StartHost failed, but will try again: provision: IP not found
* Updating the running hyperv "minikube" VM ...
*
X Failed to start hyperv VM. "minikube start" may fix it.: provision: IP not found
*
* minikube is exiting due to an error. If the above message is not useful, open an issue:
- https://github.com/kubernetes/minikube/issues/new/choose
I was facing a similar issue while running the following command:
minikube start --vm-driver="hyperv" --hyperv-virtual-switch="minikube"
Then I went through some github and stackoverflow threads and was able to resolve my issue by running following command:
minikube delete
minikube start --vm-driver="hyperv"
In my case, passing 'hyperv-virtual-switch' argument was causing the issue.
I would suggest you to check if your virtual switch is configured with your vpn network or not.
If not, then you can perform the following steps to do so:
Go to network and sharing center settings of windows:
Select your network and open the properties window for it. Go to the "Sharing" tab and allow your configured virtual switch over there.
Ultimate Goal
From a dotnet/core/sdk devcontainer (using VSCode Remote Containers), debug a .NET Core app running in a kubernetes cluster hosted on another vm of my host machine.
Current Setup
Docker Desktop for Windows running via Hyper-V
default DockerNAT network adapter
Ubuntu VM (multipass) running on same Hyper-V host
microk8s cluster running on this ubuntu instance
default "Default Switch" network adapter
Errors
When I try to ping the ubuntu vm from a docker container by hostname, the IP is resolved properly but I get the error "Destination Host Unreachable"
When I try to curl the cluster api, I get the error "No route to host"
I put this problem aside for a week, and over that time the host has been rebooted multiple times, but no further modifications were made to the networking, Hyper-V setup, etc.
Starting the Ubuntu VM today, the IP changed from what used to be 172.?.?.? to 192.168.92.x . I do not know what caused this change.
Now, Docker Desktop containers can ping the Ubuntu VM and curl the microk8s /api endpoint. Until such a time that I can reproduce the issue, I will mark this question as "solved" and reopen and try Nick's recommended solution if the issue returns.
I am new to virtual machines so pardon my ignorance.
I have a host machine running Windows Server 2012 R2 and I'm trying to run a VM with Windows 8.1 Enterprise using Hyper-V. I need to be able to use USB devices on the VM.
Please check screenshot for the Hyper-V settings and the VM settings. The VMConnect does not have 'Show Options' to select local resources.
I tried using Remote Desktop Connection to the VM but nothing happens when USB devices are plugged in the host machine.
Not sure what I'm missing here.
Any help in fixing this will be greatly appreciated. Thanks!
Hyper-V Settings
VM Settings
If the USB device you want to use in the VM is a USB memory stick share it with the RDP local resources option as a Drive instead of the trying to replicate the USB port itself.
Eg:
There is a dependency(XRDP) to be installed in order to enable Enhanced Session Mode. Please follow the following steps or watch this video for more clarity.
Visit https://www.youtube.com/watch?v=LS2m6iyG7_M&ab_channel=VikeshYadav
On hyper-v linux machine:
git clone https://github.com/Microsoft/linux-vm-tools
cd linux-vm-tools/ubuntu/18.04/
sudo chmod +x install.sh
sudo ./install.sh
On windows machine:
set-vm -VMName ubuntu -EnhancedSessionTransportType HvSocket
I've got Win8.1 guest system (1 gen VM) and Win10 as host. Tried pretty much everything, but wasn't able to enable Enhanced Mode (simply grayed out all the time), unless I enabled RDP connections in the guest system (Control Panel, Allow remote access to your computer). After this change VMConnect with ability to share local resources appeared on attempt to connect to the VM.
Hope this helps all the people who find this thread while googling.
Good morning to all,
I have installed Centos 6.7 x86 64 on a Virtual Machine. It is not the first time I'm using this virtual machine...I have already installed a Windows xp 32 bit system, and a Centos 7 with graphical interfac system, and they both connected as well. This time I can't start a connection. In the virtual machine I set the parameters on "NAT" and "Connected Cable", and here I report my inux configurations:
Configure eth0
#
vi /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE="eth0"
NM_CONTROLLED="yes"
ONBOOT=yes
HWADDR=A4:BA:DB:37:F1:04
TYPE=Ethernet
BOOTPROTO=static
NAME="System eth0"
UUID=5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03
IPADDR=192.168.8.171
NETMASK=255.255.255.0
Configure Default Gateway
#
vi /etc/sysconfig/network
NETWORKING=yes
HOSTNAME=centos6
GATEWAY=192.168.8.3
Restart Network Interface
#
/etc/init.d/network restart
Configure DNS Server
#
vi /etc/resolv.conf
nameserver 8.8.8.8
"
I've copied this parameters from a website guide. Anyway, I tried also setting NM_CONTROLLED=no and ONBOOT=no, but nothing works.
Even if I try to pinging google by the command
ping www.google.it
it doesn't work.
Any suggestions?