I tried to start a container with VirtualBox 6.0.8 on Windows 10.0.1709 with Hyper-V enabled. I finally gave into enabling Hyper-V because I need Kubernetes for work and it's just easier that way.
I got this error from VirtualBox:
Code: Select all
VirtualBox 6.0.8 HMR3Init: Attempting fall back to NEM:VT-x is not available [....]
NEMR3Init: Native init failed: VERR_NEM_MISSING_KERNEL_API.
After reading here that I need at least Windows version 10.0.1809
socratis wrote:
So, if you can't find the DLL and VirtualBox complains, there's a really valid reason; you're running an older version of Win10 that doesn't have that capability enabled. And mind you, that's the version (17083, pre-1803) that this was enabled. So you'll need Win10 1803 or 1809 to have it work properly. The newer the build, the better I expect it to be supported...
I now forced an upgrade to 10.0.18362.175.
Now when I start the virtual machine I get am prompted in multiple UAC elevated prompts and finally I get an error that is different from before Windows upgrade:
VERR_NEM_VM_CREATE_FAILED
Code: Select all
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}
Code: Select all
00:00:03.410098 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED)}, preserve=false aResultDetail=-6805
00:00:03.410877 Console: Machine state changed to 'PoweredOff'
00:00:03.461031 Power up failed (vrc=VERR_NEM_VM_CREATE_FAILED, rc=E_FAIL (0X80004005))
Moreover: it is really annoying that sometimes when I view the log files the VirtualBox application just terminates!!
Full logfile:
https://www.dropbox.com/s/bhy4lyje6qwmb ... 2.log?dl=1