VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (418 - 420 of 16363)

Ticket Resolution Summary Owner Reporter
#20358 duplicate VM launch fail on Windows 10 when WSL2 and Docker is enabled Janis Baumanis
Description

We are using Docker containers and Vagrant + VirtualBox virtual machines in Windows 10 (now 20H2). Would be very convenient to make both parties (Docker+WSL2 and VirtualBox) working together on same machine. However when Docker Desktop with WSL2 support is installed, existing VirtualBox virtual machines (Linux 64-bit quests with installed VirtualBox Guest additions) fail to launch. Instead error message appear:

WHvCapabilityCodeHypervisorPresent is FALSE! Make sure you have enabled the 'Windows Hypervisor Platform' feature. (VERR_NEM_NOT_AVAILABLE). VT-x is not available (VERR_VMX_NO_VMX).

"Windows Hypervisor Platform" feature enabling in Windows features does not change anything. It is not possible to change paravirtualization interface type under VM "Settings - System - Acceleration" too - OK button remain disabled.

To get VirtualBox VMs running again either "hypervisorlaunchtype" must be disabled through Windows Command Prompt with command

bcdedit /set hypervisorlaunchtype off

or Docker Desktop must be uninstalled together with "Windows Hypervisor Platform", "Virtual Machine Platform" and "Windows Subsystem for Linux" feature disabling in Windows Features with subsequential Windows restart. Both actions obviously permit Docker container using together with VirtualBox. Are there is another way how to use VirtualBox 64-bit VMs in Windows host together with WSL2 + Docker installed in same Windows host?

I seen Hyper-V virtualization support appearing in VirtualBox changelog starting from version 6.1.18 with Hyper-V related fixes in 6.1.22. However it does not help for us. Didn't found any useful information about how to run Docker+WSL2 and VirtualBox together in Internet either.

Environment info:

Host: Windows 10 20H2, 64-bit
Guests: Ubuntu Linux 18.04 LTS, 64-bit
Hardware: Dell OptiPlex 980, Intel Core i5-750 CPU (has VT-x support), 16 GB RAM
Dell BIOS, version A18, VT-x is enabled
#20350 duplicate I can't open virtualbox, it answers me this error. thanks for your help zmotronick
Description

Fallo al adquirir el objeto VirtualBox COM.

La aplicación terminará ahora.

Document is empty.

Location: '/Users/carlosmartinezosuna/Library/VirtualBox/VirtualBox.xml', line 1 (0), column 1.

/Users/vbox/tinderbox/6.1-mac-rel/src/VBox/Main/src-server/VirtualBoxImpl.cpp[740] (nsresult VirtualBox::init()).

Código resultado: NS_ERROR_FAILURE (0x80004005) Componente: VirtualBoxWrap Interfaz: IVirtualBox {d0a0163f-e254-4e5b-a1f2-011cf991c38d} Receptor: IVirtualBoxClient {d2937a8e-cb8d-4382-90ba-b7da78a74573}

#20349 invalid I can't open virtualbox, it answers me this error. thanks for your help zmotronick
Description

Fallo al adquirir el objeto VirtualBox COM.

La aplicación terminará ahora.

Document is empty.

Location: '/Users/carlosmartinezosuna/Library/VirtualBox/VirtualBox.xml', line 1 (0), column 1.

/Users/vbox/tinderbox/6.1-mac-rel/src/VBox/Main/src-server/VirtualBoxImpl.cpp[740] (nsresult VirtualBox::init()).

Código resultado: NS_ERROR_FAILURE (0x80004005) Componente: VirtualBoxWrap Interfaz: IVirtualBox {d0a0163f-e254-4e5b-a1f2-011cf991c38d} Receptor: IVirtualBoxClient {d2937a8e-cb8d-4382-90ba-b7da78a74573}

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy