VirtualBox on Windows 10 Host Version 10.0.18363.778 (1909 - 19H2)

[fdavidg]

I am running VirtualBox on a Windows 10 Host at version 10.0.18363 which is 1909 - 19h2

I have attached a zipped logfile and a png file of the Windows Features screen showing Hyper-V enabled and Virtual Machine Platform enabled and Windows Hypervisor Platform enabled.

No matter what I try I continue to get the following error:

docker-provider: Booting VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "b8d0a299-220a-4a52-b6c0-4c967ed980d5", "--type", "headless"]

Stderr: VBoxManage.exe: error: WHvCapabilityCodeHypervisorPresent is FALSE! Make sure you have enabled the 'Windows Hypervisor Platform' feature. (VERR_NEM_NOT_AVAILABLE).
VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole

I have trolled the Internet and this forum and tried numerous suggestions, but I can NOT get a VirtualBox VM running on this machine.

I would appreciate some clear suggestions on how to proceed!

Frank Gunseor

[scottgus1]

Hyper-V blocks or severely inhibits Virtualbox. The devs are working on it, but it is not an OK situation yet. For further info, see I have a 64bit host, but can't install 64bit guests and https://www.tenforums.com/tutorials/139 ... puter.html

Vagrant changes Virtualbox in ways we can't predict, so we don't support Vagrant-modified Virtualbox.

[fdavidg]

scottgus1,

I thought that VirtualBox-6.1.7 r137622 was suppose to be compatible with Hyper-V?????? Is this NOT the case? Am I wasting my time?

Actually, I get exactly the same errors running the VM WITHOUT the Vagrant-modified VirtualBox.

Frank Gunseor

[mpack]

Am I wasting my time?

Hmm. How does one answer that. I'm going to say... yes?

Actually, I get exactly the same errors running the VM WITHOUT the Vagrant-modified VirtualBox.

How is that relevant? You were told that Vagrant is not supported, not that Vagrant causes this error.