VBOX_E_INVALID_OBJECT_STATE 0X80BB0007

Discussions related to using VirtualBox on Linux hosts.
Post Reply
talkinggoat
Posts: 7
Joined: 29. May 2011, 18:08
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: XP, Fedora

VBOX_E_INVALID_OBJECT_STATE 0X80BB0007

Post by talkinggoat »

For the last couple weeks, we've been having an issue where the VBoxEs don't start up correctly, after being backed up. I use a script that commands the box to go into a saved state, then exports the state to an OVA file, on the backup media, then re-launches the VBox in it's previous, headless state. For about a year, it has not had any issues, then, a couple weeks ago, I cloned the VBox, to get rid of the saved states it had, so we could upgrade the storage on our server. Completed no problem. Ever since then, it has been giving this problem. It seems to be random, however, this is the error log...

Code: Select all

VirtualBox VM 5.1.22 r115126 linux.amd64 (Apr 28 2017 16:44:54) release log
00:00:00.037452 Log opened 2017-06-11T23:47:27.617747000Z
00:00:00.037455 Build Type: release
00:00:00.037461 OS Product: Linux
00:00:00.037463 OS Release: 4.8.0-53-generic
00:00:00.037466 OS Version: #56~16.04.1-Ubuntu SMP Tue May 16 01:18:56 UTC 2017
00:00:00.037508 DMI Product Name: System Product Name
00:00:00.037524 DMI Product Version: System Version
00:00:00.037611 Host RAM: 16044MB (15.6GB) total, 14645MB (14.3GB) available
00:00:00.037621 Executable: /usr/lib/virtualbox/VBoxHeadless
00:00:00.037623 Process ID: 6867
00:00:00.037625 Package type: LINUX_64BITS_UBUNTU_16_04
00:00:00.057417 Installed Extension Packs:
00:00:00.057458   Oracle VM VirtualBox Extension Pack (Version: 5.1.22 r115126; VRDE Module: VBoxVRDP)
00:00:00.060047 Console: Machine state changed to 'Restoring'
00:00:00.069884 Console: Machine state changed to 'Saved'
00:00:00.075569 Power up failed (vrc=VINF_SUCCESS, rc=VBOX_E_INVALID_OBJECT_STATE (0X80BB0007))
The machine would not start back up, after this happens, without some work. I decided to restart the Vbox service, but discovered there is no longer a script in /etc/init.d. The scrip now resides in /usr/lib/virtualbox. I isolated the process through the command,

Code: Select all

ps -e | grep -i vbox
 6171 ?        00:00:00 iprt-VBoxWQueue
 6175 ?        00:00:09 iprt-VBoxTscThr
 6460 ?        02:13:09 VBoxXPCOMIPCD
 6465 ?        1-23:17:04 VBoxSVC
Then, kill the process numbers. Yours will be different.

Code: Select all

sudo kill -9 6460 6465
Now, re-issuing

Code: Select all

ps -e | grep -i vbox
Should only show...

Code: Select all

6171 ?        00:00:00 iprt-VBoxWQueue
 6175 ?        00:00:09 iprt-VBoxTscThr
Restart the VBoxSVC by using...

Code: Select all

nohup /usr/lib/virtualbox/VBoxSVC &
Virtualbox then allowed me to re-start the vms, from the saved state. IDK if this is going to continue. If it does, I'll come back and update, but this seems to have solved the issue of the vms not wanting to power back up.
Post Reply