You are not logged in.

#1 2019-02-06 18:27:10

Marvix
Member
Registered: 2013-10-08
Posts: 98

[SOLVED] VirtualBox Windows machine can't start from saved state

Having an fresh new installation of Arch to my computer, I encounter the same problem I had before with my previous system.

Everytime I start a Windows 7 machine from a saved state, starts with the following error

The VM session was aborted.

Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
SessionMachine
Interface: 
ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}

As I searched, the NS_ERROR_FAILURE (0x80004005) it is a general error and can't get any specific information of the problem to solve.

I have installed  from pacman the
virtualbox
virtualbox-guest-iso
virtualbox-host-modules-arch
and linux-headers

and from AUR only the virtualbox-ext-oracle in order to have USB interaction and shared folder functionality.

As I attach my latest VirtualBox log file

00:00:00.007796 main     VirtualBox XPCOM Server 6.0.4 r128164 linux.amd64 (Jan 28 2019 15:36:33) release log
00:00:00.007800 main     Log opened 2019-02-05T08:49:21.422942000Z
00:00:00.007801 main     Build Type: release
00:00:00.007805 main     OS Product: Linux
00:00:00.007807 main     OS Release: 4.20.6-arch1-1-ARCH
00:00:00.007808 main     OS Version: #1 SMP PREEMPT Thu Jan 31 08:22:01 UTC 2019
00:00:00.007875 main     DMI Product Name: 20236
00:00:00.007963 main     Host RAM: 3812MB (3.7GB) total, 3364MB (3.2GB) available
00:00:00.007970 main     Executable: /usr/lib/virtualbox/VBoxSVC
00:00:00.007971 main     Process ID: 7057
00:00:00.007972 main     Package type: LINUX_64BITS_GENERIC (OSE)
00:00:00.016962 main     IPC socket path: /tmp/.vbox-marvix-ipc/ipcd
00:00:00.352040 nspr-2   VirtualBox: object creation starts
00:00:00.354903 nspr-2   Home directory: '/home/marvix/.config/VirtualBox'
00:00:00.471268 nspr-2   NAT: resolv.conf: nameserver 9.9.9.9
00:00:00.471317 nspr-2   HostDnsMonitor::updateInfo
00:00:00.496689 nspr-2   HostDnsMonitor: old information
00:00:00.496730 nspr-2     no server entries
00:00:00.496736 nspr-2     no domain set
00:00:00.496741 nspr-2     no search string entries
00:00:00.496747 nspr-2   HostDnsMonitor: new information
00:00:00.496792 nspr-2     server 1: 9.9.9.9
00:00:00.496803 nspr-2     domain: lan
00:00:00.496808 nspr-2     no search string entries
00:00:00.555607 nspr-2   VD: VDInit finished with VINF_SUCCESS
00:00:00.563814 nspr-2   VirtualBox: object created
00:00:11.401503 nspr-3   Saving settings file "/home/marvix/.config/VirtualBox/VirtualBox.xml" with version "1.12-linux"
00:00:11.740305 nspr-2   Saving settings file "/home/marvix/.config/VirtualBox/VirtualBox.xml" with version "1.12-linux"
00:00:21.311151 nspr-2   Saving settings file "/home/marvix/.config/VirtualBox/VirtualBox.xml" with version "1.12-linux"
00:06:15.781662 nspr-3   Saving settings file "/home/marvix/.config/VirtualBox/VirtualBox.xml" with version "1.12-linux"
00:06:15.944228 nspr-2   Saving settings file "/home/marvix/.config/VirtualBox/VirtualBox.xml" with version "1.12-linux"
00:06:16.023926 nspr-3   Saving settings file "/home/marvix/.config/VirtualBox/VirtualBox.xml" with version "1.12-linux"
00:06:16.095333 nspr-2   Saving settings file "/home/marvix/.config/VirtualBox/VirtualBox.xml" with version "1.12-linux"
00:06:16.165983 nspr-2   Saving settings file "/home/marvix/.config/VirtualBox/VirtualBox.xml" with version "1.12-linux"
00:06:21.744646 main     VirtualBox: object deletion starts
00:06:22.137828 Watcher  ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={d0a0163f-e254-4e5b-a1f2-011cf991c38d} aComponent={VirtualBoxWrap} aText={The object is not ready}, preserve=false aResultDetail=0
00:06:26.745174 main     {00007f32e40151d0} HostPowerServiceLinux::~HostPowerServiceLinux: RTThreadWait() for 5000 ms failed with VERR_TIMEOUT
00:06:26.745513 main     VirtualBox: object deleted

If i'm not mistaken, the third line shows an error that has to be with permissions?

Versions
VirtualBox                                 6.0.4-1
virtualbox-host-modules-arch 6.0.4-1
virtualbox-guest-iso                 6.0.4-1
linux-headers                           4.20.6.arch1-1
linux                                         4.20.6
virtualbox-oracle-ext              6.0.4-1

