VM on ubuntu not starting after reboot of system. Result Code: NS_ERROR_FAILURE (0X80004005)

Discussions related to using VirtualBox on Linux hosts.
Post Reply
PatWasHere
Posts: 4
Joined: 11. Jan 2024, 19:25

VM on ubuntu not starting after reboot of system. Result Code: NS_ERROR_FAILURE (0X80004005)

Post by PatWasHere »

Hi All,

Running Virtualbox 7.0.14 f161095 to run a homeasistant VM on Ubuntu 22.04. Noticed my HA VM crashed a couple of times over the past week and was able to restart the VM manually. In an attempt to fix it rebooted the whole machine. After the reboot the VM no longer will start. I have tried to restore a snapshot and archived version that was working prior, but they also will not start.

Any guidance on how to tackle this would be appreciated.

I did do a apt get/apt update recently. Maybe a system update messed with some versions?

Getting the following error shown in the Virtualbox UI.

Code: Select all

"The virtual machine 'homeassistant 1 1' has terminated unexpectedly during startup with exit code 1 (0x1).
Result Code:
NS_ERROR_FAILURE (0X80004005)
Component:
MachineWrap
Interface:
IMachine {300763af-5d6b-46e6-aa96-273eac15538a}"

Here is the last part of the log: (let me know if I should post the whole thing)

Code: Select all

01:00:41.278626 E1000#0: TX frames up to 16384: 12
01:00:41.278628 E1000#0: TX frames up to 32768: 6
01:00:41.278629 E1000#0: Larger TX frames    : 1
01:00:41.278631 E1000#0: Max TX Delay        : 0
01:00:41.317563 GIM: KVM: Resetting MSRs
01:00:41.320183 vmmR3LogFlusher: Terminating (VERR_OBJECT_DESTROYED)
01:00:41.320225 Changing the VM state from 'DESTROYING' to 'TERMINATED'
01:00:41.322973 Console: Machine state changed to 'PoweredOff'
01:00:41.323003 VBoxHeadless: processEventQueue: VERR_INTERRUPTED, termination requested
01:00:41.826299 VBoxHeadless: exiting
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: VM on ubuntu not starting after reboot of system. Result Code: NS_ERROR_FAILURE (0X80004005)

Post by scottgus1 »

Please zip and post the VboxHardening.log.
PatWasHere
Posts: 4
Joined: 11. Jan 2024, 19:25

Re: VM on ubuntu not starting after reboot of system. Result Code: NS_ERROR_FAILURE (0X80004005)

Post by PatWasHere »

not sure how to get one of VboxHardening.log. Attached vbox.log and vboxui.log files. Thanks fo the help.
Attachments
VBoxUI.zip
(34.95 KiB) Downloaded 35 times
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: VM on ubuntu not starting after reboot of system. Result Code: NS_ERROR_FAILURE (0X80004005)

Post by scottgus1 »

Sorry, it's a Linux host, I should have seen that. No hardening log.

This may be because there's a mix of Virtualbox versions on the host. Uninstall/purge all Virtualbox-related files (the VMs will stay behind) then reboot and reinstall Official Virtualbox from www.virtualbox.org. Note the prerequisites first https://www.virtualbox.org/manual/ch02. ... nux-prereq. Note also that Official Virtualbox doesn't use dkms.
PatWasHere
Posts: 4
Joined: 11. Jan 2024, 19:25

Re: VM on ubuntu not starting after reboot of system. Result Code: NS_ERROR_FAILURE (0X80004005)

Post by PatWasHere »

OK, will give that a shot. so 7.0.14 is ok to install?
PatWasHere
Posts: 4
Joined: 11. Jan 2024, 19:25

Re: VM on ubuntu not starting after reboot of system. Result Code: NS_ERROR_FAILURE (0X80004005)

Post by PatWasHere »

WOOT! I am up and back running.

What I did,

Closed VirtualBox app.
from terminal:

sudo apt-get remove virtualbox\*
sudo reboot

After the reboot download the deb file from https://www.virtualbox.org/wiki/Linux_Downloads and install it.
opened up VirtualBox and started my VM :) no errors. I am happy.

Thanks for the help.
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: VM on ubuntu not starting after reboot of system. Result Code: NS_ERROR_FAILURE (0X80004005)

Post by scottgus1 »

Great! Glad you're up and running.
Post Reply