Ticket #12145 (closed defect: obsolete)

Opened 4 years ago

Last modified 11 months ago


Reported by: Mr_Inc Owned by:
Priority: major Component: VM control
Version: VirtualBox 4.2.18 Keywords: savestate headless
Cc: Guest type: Windows
Host type: Windows


I start and run the VM (Guest Windows Home Server v1) using VMBoxManage in headless mode. When I attempt to savestate using (either in a CMD file or direct in a command line) I get this error.

VBoxManage.exe: error: Failed to create the VirtualBox object! VBoxManage.exe: error: Code CO_E_SERVER_EXEC_FAILURE (0x80080005) - Server execution failed (extended info not available) VBoxManage.exe: error: Most likely, the VirtualBox COM server is not running or failed to start.

I can reproduce this 100%.

If I run the VM from the GUI, the savestate from command line works fine. As sson as the VM is launched headless, savestate won't work,

Change History

comment:1 Changed 4 years ago by Mr_Inc

Forgot to add: Host is Windows 7 64 Bit. 16GB Memory.

comment:2 Changed 4 years ago by Mr_Inc

Also forgot mention that the same error occurs should I try to start the GUI whilst a headless VM is running.

Failed to create the VirtualBox COM object.

The application will now terminate.

Callee RC: CO_E_SERVER_EXEC_FAILURE (0x80080005)

Last edited 4 years ago by Mr_Inc (previous) (diff)

comment:3 Changed 3 years ago by operator error

I have same issue. Running a headless VM as a Windows Service on startup by VBoxVmService, which is set to log on as Administrator. Windows 7 Ultimate x64 host, Windows Server 2003 guest. Headless VM starts fine, I can Remote Desktop into it. When attempting to start VirtualBox GUI however, same error message appears:

Failed to create the VirtualBox COM object.

The application will now terminate.

Callee RC: CO_E_SERVER_EXEC_FAILURE (0x80080005)

Very little software on host machine, building it to run VBox only. I already ran into software interference during this build tho, so hopefully if it's another application we can narrow that down quick.

Through more testing I see this error is 100% reproducible. If I change the VBoxVmService startup type from Automatic to Manual and reboot (so that the headless VM is no longer started), I can bring up the VirtualBox GUI fine. If I change the service startup type back to Automatic and reboot, same error occurs.

For me personally, this issue is not a high priority. I plan on running this host off-site, I want the headless VM to run as a service, and I don't really need VBox GUI for anything anymore anyway (I already have the VM setup the way I wanted).

Last edited 3 years ago by operator error (previous) (diff)

comment:4 Changed 11 months ago by aeichner

  • Status changed from new to closed
  • Resolution set to obsolete

Please reopen if still relevant with a recent VirtualBox release.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use