VirtualBox

Ticket #7367 (reopened defect)

Opened 4 years ago

Last modified 15 months ago

VBoxManage startvm command fails if no gui is available

Reported by: stoxx Owned by:
Priority: minor Component: VM control
Version: VirtualBox 3.2.8 Keywords: NS_ERROR_FAILURE
Cc: Guest type: other
Host type: Solaris

Description (last modified by frank) (diff)

when no X environment is present (ssh shell, no gui started on host, etc), this error message is presented:

tobo@elena:~$ VBoxManage startvm 2ct2 Oracle VM VirtualBox Command Line Management Interface Version 3.2.8 (C) 2005-2010 Oracle Corporation All rights reserved.

Waiting for the VM to power on... ERROR: The virtual machine '2ct2' has terminated unexpectedly during startup with exit code 0 Details: code NS_ERROR_FAILURE (0x80004005), component Machine, interface IMachine, callee tobo@elena:~$

which is far from elegant. Correct behaviour would be to require --type vrdp or such.

this is opensolaris host 111b or such.

please contact me at my registered address if further info is necessary.

Change History

comment:1 Changed 3 years ago by frank

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

Please reopen if still relevant with VBox 4.0.4.

comment:2 Changed 2 years ago by gcc

  • Status changed from closed to reopened
  • Resolution fixed deleted

Still happens in 4.1.14.

This failure mode is really unclear. The logs don't appear to say anything useful. Not even a google search turns up that this error can be caused by failing to specify --type headless when starting the virtual machine.

comment:3 Changed 19 months ago by frank

  • Description modified (diff)

Well, the error message I get when I try this is VBoxManage: error: Could not launch a process for the machine 'debian' (VERR_FILE_NOT_FOUND) .... I understand that in case there is no GUI application installed, the default type could be headless but OTOH I hesitate to implement that because this could also mean an installation problem.

comment:4 Changed 15 months ago by scai

Problem still exists:

$ VBoxManage --version
4.2.6r82870
$ VBoxManage startvm "Build Server"
Waiting for VM "Build Server" to power on...
VBoxManage: error: The virtual machine 'Build Server' has terminated unexpectedly during startup with exit code 0
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component Machine, interface IMachine
$ VBoxManage startvm "Build Server" --type headless
Waiting for VM "Build Server" to power on...
VM "Build Server" has been successfully started.

I suggest adding a clearer error message.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use