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

crash while trying to start minikube on ubuntu18.04 on proxmox #6498

Closed
liorms opened this issue Feb 5, 2020 · 2 comments
Closed

crash while trying to start minikube on ubuntu18.04 on proxmox #6498

liorms opened this issue Feb 5, 2020 · 2 comments
Labels
cause/nested-vm-config When nested VM's appear to play a role kind/support Categorizes issue or PR as a support question. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@liorms
Copy link

liorms commented Feb 5, 2020

liorms@k8su1804:~$ minikube start
o minikube v1.0.1 on linux (amd64)
$ Downloading Kubernetes v1.14.1 images in the background ...

Creating virtualbox VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...

! Unable to start VM
X Error: [VBOX_VTX_DISABLED] create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory
i Advice: In some environments, this message is incorrect. Try 'minikube start --no-vtx-check'

  • If the above advice does not help, please let us know:

Creating virtualbox VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...

! Unable to start VM: create: creating: Unable to start the VM: /usr/bin/VBoxManage startvm minikube --type headless failed:
VBoxManage: error: VT-x is not available (VERR_VMX_NO_VMX)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole

Details: 00:00:00.897179 Power up failed (vrc=VERR_VMX_NO_VMX, rc=NS_ERROR_FAILURE (0X80004005))

@tstromberg
Copy link
Contributor

minikube v1.0 is very very old: do you mind retrying with v1.7.0?

Also, it's quite possible that proxmox does not support VirtualBox. I'm not sure what virtualization it supports, but I would suggest trying kvm2.

@tstromberg tstromberg added cause/nested-vm-config When nested VM's appear to play a role triage/needs-information Indicates an issue needs more information in order to work on it. kind/support Categorizes issue or PR as a support question. labels Feb 5, 2020
@liorms
Copy link
Author

liorms commented Feb 6, 2020

hi,
it turned up to be proxmox configuration issue.
proxmox does support vbox.
when configured ok - it even starts with older kube* versions:
liorms@k8su1804:~$ minikube start
o minikube v1.0.1 on linux (amd64)
$ Downloading Kubernetes v1.14.1 images in the background ...
i Tip: Use 'minikube start -p ' to create a new cluster, or 'minikube delete' to delete this one.
: Restarting existing virtualbox VM for "minikube" ...
: Waiting for SSH access ...

  • "minikube" IP address is 192.168.99.100
  • Configuring Docker as the container runtime ...
  • Version of container runtime is 18.06.3-ce
    : Waiting for image downloads to complete ...
  • Preparing Kubernetes environment ...
    @ Downloading kubeadm v1.14.1
    @ Downloading kubelet v1.14.1
  • Pulling images required by Kubernetes v1.14.1 ...
    : Relaunching Kubernetes v1.14.1 using kubeadm ...
    : Waiting for pods: apiserver proxy

liorms@k8su1804:~$ minikube status
host: Running
kubelet: Running
apiserver: Running
kubectl: Correctly Configured: pointing to minikube-vm at 192.168.99.100

ALL WORKS...
:-)

@liorms liorms closed this as completed Feb 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cause/nested-vm-config When nested VM's appear to play a role kind/support Categorizes issue or PR as a support question. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

2 participants