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.

Sign up for GitHub

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

Jump to bottom

Improve error handling for "VirtualBox won't boot a 64bits VM when Hyper-V is activated" #4051

Closed
Dhiraj0007 opened this issue Apr 4, 2019 · 16 comments · Fixed by #4112
Closed

Improve error handling for "VirtualBox won't boot a 64bits VM when Hyper-V is activated" #4051

Dhiraj0007 opened this issue Apr 4, 2019 · 16 comments · Fixed by #4112
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@Dhiraj0007
Copy link

Shows the error bellow:
! Unable to start VM: create: precreate: This computer is running Hyper-V. VirtualBox won't boot a 64bits VM when Hyper-V is activated. Either use Hyper-V as a driver, or disable the Hyper-V hypervisor. (To skip this check, use --virtualbox-no-vtx-check)
@tstromberg tstromberg added the needs-solution-message Issues where where offering a solution for an error would be helpful label Apr 4, 2019
@tstromberg tstromberg changed the title Minicube crashed Add solution message for "This computer is running Hyper-V. VirtualBox won't boot a 64bits VM when Hyper-V is activated" Apr 4, 2019
@tstromberg tstromberg added good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. labels Apr 4, 2019
@tstromberg tstromberg changed the title Add solution message for "This computer is running Hyper-V. VirtualBox won't boot a 64bits VM when Hyper-V is activated" Improve error handling for "VirtualBox won't boot a 64bits VM when Hyper-V is activated" Apr 4, 2019
@tstromberg tstromberg added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Apr 4, 2019
@RA489
Copy link

RA489 commented Apr 10, 2019 •
edited
Loading

@Dhiraj0007 IIUC are you using virtualbox to create the VM when Hyper-V is activated?

@Dhiraj0007
Copy link
Author

Yes

@RA489
Copy link

RA489 commented Apr 10, 2019 •
edited
Loading

@Dhiraj0007 Only one hypervisor can run at a time, and since Hyper-V runs all the time as it is enabled virtualbox won't boot a 64bits VM. The workaround is to disable Hyper-V when you want to run VirtualBox.

@RA489
Copy link

RA489 commented Apr 10, 2019 •
edited
Loading

@Dhiraj0007 try this workaround and lets see this works for you or not?

This was referenced Apr 18, 2019
Closed
Merged
@tstromberg tstromberg removed the needs-solution-message Issues where where offering a solution for an error would be helpful label May 14, 2019
@tstromberg tstromberg reopened this May 14, 2019
@snip300r
Copy link

snip300r commented Jul 3, 2019

Did we find any solution for this problem?

@ivankatashkova ivankatashkova mentioned this issue Jul 17, 2019
Closed
@aningoo
Copy link

aningoo commented Aug 1, 2019 •
edited
Loading

When you want to use Hyper-V instead of the default vBox.

  1. run CMD as admin

  2. "minikube start --vm-driver hyperv"

  3. optional, you might need this:
    https://docs.docker.com/machine/drivers/hyper-v/

@KnutRyagerInmeta
Copy link

I was able to deactivate hyper-V. However, now I get an error message from Docker that it requires Hyper-V to work properly, and minikube start just stops at Preparing Kubernetes v1.15.2 on Docker 18.09.8 ... indefinitely. My understanding is that running Docker containers is the main purpose of Kubernetes? Confused.

@yekolla yekolla mentioned this issue Dec 12, 2019
Closed
@codepractisedemo
Copy link

I am also facing the similar problem , when you disable the deactivate hyper-V and it wont able to connect the virtual box itself. since i have download the latest version

@lukasmrtvy
Copy link

@tstromberg Latest VirtualBox 6.1.16 can run 64bits VM with Hyper-V backend

@panktrip
Copy link

I am running virtualbox 6.1.32 on windows-10. but I still see the above reported issue.

