Ubuntu18.04 NS_ERROR_FAILURE

[wendaotao]

Failed to open a session for the virtual machine ss.

The virtual machine 'ss' has terminated unexpectedly during startup because of signal 6.

Result Code: NS_ERROR_FAILURE (0x80004005) Component: MachineWrap Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}

[wendaotao]

$ dpkg -l | grep virtualbox
rc virtualbox 5.2.32-dfsg-0~ubuntu18.04.1 amd64 x86 virtualization solution - base binaries
ii virtualbox-6.0 6.0.14-133895~Ubuntu~bionic amd64 Oracle VM VirtualBox
rc virtualbox-qt 5.2.32-dfsg-0~ubuntu18.04.1 amd64 x86 virtualization solution - Qt based user interface
$ uname -a
Linux lt-HP-Z440-Workstation 5.0.0-36-generic #39~18.04.1-Ubuntu SMP Tue Nov 12 11:09:50 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

[Socratis]

You didn't specify the VM name when you run the "VBoxBugReport" tool, as in:

VBoxBugReport "ss"

So, if you could run the "VBoxBugReport" tool again properly, and replace what you already have as an attachment, that would be better.

And could you also edit your comment:1 and include the Terminal output between {{{ and }}} tags? It comes out as you intended it to...

Finally, it's usually better and faster, if issues get first addressed in the ​VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved in the forums, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of.

Plus a discussion and analysis on the bug tracker is going to help me, is going to help you, and potentially a future drive-by user or two. Not so in the forums, many more tend to benefit.

So, please open a new thread in the ​VirtualBox on Linux Hosts section of the forums. Please be sure to mention that you came from the bug tracker and include the ticket number.

[wendaotao]

$ VBoxBugReport "ss"
Oracle VM VirtualBox Bug Report Tool 6.0.14
(C) 2019 Oracle Corporation
All rights reserved.

ERROR: Failed to open directory '/home/lt/VirtualBox VMs/ss/Logs/VBox.log*'

Thanks for reply, I will issue this to forums.

[Socratis]

Any idea why you can't even read your own home directory? Actually its sub-directories...

What does the output of the following command show?

ls -alR "/home/lt/VirtualBox VMs/ss/"

But actually it's better if we continue on the forums... ;)

[Socratis]

Replying to wendaotao:

Thanks for reply, I will issue this to forums.

Have you opened a thread in the forums? Because I can't seem to find it. If you did, can you post the link?

[Cacilhas]

I got the very same error NS_ERROR_FAILURE (0x80004005), but with different versions:

$ uname -r
5.3.0-40-generic
$ dpkg -l | ag virtualbox
ii  virtualbox-6.1                                              6.1.4-136177~Ubuntu~bionic                                  amd64        Oracle VM VirtualBox

I created the first virtual machine. When I try to run it for installing the system, I got:

$ vboxmanage startvm 'CentOS 6'
Waiting for VM "CentOS 6" to power on...
VBoxManage: error: The virtual machine 'CentOS 6' has terminated unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine

I’ve seen a lot of fora, searching for that error code, but it seems to be a general code, ’cause I’ve found quite different issues and causes.

It’s not a corner case, but something is happening around indeed.

[aeichner]

Can you please provide the VBox.log of the affected VM?

[FeelTech]

I am also getting the same error while starting VM

==> default: Booting VM... There was an error while executing VBoxManage, a CLI used by Vagrant for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "2967aab1-2950-4da7-aa86-2e6e8efce9b3", "--type", "headless"]

Stderr: VBoxManage: error: The virtual machine 'docker_default_1619593058883_17000' has terminated unexpectedly during startup with exit code 1 (0x1) VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine