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

VirtualBox/Hyper-V conflict: WHvSetupPartition failed - VERR_NEM_VM_CREATE_FAILED #4587

Open
Booooooger opened this issue Jun 25, 2019 · 52 comments

Comments

@Booooooger
Copy link

@Booooooger Booooooger commented Jun 25, 2019

  • 执行命令
    minikube start --memory 1024 --cpus 1 --disk-size 40GB --vm-driver virtualbox --bootstrapper=kubeadm

  • 控制台输出

minikube v1.2.0 on windows (amd64) Creating virtualbox VM (CPUs=1, Memory=1024MB, Disk=40000MB) ...
E0625 18:36:59.036469 1740 start.go:559] StartHost: create: creating: Unable to start the VM: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe startvm minikube --type headless failed: VBoxManage.exe: error: Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED) VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole Details: 00:00:00.855203 Power up failed (vrc=VERR_NEM_VM_CREATE_FAILED, rc=E_FAIL (0X80004005)) X Unable to start VM: create: creating: Unable to start the VM: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe startvm minikube --type headless failed: VBoxManage.exe: error: Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED) VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole Details: 00:00:00.855203 Power up failed (vrc=VERR_NEM_VM_CREATE_FAILED, rc=E_FAIL (0X80004005))**:

  • 日志输出
    getting ssh client for bootstrapper: Error dialing tcp via ssh client: dial tcp 127.0.0.1:22: connectex: No connection could be made because the target machine actively refused it

  • 操作系统信息
    Win10 家庭中文版

@Booooooger Booooooger added the l/zh-CN label Jun 25, 2019
@tstromberg tstromberg changed the title minikube 不能使用VirtualBox启动 vbox: Call to WHvSetupPartition failed: ERROR_SUCCESS (VERR_NEM_VM_CREATE_FAILED) Jun 25, 2019
@tstromberg

This comment has been minimized.

Copy link
Contributor

@tstromberg tstromberg commented Jun 25, 2019

This appears to be due to VirtualBox attempting to use HyperV as a backend, but failing for some reason: https://forums.virtualbox.org/viewtopic.php?f=6&t=92260

I had no idea that this was even possible with HyperV. I wonder if anyone else has gotten this configuration to work?

@tstromberg

This comment has been minimized.

Copy link
Contributor

@tstromberg tstromberg commented Jun 25, 2019

你使用的是什么版本的virtualbox?

@Booooooger Booooooger closed this Jun 27, 2019
@0rtem

This comment has been minimized.

@versusversus

This comment has been minimized.

Copy link

@versusversus versusversus commented Jul 14, 2019

RUN > CMD > bcdedit /set hypervisorlaunchtype off
then reboot host machine.

@AdamSEY

This comment has been minimized.

Copy link

@AdamSEY AdamSEY commented Jul 16, 2019

bcdedit /set hypervisorlaunchtype off works for me

@zhangzhuow

This comment has been minimized.

Copy link

@zhangzhuow zhangzhuow commented Jul 18, 2019

RUN > CMD > bcdedit /set hypervisorlaunchtype off
then reboot host machine.

果然关闭hyper-v就可以了 不是说virtualBox6.0+可以直接运行的吗

@rickgode

This comment has been minimized.

Copy link

@rickgode rickgode commented Jul 24, 2019

bcdedit /set hypervisorlaunchtype off works for me

This worked for me as well!

Ricky

@kindkid4

This comment has been minimized.

Copy link

@kindkid4 kindkid4 commented Jul 25, 2019

RUN > CMD > bcdedit /set hypervisorlaunchtype off
then reboot host machine.

Thx a lot,it fixed everything!

@CristianTrejo

This comment has been minimized.

Copy link

@CristianTrejo CristianTrejo commented Jul 25, 2019

RUN > CMD > bcdedit /set hypervisorlaunchtype off
then reboot host machine.

This worked for me.
Thanks!

@SLKTH

This comment has been minimized.

Copy link

@SLKTH SLKTH commented Jul 28, 2019

RUN > CMD > bcdedit /set hypervisorlaunchtype off
then reboot host machine.

This works.

