Vertual machine could not start

Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed.
Detected OS with VirtualBox support
Initializing console…
Checking for OpenSSH Client at C:\WINDOWS\system32\OpenSSH\ssh.exe
OpenSSH check passed
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
No default docker-machine, good!
Error checking TLS connection: Host is not running
Docker is not communicating properly. We’ll attempt to establish communication…
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
webodm - virtualbox Stopped Unknown
WebODM VM exists, attempting to launch it…
Starting “webodm”…
(webodm) Check network to re-create if needed…
(webodm) Windows might ask for the permission to configure a dhcp server. Sometimes, such confirmation window is minimized in the taskbar.
Unable to start the VM: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe startvm webodm --type headless failed:
VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
Details: 00:00:01.118064 Power up failed (vrc=VERR_VMX_NO_VMX, rc=E_FAIL (0X80004005))
Could not start virtual machine. Check the console for error messages and attempt to fix the problems manually, then restart this application.

COULD NOT START VERTUAL MACHINE
INITIALISATION FAILED

1 Like
  1. Check that the VT-X feature is enabled from the BIOS.
  2. Check that Hyper-V is disabled.
1 Like

This is a non-issue on the latest VirtualBox (6.x and newer), as it can now co-exist with Hyper-V.

Update your VirtualBox, if you can afford to.

As an aside, the fundraising here goes towards an effort to have a WSL2 image, so virtualization won’t be needed:

2 Likes