PS C:> minikube start --driver=virtualbox

  • minikube v1.25.1 on Microsoft Windows 10 Enterprise 10.0.19044 Build 19044
  • Using the virtualbox driver based on user configuration
  • Starting control plane node minikube in cluster minikube
  • Creating virtualbox VM (CPUs=2, Memory=4000MB, Disk=20000MB) ...
    ! StartHost failed, but will try again: creating host: create: precreate: This computer is running Hyper-V. VirtualBox won't boot a 64bits VM when Hyper-V is activated. Either use Hyper-V as a driver, or disable the Hyper-V hypervisor. (To skip this check, use --virtualbox-no-vtx-check)
  • Creating virtualbox VM (CPUs=2, Memory=4000MB, Disk=20000MB) ...
  • Failed to start virtualbox VM. Running "minikube delete" may fix it: creating host: create: precreate: This computer is running Hyper-V. VirtualBox won't boot a 64bits VM when Hyper-V is activated. Either use Hyper-V as a driver, or disable the Hyper-V hypervisor. (To skip this check, use --virtualbox-no-vtx-check)

X Exiting due to PR_VBOX_HYPERV_64_BOOT: Failed to start host: creating host: create: precreate: This computer is running Hyper-V. VirtualBox won't boot a 64bits VM when Hyper-V is activated. Either use Hyper-V as a driver, or disable the Hyper-V hypervisor. (To skip this check, use --virtualbox-no-vtx-check)

@panktrip
Copy link

when I disable the check, as suggested in the error message above, I do get other error as shown below.

PS C:\WINDOWS\system32> minikube start --driver=virtualbox --no-vtx-check=true

  • minikube v1.25.1 on Microsoft Windows 10 Enterprise 10.0.19044 Build 19044
  • Using the virtualbox driver based on existing profile
  • Starting control plane node minikube in cluster minikube
  • Creating virtualbox VM (CPUs=2, Memory=4000MB, Disk=20000MB) ...
  • Deleting "minikube" in virtualbox ...
    ! StartHost failed, but will try again: creating host: create: creating: Unable to start the VM: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe startvm minikube --type headless failed:
    VBoxManage.exe: error: Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND).
    VBoxManage.exe: error: Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND)
    VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole

Details: 00:00:02.438665 Power up failed (vrc=VERR_INTNET_FLT_IF_NOT_FOUND, rc=E_FAIL (0X80004005))

  • Failed to start virtualbox VM. Running "minikube delete" may fix it: Error loading existing host. Please try running [minikube delete], then run [minikube start] again.: filestore "minikube": open C:\Users\tripathip.minikube\machines\minikube\config.json: The system cannot find the file specified.

X Exiting due to GUEST_NOT_FOUND: Failed to start host: Error loading existing host. Please try running [minikube delete], then run [minikube start] again.: filestore "minikube": open C:\Users\tripathip.minikube\machines\minikube\config.json: The system cannot find the file specified.

@Jonaz1982
Copy link

$ minikube start --vm-driver kvm2

  • minikube v1.25.2 en Microsoft Windows 10 Pro 10.0.19044 Build 19044
  • Using the virtualbox driver based on existing profile
  • Starting control plane node minikube in cluster minikube
  • Creando virtualbox VM (CPUs=2, Memory=6000MB, Disk=20000MB) ...
    ! StartHost failed, but will try again: creating host: create: precreate: This c
    omputer is running Hyper-V. VirtualBox won't boot a 64bits VM when Hyper-V is ac
    tivated. Either use Hyper-V as a driver, or disable the Hyper-V hypervisor. (To
    skip this check, use --virtualbox-no-vtx-check)
  • Creando virtualbox VM (CPUs=2, Memory=6000MB, Disk=20000MB) ...
  • Failed to start virtualbox VM. Running "minikube delete" may fix it: creating
    host: create: precreate: This computer is running Hyper-V. VirtualBox won't boot
    a 64bits VM when Hyper-V is activated. Either use Hyper-V as a driver, or disab
    le the Hyper-V hypervisor. (To skip this check, use --virtualbox-no-vtx-check)

X Saliendo por un error PR_VBOX_HYPERV_64_BOOT: Failed to start host: creating h
ost: create: precreate: This computer is running Hyper-V. VirtualBox won't boot
a 64bits VM when Hyper-V is activated. Either use Hyper-V as a driver, or disabl
e the Hyper-V hypervisor. (To skip this check, use --virtualbox-no-vtx-check)

@krishnarayapudi25 krishnarayapudi25 mentioned this issue May 13, 2022
Closed
@veelash27 veelash27 mentioned this issue Jul 27, 2022
Closed
@akaikkhan
Copy link