@georgeraveen

This comment has been minimized.

Copy link

@georgeraveen georgeraveen commented Aug 3, 2019

RUN > CMD > bcdedit /set hypervisorlaunchtype off
then reboot host machine.

This works. thanks a lot

@medyagh medyagh reopened this Aug 3, 2019
@medyagh

This comment has been minimized.

Copy link
Member

@medyagh medyagh commented Aug 3, 2019

now that there is a solution ! I suggest this be added to the solution message !

@dubiZA

This comment has been minimized.

Copy link

@dubiZA dubiZA commented Aug 3, 2019

RUN > CMD > bcdedit /set hypervisorlaunchtype off
then reboot host machine.

Anyone using WSL2 after running this commmand? Does WSL2 still work?

@Enoxime

This comment has been minimized.

Copy link

@Enoxime Enoxime commented Aug 4, 2019

Anyone using WSL2 after running this commmand? Does WSL2 still work?

Works for me with Ubuntu even when installing Debian.

@rlabrecque

This comment has been minimized.

Copy link

@rlabrecque rlabrecque commented Aug 11, 2019

WSL2 doesn't seem to work for me anymore after doing so. :/

@thinszx

This comment has been minimized.

Copy link

@thinszx thinszx commented Aug 11, 2019

WSL2 doesn't seem to work for me anymore after doing so. :/

WSL 2 is now using virtualization technology (based on Hyper-V) so it won't work as well after shutting down hyper-v support😟

@bhavanikp84

This comment has been minimized.

Copy link

@bhavanikp84 bhavanikp84 commented Aug 11, 2019

RUN > CMD > bcdedit /set hypervisorlaunchtype off
then reboot host machine.

This works.

Thanks, This worked!!

@FrozenBeard

This comment has been minimized.

Copy link

@FrozenBeard FrozenBeard commented Aug 16, 2019

RUN > CMD > bcdedit /set hypervisorlaunchtype off
then reboot host machine.

Thanks this worked!

@heiniovason

This comment has been minimized.

Copy link

@heiniovason heiniovason commented Aug 19, 2019

Even though I deactivated Hyper-v in "Turn on/off windows features" I still had to run "bcdedit /set hypervisorlaunchtype off" in CMD. Thank god I found this discussion, or I'd have to setup my dev env all over again ...

@tstromberg tstromberg changed the title vbox: Call to WHvSetupPartition failed: ERROR_SUCCESS (VERR_NEM_VM_CREATE_FAILED) vbox: WHvSetupPartition failed: ERROR_SUCCESS (VERR_NEM_VM_CREATE_FAILED) (Hyper-V conflict) Aug 20, 2019
@TheDarkestPlays

This comment has been minimized.

Copy link

@TheDarkestPlays TheDarkestPlays commented Aug 22, 2019

So, when I put in the bcdedit /set hypervisorlaunchtype off thing, I get "The boot configuration data store could not be opened.
Access is denied."

@tstromberg tstromberg changed the title vbox: WHvSetupPartition failed: ERROR_SUCCESS (VERR_NEM_VM_CREATE_FAILED) (Hyper-V conflict) VirtualBox/Hyper-V conflict: WHvSetupPartition failed - VERR_NEM_VM_CREATE_FAILED Sep 20, 2019
@shvi0888

This comment has been minimized.

Copy link

@shvi0888 shvi0888 commented Sep 21, 2019

RUN > CMD > bcdedit /set hypervisorlaunchtype off
then reboot host machine.

Thanks works for me!!

@inigopascall

This comment has been minimized.

Copy link

@inigopascall inigopascall commented Sep 26, 2019

In my case this was because I had Windows Sandbox enabled. Disabling this in 'Turn Windows features on or off' and restarting my machine solved the issue.

@Stanley-Yao

This comment has been minimized.

Copy link

@Stanley-Yao Stanley-Yao commented Sep 29, 2019

RUN > CMD > bcdedit /set hypervisorlaunchtype off
then reboot host machine.

Thank god,it wooooorks for me, what happened here?

@ericjhl

This comment has been minimized.

Copy link

@ericjhl ericjhl commented Sep 30, 2019

RUN > CMD > bcdedit /set hypervisorlaunchtype off
then reboot host machine.

Thanks a lot, it works for me.

@kalhua

This comment has been minimized.

Copy link

@kalhua kalhua commented Sep 30, 2019

The bcedit thing did not work for me. Actually it was due to the core isolation security.
I disabled it and Virtualbox now works like a charm.

Windows Defender Security Center> Device Security> Core isolation > Memory integrity : off

https://forums.virtualbox.org/viewtopic.php?p=417512&sid=dab40dbc19d96086d6009ffae8554b92#p417512

@diegolsr

This comment has been minimized.

Copy link

@diegolsr diegolsr commented Oct 5, 2019

RUN > CMD > bcdedit /set hypervisorlaunchtype off
then reboot host machine.

This worked for me.
Thanks!

@sensesnet

This comment has been minimized.

Copy link

@sensesnet sensesnet commented Oct 9, 2019

Thank you so much!!!!

@messy80

This comment has been minimized.

Copy link

@messy80 messy80 commented Oct 15, 2019

CMD > bcdedit /set hypervisorlaunchtype off

did NOT work for me :( (it def ran successfully).

I have Windows 10 enterprise, 1903, build 18362.418

In windows features there is nothing even remotely related to VM's enabled yet i still get;

Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED).
Result Code: | E_FAIL (0x80004005)
-- | --
Component: | ConsoleWrap
Interface: | IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Please help!

@pawankaushal

This comment has been minimized.

Copy link

@pawankaushal pawankaushal commented Oct 23, 2019

running the VirtualBox installation again in repair mode will fix it again. I had success results with VirtualBox 6.

@messy80

This comment has been minimized.

Copy link

@messy80 messy80 commented Oct 24, 2019

running the VirtualBox installation again in repair mode will fix it again. I had success results with VirtualBox 6.

that worked thanks!

@MiguelAtTweddle

This comment has been minimized.

Copy link

@MiguelAtTweddle MiguelAtTweddle commented Oct 28, 2019

What worked for me:
I uninstalled the hyperV feature first and rebooted. Then I noticed the 'Call to WHvSetupPartition failed'.
On reboot; I disabled everything in BIOS concerning Virtualization, but on startup windows 10 froze.
Hard shutdown and enabled the Virtualization back on again in BIOS.
After startup I could install a linux OS in VMBox.

@MiguelAtTweddle

This comment has been minimized.

Copy link

@MiguelAtTweddle MiguelAtTweddle commented Oct 28, 2019

What worked for me:
I uninstalled the hyperV feature first and rebooted. Then I noticed the 'Call to WHvSetupPartition failed'.
On reboot; I disabled everything in BIOS concerning Virtualization, but on startup windows 10 froze.
Hard shutdown and enabled the Virtualization back on again in BIOS.
After startup I could install a linux OS in VMBox.
I wouldn't recommend on using hyperV to anyone, because it has some stupid limitations I didn't know about.

@devlimon

This comment has been minimized.

Copy link

@devlimon devlimon commented Nov 1, 2019

RUN > CMD > bcdedit /set hypervisorlaunchtype off
then reboot host machine.

it solved my windows 10 problem

@stimpy77

This comment has been minimized.

Copy link

@stimpy77 stimpy77 commented Nov 3, 2019

There are a ton of people saying regarding disabling Hyper-V #MeToo "that worked" "fixed it" "this is the solution" etc. This is a lot of unnecessary spam.

But the incompatibility of Hyper-V is an ongoing issue. The fact that VirtualBox recently began supporting creating and running VMs while Hyper-V is enabled should clue all of you in that this is a fixable problem, and they haven't gotten this far yet.

As such, turning off Hyper-V is not a solution. It is a workaround, and apparently the only option available for now, since the solution is outside of the scope of kubernetes / minkube but rather between Microsoft and Oracle (Windows Hyper-V and VirtualBox).

@Vizionz

This comment has been minimized.

Copy link

@Vizionz Vizionz commented Nov 13, 2019

The solution of executing in CMD (Admin) bcdedit /set hypervisorlaunchtype off did not help me.

