virtualbox.org

Hi all,

I get this error message when I start the VM:

---
Failed to open a session for the virtual machine Name.

The virtual machine 'Name' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'M:\VirtualBox VMs\Name\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {93859c64-b5bc-4218-a960-4em27c3513dk}
---

Please, how to fix it?

Thanks,

Please zip and post that log file, using the forum's Upload Attachment tab.

Also see Diagnosing VirtualBox Hardening Issues

Thanks for your reply,
here is the VBoxHardening.log file

I'm afraid this one puzzles me. The posted log has an exit code of 0. It should have been 1 according to the posted error message. When the hardening exit code is 0 as logged, there wouldn't be a hardening error message and the VM would start.

Hi @scottgus1, Hi all,

What's the solution to access VMs,
Thanks,

Is the error message still the same as in the first post? The attached log had a different exit code saying there was no error.

scottgus1 wrote:Is the error message still the same as in the first post? The attached log had a different exit code saying there was no error.

Yes it was.
Try using the other start option, that appear from the falling menu.

Please try the following:

1. Open a Windows Command Prompt and start the VM with the following commands:
Check if the command output exhibits more detailed error messages and post them.

2. Compare the current wall clock time to the date and time of the VBoxHardening.log and VBox.log files to check if they were created at all, and if so, post a zip file containing them.

3. Post a zip file containing the contents of the C:\Users\<username>\.VirtualBox folder (note the ".").

Hi All,

Thank you for your replies.

---
I successfully accessed the VM by choosing the "Deatachable Start" option. But, every time I have to select this option to open VM.

It's better to make a "Normal Start" working again.

---
On the other hand, I executed the commands: But there are no outputs.

Concerning to compare the current wall clock time to the date and time of the VBoxHardening.log and VBox.log file, I don't manage to do so, I don't found this information.

Otherwise, I post here the VirtualBox zip folder.

---

Thanks,

martin123 wrote:On the other hand, I executed the commands:

Code: Select all

cd "C:\Program Files\Oracle\VirtualBox"
VirtualBoxVM --startvm "VM name"

But there are no outputs.

Just to be sure: You did replace the "VM name" in the command?

martin123 wrote:Concerning to compare the current wall clock time to the date and time of the VBoxHardening.log and VBox.log file, I don't manage to do so, I don't found this information.

If you meant to say that you didn't know where to find the files, take a look inside the e.g. M:\VirtualBox VMs\Nectar\Logs\ folder. If you meant to say that there were no files created, please say so. In the latter case, please provide a zip file containing the M:\VirtualBox VMs\Nectar\Nectar.vbox\ file instead.

General questions:

What type of device is "M:"? Is it constantly available?

Did you do something special regarding USB devices?

Yes, I replaced the "VM name" in the command, see the screenshot.

Concerning the wall clock time, I meant, I can't find and check the information inside the file. I provide here the "vbox" zip file.

The type of "M" device is an external hard drive.

I didn't do something special regarding USB devices.

Thanks for the VM configuration file, which helped to rule out some possible problems (e.g. USB filters).

martin123 wrote:Concerning the wall clock time, I meant, I can't find and check the information inside the file.

Ah, that's probably a misunderstanding. Let me elaborate:

The error you're experiencing happens very early, and therefore it's possible that no new VBoxHardening.log and VBox.log files are created. In consequence, you would find only files from previous VM runs inside the M:\VirtualBox VMs\Nectar\Logs\ folder. I suggested to compare the timestamp (date and time) of the files (not their contents) in the host's filesystem to your wall clock time. Alternatively, you could delete the log files before trying to start the VM.

I emptied the Logs folder and deleted all the files inside, but I still get the same error message when starting the VM.

Of course you got the same error message. But did you get new log files or not?

Yes, I got a new log file: VBoxHardening.log