The version of VirtualBox and the version of the extension packs that VirtualBox has installed must be the same or lower version. It looks like you still have 4.1.8 extensions packs installed in VirtualBox 4.1.2.
Open Virtualbox, on the File menu select preferences. A new window will open. Select Extensions. Now mark all extensions and uninstall them using the button with the small red x.
If you want to install again the extension pack (if you need to use USB or RDP), please go to this page, and download ones that match your VirtualBox version.
More or less inclusive guide to running Kurbernetes :
Clear-up : all of the following is for linux-only as Kubernetes can only run whithin a linux or mac (same difference) environement.
additionally Kubernetes.io specifies that only the ubuntu ditribution is supported.
There is possibly an assumption of being able to run an ubuntu VT-D utilising VM inside windows and inside the ubuntu VM boot another VT-D utilising VM.
As I understand it, this is not possible and Kubernetes should update their webpage and guides accordingly.
Finally it's more than possible that hardware is a factor here. IOMMU support is a necessity and so is enbling it in the BIOS.
I'd also highly recommend having more than 4GB of ram for this. (especially if the two-tiered VT-d emulation IS possible and that's what you're attempting).
The info used here was retrieved from :
EMULATING on a LOCAL machine :
I imagine this is what you want to see :
Here's what I did (the following is the easiest solution of the three) :
mkdir temp
cd temp
sudo apt update && sudo apt install libvirt-bin qemu-kvm
sudo adduser $USER kvm
sudo adduser $USER libvirtd
curl -LO https://storage.googleapis.com/kubernetes-release/release/$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)/bin/linux/amd64/kubectl
curl -Lo minikube https://storage.googleapis.com/minikube/releases/v0.19.0/minikube-linux-amd64
curl -L https://github.com/docker/machine/releases/download/v0.11.0/docker-machine-`uname -s`-`uname -m`
curl -L https://github.com/dhiltgen/docker-machine-kvm/releases/download/v0.10.0/docker-machine-driver-kvm-ubuntu14.04
chmod +x ./kubectl minikube docker-machine docker-machine-driver-kvm
sudo mv ./kubectl /usr/local/bin/kubectl
sudo mv minikube /usr/local/bin/minikube
sudo mv docker-machine /usr/local/bin/docker-machine
sudo mv docker-machine-driver-kvm /usr/local/bin/docker-machine-driver-kvm
cd ../
rm -rf temp
kubectl cluster-info
# edit the /etc/environement to include usr/local/bin in your PATH=""
# (arguments are seperated with ":") but it does by default. If it didn't
# then once you've edited and saved remember to run :
# source /etc/environment
docker-machine create -d kvm myengine0
minikube --vm-driver=kvm start
And this is despite being on the wrong OS. I'm on Mint 18 but it worked anyways.
edits and suggestions welcome.
EMULATING on an EMULATED machine (as I understand it this isn't possible) :
W.I.P. help and edits welcome.
Actual Kubernetes INSTALL on a LOCAL or EMULATED machine :
W.I.P. help and edits welcome.
As I understand it :
sudo apt-add-repository -y ppa:juju/stable
sudo apt update && sudo apt install snapd juju-local # or juju or juju-2.0
# I don't know which is cleaner/more functinal.
# Addapt as needed :
juju add-credential aws
# enter credetial, select userpass, enter username, enter password
juju update-clouds
juju bootstrap aws/us-east-2
juju deploy canonical-kubernetes
sudo snap install conjure-up --classic
then once in snap :
conjure-up kubernete
Best Answer
Your only real option is a matter of order:
If you start and open the VirtualBox machine, wait for it to finish booting and then start the KVM machine (from virt-manager or virsh) it should work correctly. Booting the machines in the opposite order will not work.
Loading and unloading the
kvm
andkvm_intel
modules will satisfy VirtualBox's requirements. A smoother, script-based method for this can be found here.EDIT: this solution (boot order) no longer seems to work for me, since upgrading to Ubuntu 13.10. YMMV.