Opened 14 years ago
Last modified 7 years ago
#7367 closed defect
VBoxManage startvm command fails if no gui is available — at Version 3
| Reported by: | tuomas leikola | Owned by: | |
|---|---|---|---|
| Component: | VM control | Version: | VirtualBox 3.2.8 |
| Keywords: | NS_ERROR_FAILURE | Cc: | |
| Guest type: | other | Host type: | Solaris |
Description (last modified by )
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 (3)
comment:1 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:2 by , 12 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
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 by , 12 years ago
| 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.
Please reopen if still relevant with VBox 4.0.4.