Error-!

Exiting due to GUEST_DRIVER_MISMATCH: The existing "minikube" cluster was created using the "virtualbox" driver, which is incompatible with requested "hyperv" driver.

  • Suggestion: Delete the existing 'minikube' cluster using: 'minikube delete', or start the existing 'minikube' cluster using: 'minikube start --driver=virtualbox'

Solutions-

C:\Windows\system32>minikube delete (delete the existing minikube cluster)

  • Removed all traces of the "minikube" cluster.

C:\Windows\system32>minikube start --vm-driver hyperv (Use this command and you must have windows10 Pro OS)

  • minikube v1.30.1 on Microsoft Windows 10 Pro 10.0.19045.3086 Build 19045.3086
  • Using the hyperv driver based on user configuration
  • Starting control plane node minikube in cluster minikube
  • Creating hyperv VM (CPUs=2, Memory=2200MB, Disk=20000MB) ...
  • Preparing Kubernetes v1.26.3 on Docker 20.10.23 ...
    • Generating certificates and keys ...
    • Booting up control plane ...
    • Configuring RBAC rules ...
  • Configuring bridge CNI (Container Networking Interface) ...
  • Verifying Kubernetes components...
    • Using image gcr.io/k8s-minikube/storage-provisioner:v5
  • Enabled addons: storage-provisioner, default-storageclass
  • Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default

And please must check the virtual machine plateform checked off and hypervisor is turn on by going to turn on windows feature on or off.

@MecHCoDeR2023
Copy link

MecHCoDeR2023 commented Jan 5, 2024 •
edited
Loading

Hi, for me the issue has been solved by the following steps:

  1. Runs PowerShell as administrator.
  2. Specifies Hyper-V as the user driver
  3. Before creating any new minikube clusters delete any of the existing logs using the command "minikube delete"

#Result

C:\WINDOWS\system32> minikube start --driver=hyperv

  • minikube v1.32.0 on Microsoft Windows 10 Pro 10.0.19045.3803 Build 19045.3803
  • Using the hyperv driver based on user configuration
  • Starting control plane node minikube in cluster minikube
  • Creating hyperv VM (CPUs=2, Memory=2200MB, Disk=20000MB) ...
  • Preparing Kubernetes v1.28.3 on Docker 24.0.7 ...
    • Generating certificates and keys ...
    • Booting up control plane ...
    • Configuring RBAC rules ...
  • Configuring bridge CNI (Container Networking Interface) ...
  • Verifying Kubernetes components...
    • Using image gcr.io/k8s-minikube/storage-provisioner:v5
  • Enabled addons: storage-provisioner, default-storageclass
  • Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default

#OR

  1. Run bcdedit /set hypervisorlaunchtype off to disable Hyper-V temporarily.
  2. Started Minikube with the --driver=hyperv flag to use the Hyper-V driver.
  3. Resolved conflicts between VirtualBox and Hyper-V.

@jvscampos
Copy link

Oque funcionou para mim foi:

minikube delete --all

e depois

minikube start

dentro do PowerShell7

@nidhi102
Copy link

I am gtting below error,while trying to start the minikube,please help:
C:\Windows\system>minikube start --vm-driver hyperv

  • minikube v1.34.0 on Microsoft Windows 11 Pro 10.0.22000.2538 Build 22000.2538
    E1028 22:13:12.590832 1220 start.go:812] api.Load failed for minikube: filestore "minikube": Docker machine "minikube" does not exist. Use "docker-machine ls" to list machines. Use "docker-machine create" to add a new one.

! Exiting due to GUEST_DRIVER_MISMATCH: The existing "minikube" cluster was created using the "virtualbox" driver, which is incompatible with requested "hyperv" driver.

  • Suggestion: Delete the existing 'minikube' cluster using: 'minikube delete', or start the existing 'minikube' cluster using: 'minikube start --driver=virtualbox'

C:\Windows\system32>minikube status
E1028 22:13:27.139283 9852 status.go:263] The "minikube" host does not exist!
minikube
type: Control Plane
host: Nonexistent
kubelet: Nonexistent
apiserver: Nonexistent
kubeconfig: Nonexistent

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Milestone
No milestone