Last edited by Marvix (2019-04-23 19:58:50)

Offline

#2 2019-02-07 11:24:23

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 7,195

Re: [SOLVED] VirtualBox Windows machine can't start from saved state

Was the vbox version when the state was saved the same as the one you're running now ?


Multi-init booting with apg Openrc and systemd coexisting
Automounting : not needed, i prefer pmount
Aur helpers : makepkg + my own local repo === rarely need them

Offline

#3 2019-02-07 13:31:18

Marvix
Member
Registered: 2013-10-08
Posts: 98

Re: [SOLVED] VirtualBox Windows machine can't start from saved state

Lone_Wolf wrote:

Was the vbox version when the state was saved the same as the one you're running now ?

Yes, I've tried before there was any kernel and virtualbox related to kernel update, many times.

I can't start a saved state even when I saved it a minute ago. It may not have any relation with software or kernel version.

Last edited by Marvix (2019-02-07 13:58:23)

Offline

#4 2019-02-07 17:00:03

qwer1234
Member
Registered: 2010-06-16
Posts: 9

Re: [SOLVED] VirtualBox Windows machine can't start from saved state

The same issue here with a Windows XP guest machine.

Offline

#5 2019-02-07 19:49:09

Marvix
Member
Registered: 2013-10-08
Posts: 98

Re: [SOLVED] VirtualBox Windows machine can't start from saved state

qwer1234 wrote:

The same issue here with a Windows XP guest machine.

Could you upload your latest Virtualbox log from .config/Virtualbox? It Is named as VBoxSVC.log.(number)

Update

As I'm still messing around, in order to find solution, the problem starts when I install the guest additions software, the snapshot I have without guest additions, works fine with saved states.

I will inform for anything new.

Last edited by Marvix (2019-02-07 20:37:59)

Offline

#6 2019-03-14 11:43:00

ezacaria
Member
Registered: 2007-12-10
Posts: 61

Re: [SOLVED] VirtualBox Windows machine can't start from saved state

Interestingly enough, my xp guest had no trouble to resume from snapshots (even with guest additions), whereas my Arch guest did crash with the same code (0x80004005).

But unfortunately, my issues seem to relate to something else, therefore I cannot offer any help sad

For what it may be worth, the paravirtualisation interface (under machine settings - system - acceleration) works OK as "Legacy" for the xp guest, but had to be changed to "default" for the Arch. However, please note that my error with the Arch guest related  to the "Expression: !VMCPU_FF_IS_SET(pVCpu, VMCPU_FF_INTERRUPT_PIC)" problem and not to the "aRC=E_ACCESSDENIED" as in your case.

On the other hand, I looked at the additions in my xp guest, and they are still on the old level 5.1.24. I updated them to 6.0.4.r128413 and saved a snapshot. I can start the xp guest just fine from it.

Offline

#7 2019-04-23 19:57:59

Marvix
Member
Registered: 2013-10-08
Posts: 98

Re: [SOLVED] VirtualBox Windows machine can't start from saved state

With today's updated new version of Linux's kernel linux 5.0.9.arch1-1  and VirtualBox's 6.0.6-2 version and it's packages, the problem is for now solved.

Offline

#8 2019-04-24 21:50:34

twelveeighty
Member
From: Alberta, Canada
Registered: 2011-09-04
Posts: 493

Re: [SOLVED] VirtualBox Windows machine can't start from saved state

FWIW: I had these problems with Windows 7 guests (i.e. not Windows 10 guests), but oddly enough a "workaround" for me was to reboot the host after saving the state. In other words: the resume worked 100% of the time if the host was "freshly" rebooted. I tried experimenting with unloading the kernel modules, etc., but only a reboot "fixed" it. Just in case this problem creeps back into a future version of Vbox.

Offline

#9 2019-04-30 15:08:48

Nyilas_Laszlo
Member
Registered: 2018-05-17
Posts: 2

Re: [SOLVED] VirtualBox Windows machine can't start from saved state

For 0x80004005 error:

I had the same problem.
uname -r: 5.0.10-arch1-1-ARCH.
VirtualBox version: 6.0.6-2

First I downgraded to VirtualBox but that didn't solve the problem. Then I found this solution:
"Guest machine default name too long with VirtualBox..."
https://github.com/hashicorp/vagrant/issues/9524

So I tested it! I created a new one guest OS with SHORTER name (WinXP) and the problem is gone away.

Offline

#10 2019-05-01 16:59:46

Marvix
Member
Registered: 2013-10-08
Posts: 98

Re: [SOLVED] VirtualBox Windows machine can't start from saved state

Apparently the 0x80004005 error is very general problem and there is to have information of hosting OS, version of virtualbox and guest OS.

Error logs, with few exceptions, shows valuable information.

twelveeighty that didn't work in my case. At least you had to reboot, instead shutdown and boot again all over the guest OS like me. Good of you to share.

Nyllas_Laszio Thank you for sharing.

Offline

Board footer

Powered by FluxBB