But after reading @tag's response, I decided to do the following steps that got me running VB VMs

  1. CMD (Admin) > bcdedit /deletevalue hypervisorlaunchtype
  2. Uninstall Docker
  3. Windows Feature > Disable 'Containers'
  4. Windows Feature > Disable 'Hyper-V'
  5. Restart
  6. Attempt to start VB VMs.
@nakulvr

This comment has been minimized.

Copy link

@nakulvr nakulvr commented Nov 13, 2019

As per the Virtualbox changelog (VirtualBox 6.0.0 onwards): Added support for using Hyper-V as the fallback execution core on Windows host, to avoid inability to run VMs at the price of reduced performance
https://www.virtualbox.org/wiki/Changelog-6.0

And looking at the official documentation: Oracle VM VirtualBox can be used on a Windows host where Hyper-V is running. This is an experimental feature.
No configuration is required. Oracle VM VirtualBox detects Hyper-V automatically and uses Hyper-V as the virtualization engine for the host system. The CPU icon in the VM window status bar indicates that Hyper-V is being used.

https://docs.oracle.com/cd/E97728_01/F12469/html/hyperv-support.html

Has anyone had success booting a VM in VirtualBox which internally uses Hyper-V as virtualization engine?

@zaw-moe-htike

This comment has been minimized.

Copy link

@zaw-moe-htike zaw-moe-htike commented Dec 6, 2019

It work for me
RUN > CMD > bcdedit /set hypervisorlaunchtype off
then reboot host machine.

@UbaidurRehman1

This comment has been minimized.

Copy link

@UbaidurRehman1 UbaidurRehman1 commented Dec 8, 2019

RUN > CMD > bcdedit /set hypervisorlaunchtype off
then reboot host machine.

Its work

@broomerr

This comment has been minimized.

Copy link

@broomerr broomerr commented Dec 18, 2019

You could run VirtualBox on top of Hyper-V.
But some additional actions needed.

  1. need to enable "Windows Hypervisor Platform" in OptionalFeatures.exe
  2. set "VBoxInternal/NEM/UseRing0Runloop" for virtual machine. See here how:
    https://superuser.com/questions/1480214/virtualbox-6-doesnt-run-with-hyper-v-enabled-on-windows-10-1903

But seams minikube not able to create new VM!
Only reuse.

@avinal

This comment has been minimized.

Copy link

@avinal avinal commented Dec 19, 2019

bcdedit /set hypervisorlaunchtype off works for me. Thanks 👍

@9ofe

This comment has been minimized.

Copy link

@9ofe 9ofe commented Dec 19, 2019

RUN > CMD > bcdedit /set hypervisorlaunchtype off
then reboot host machine.
did not work for me :((
C:\WINDOWS\system32>bcdedit /set hypervisorlaunchtype off
The boot configuration data store could not be opened.
The system cannot find the file specified.

@semiautomatix

This comment has been minimized.

Copy link

@semiautomatix semiautomatix commented Dec 20, 2019

Thanks for the help all.

//Disable hyper-V in Powershell
PS> Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All

//This has to also be set!
RUN > CMD > bcdedit /set hypervisorlaunchtype off

Reboot.

Edit: don't know why the thumbs down. I just had to do it again now after a Windows update. And again it worked.

And yes, run as administrator - always run system changes as administrator!

@TahseenAlaa

This comment has been minimized.

Copy link

@TahseenAlaa TahseenAlaa commented Jan 9, 2020

RUN> CMD> Right Click> Run as Administrator> bcdedit /set hypervisorlaunchtype off

then reboot host machine.

@andrew-curtis

This comment has been minimized.

Copy link

@andrew-curtis andrew-curtis commented Jan 10, 2020

RUN > CMD > bcdedit /set hypervisorlaunchtype off
then reboot host machine.

worked for me too!

@noobencoder

This comment has been minimized.

Copy link

@noobencoder noobencoder commented Jan 11, 2020

RUN > CMD > bcdedit /set hypervisorlaunchtype off
then reboot host machine.

it worked Thanks!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
You can’t perform that action at this time.