SOLVED Virtual machine terminated unexpectedly during startup with exit code 1 (0x1).

[Makarios]

HI I suddenly have this error when I try to open my VM.

VM wa srunning fine, then I shut down my pc, went out for an hour or 2 and on my return started up the Host and the VM does not want to open..infact all my VM;s gives the same error.


Failed to open a session for the virtual machine Win10.

The virtual machine 'Win10' has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

Ive been running this VM for several years at least 1 x per day.

Host is Linux mint 20.3 Cinnamon
Official Oracle Virtual box 6.1 - Version 6.1.34 r150636 (Qt5.12.8)

I tried attaching the log file but its size is 220kb and the attachments can only accept 128kb

Any guide as to steps I can take to recover form this?

i have restored the host with Time shift to 2 prior backups but it has no effect on the error

[Makarios]

Here is the error message screenshot

[Makarios]

Hi All

Can Any one assist me with this?

[scottgus1]

I am no Linux guru, but I have seen this before. FWIW It's probably web-searchable, especially with the site restrictor "site:forums.virtualbox.org" added.

I believe this happens when there is a mix of Linux distro fork and official Virtualbox versions on the PC, and a purge & the prerequisites for Official weren't run first.

[Makarios]

Hi Scottgus1, its just weird that this Virtual box ( official) Vm has been running for 24 months or longer with zero issues.

[scottgus1]

Yep, sure can do that. Then something updates, or a new kernel, or something else etc.

(Virtualbox doesn't auto-update, unless you have it tied into the package manager, which can auto-update it.)

[Makarios]

My Problem has been solved...

Seems it might have been an issue with a kernel update on Linux mint.

These are the steps I took..

1. I restored with Timeshift to a few recent backups that did not resolve the issue
2, I then restored with timeshift to a backup of about a week ago.

This resolved the problem. Very relieved!!

3. I then made a fresh backup with Timeshift and did a full refresh on my updates and then updated everything again.

4. Just opened the VM and its working perfect, and my other regular programs has no issue like always on LMint.

Happy to close this incident

[scottgus1]

Great! Glad you're up and running.

Be aware that kernels can update again, of course, and will. They have a tendency to do that. You can uninstall/purge Virtualbox when this happens, run the prerequisites, then install the latest Virtualbox available (Virtualbox can only run on kernels that came out before the Virtualbox version came out).

Your VMs will remain through an uninstall/purge.

[Makarios]

Thanx a mil