Occasional Hang when saving machine state - data loss

[mcnaz]

Hi there.

Occasionally Virtualbox fails to save the machine and hangs on 100% on the "... Saving the execution state of the virtual machine"

I am forced to kill the VirtualBox.exe process. This unfortunately corrupts the attached virtual disk and often leads to any work done during that session to be lost.

Host Windows XP SP2

[frank]

Still relevant with VBox 4.0.4?

[frank]

No response, closing.

[midix]

This happened a week ago to me on Windows 7 Host with XP guest (both 32 bit) and just happened on Windows 7 Host with Vista guest. I am looking now at the "Saving the execution state" 100% message for an hour already. It has not fully hung, actually, I can move the message around and the guest window beneath the message is being redrawn normally (with the usual grayscale overlay which is visible on saving). It seems I'll have to kill VirtualBox.exe process again.

My log file looks really similar to the attached one: it has a bunch of messages at the end:

ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={6375231a-c17c-464b-92cb-ae9e128d71c3} aComponent={Console} aText={The virtual machine is being powered down} aWarning=false, preserve=false

VirtualBox version 4.0.8. I will upgrade to 4.0.10. now and see if it occurs again.

[impc]

Still relevant with VBox 4.1.2 Does not depend on running guest (happened with windows/linux)

[impc]

Hang on shutdown after 5xx hours of running

[ws]

It has not fully hung, actually, I can move the message around and the guest window beneath the message is being redrawn normally with the usual grayscale overlay

I observed the same characteristics here:

virtualbox 4.1.4 r74291 Windows 7 x64 also using the following software: kaspersky antivirus, vmware-player 3

added some attachments with prefix "ws111114". (Stack traces were taken at different points in time.)

After saving these attachments I did the following (no attachments for the second instance!):

While application was not responding, i started a second instance and navigated to the 4th item ("Massenspeicher" in the German GUI). The content (with IDE-Controller and SATA-Controller) was not drawn and the second application stopped responding too. I stopped further investigation at this point.

[ws]

BTW: I checked the logs of Kaspersky Anti-Virus 2011: No (false positive) threat was reported.

[ws]

Also reappeared with

VirtualBox version 4.1.8 r75467 (and Oracle VM VirtualBox Extension Pack of the same version)

host: Windows 7 x64 without any anti-virus software installed

guest: ubuntu 11.10 32bit with current guest additions installed

Would a mini-dump created by sysinternals process explorer help in finding the bug?

[orand]

This just happened to me with VirtualBox version 4.1.10 r76836. All the behaviors described above match what I'm seeing.

Host: Windows 7 x64

Guest: Windows Server 2003 32-bit

I then tried to save the state of another guest I had running and encountered the same issue.

[xerces8]

4.1.12 Win7 host, Win XP guest

Hangs on close. The log has this line repeating about once each second:

00:57:57.102 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={1968b7d3-e3bf-4ceb-99e0-cb7c913317bb} aComponent={Console} aText={The virtual machine is being powered down}, preserve=false

[Marcus]

This happens sometimes with me on VirtualBox 4.1.6

Host: Windows 7 x64

guests: Windows Server 2008R2, Windows Vista x32, Windows XP x32

[dracula]

Same here. Host Windows 7 Pro 64b, Guest: Windows XP 32 Guest addons are installed. Happened to several machine on same host. Starting 4 guests at same time and try to close one after the other.

ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={1968b7d3-e3bf-4ceb-99e0-cb7c913317bb} aComponent={Console} aText={The virtual machine is being powered down}, preserve=false

[frank]

Please attach a VBox.log file of such a VM session.

[KLH]

log from hanging VM

[KLH]

I've also seen this problem. It seems to be most prevalent when the host machine is busy (high mem usage), but I have no real evidence for this.

This behavior has trashed several VMs of mine though.

Log attached.

[brooze]

I have run into this case many times, and my conclusion is it has something related to peripheral device interrupt.

It happened when pc has serial-com device connect and plugout while save state machine.

I have no energe and time to reproduce it, maybe some guy can do it.

[progmars]

I occasionally get the same problem on Windows 7 64 bit host with VirtualBox 4.1.12. There were no visible issues, why this might happen - enough free physical RAM, enough free disk space, no hardware plugged/unplugged during saving. Still cannot reproduce.

[danf84]

Happened to me a few times with 4.1.20 and the stable version before that. Log "Win7-Pro-XPSP3Guest" attached. It got to 100% during "Saving State". Lots of access denied of some sort flooding the log while it's hanging.

[AnotherLife]

Same here. I got this when it happened. Using version 4.1.20

01:31:51.151 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={1968b7d3-e3bf-4ceb-99e0-cb7c913317bb} aComponent={Console} aText={The virtual machine is being powered down}, preserve=false

[JarrettBillingsley2]

Had this happen to me twice in the last week. I've attached the two relevant logs. I'm using 4.1.20, host OS is Win7 Ultimate x64, guest is 32-bit Linux.

[christo]

Happens quite often. Using 4.2.0 r80737. Win7 Professional x64.

49:50:27.178217 SSM: Successfully saved the VM state to '[REMOVED]\Snapshots\2012-10-21T10-49-45-952405400Z.sav'
49:50:27.178304 Changing the VM state from 'SAVING' to 'SUSPENDED'.
49:50:27.285398 Console::powerDown(): A request to power off the VM has been issued (mMachineState=Saving, InUninit=0)
49:50:27.285562 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The virtual machine is being powered down}, preserve=false
49:50:28.300470 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The virtual machine is being powered down}, preserve=false
...

[TTTIk3]

I'm starting to get worried that I'm going to lose my data if I continue to use VirtualBox. This occurs every other day now on 4.2.2 and has been occurring regularly for over a year. Running as administrator does not seem to be the answer and I'm not sure what else to try. I used to think it had to do with unplugging USB devices during saving, but that does not seem to be the case. It occurs even if I don't touch my machine during saving.

[AnotherLife]

It happens to me and I have USB controller disabled.

Maybe it has to do with I/O APIC ? For some reason I had it enabled even though I don't know what it does :-/

[wpeckham]

This happens to me with the log holding a ton of these messages ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The virtual machine is being powered down}, preserve=false

If I leave it all night, the log file gets HUGE, and waiting does no good. Win7 host 32-bit with Win7 guest 32bit, mostly default settings with more memory allocated. VB versions 4.2.2 and 4.2.4.

I was going to add "no other symptoms", but I recently noticed that this happens more often when the guest has been running slow after several hours of work. If I bring it up and do a shutdown while things are still running pretty fast, it is less likely. Still a nearly daily event. It will take several days of trials to verify this, so today it is only an observation.

[mrjl]

Happening for me as well. What I noticed is that I had some heavy disk operations going on on a host PC when I was saving VirutalBox session and it got stuck at 100%. I' using it on dell laptop with a normal (non ssd) hard drive under win7 x64. Error message in the log is the same as mentioned above. Virtual Box v 4.2.4.

[mrjl]

And again. Virtual Box v 4.2.6. Should I start looking for alternatives?

[frank]

Looks like only Windows users are affected. Is there any non-Windows user who observes the same bug? mrjl, do you have any USB devices attached to your guest?

[mrji]

The only USB device is mouse, which is attached to host. Just got the same issue again. What I have noticed, though, is that if I have heavy disk usage in host and guest, saving will most certainly hang.

[marcs]

I have a similar issue with OS X Mountain Lion host, Ubuntu 12.04 guest.

This occurred with 2.4 and again after upgrading to 2.6.

This seems to be connected to the guest additions. If I uninstall the guest additions, the problem goes away.

Here's the tail of the log:

00:00:25.834372 Guest Additions capability report: (0x5) seamless: yes, hostWindowMapping: no, graphics: yes
00:04:16.045500 Changing the VM state from 'RUNNING' to 'SUSPENDING'.
00:04:16.417176 AIOMgr: Endpoint for file '/Users/marcstober/VirtualBox VMs/Ubuntu/Ubuntu.vdi' (flags 000c0781) created successfully
00:04:16.483511 PDMR3Suspend: 149 730 646 ns run time
00:04:16.483566 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'.
00:04:19.119451 Changing the VM state from 'SUSPENDED' to 'SAVING'.
00:04:19.184924 VUSB: detached 'HidMouse' from port 1
00:05:25.185815 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={Already paused}, preserve=false

[marcs]

I have the same issue when I attempt to take a snapshot with the guest additions installed, so it seems to be an issue with saving state.

Update: I was able to resolve the problem by disabling 3D acceleration.

Not sure if it's the same issue as the Windows bug above or just the same symptom.

[Philip]

I got the problem on version 4.2.6 running on Windows 7 R2. The OS in the session was Windows 2008 R2.

During the session I had deleted a mouse driver, removed the mouse, added the mouse back in and used a new driver.

[rogerdpack]

just got this, full log:  https://gist.github.com/rdp/4724563

The relevant part appears to be, at the end, the following line is repeated over and over, forever:

00:59:50.485217 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The virtual machine is being powered down}, preserve=false

with 4.2.4, windows x64 host, linux guest, but I've run into it on other machines, as well...

[aidanhs]

Still present on 4.2.6 r82870. Windows 7 x64 SP1 host, Linux (Lubuntu) guest. I had no USB devices plugged in at all when the suspension started and when it hung (but have plugged and unplugged things while the VM was active). Guest additions are installed.

Precisely the same error as above. The VBox main interface can be started and is responsive for poking with other VM's settings. Some log context:

01:47:17.997288 ***
01:47:17.997289 ************** End of Guest state at power off ***************
01:47:17.997332 PDMR3PowerOff: 8 324 ns run time
01:47:17.997340 Changing the VM state from 'POWERING_OFF' to 'OFF'.
01:47:18.392239 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The virtual machine is being powered down}, preserve=false
[...]

I have closed the main interface and suspended the two remaining virtualbox processes (VBoxSVC.exe and its child VirtualBox.exe) so the log doesn't grow massively. Would any dumps or experiments be useful?

[frank]

Could you attach the complete VBox.log file?

[aidanhs]

Log attached (aidanhs-VBox.log), with the following modifications

• Minor path tweak at 00:00:01.096647 to remove some info.
• Many thousands of duplicate error messages at the end of the file removed.

[aidanhs]

Just to note I can probably keep these VMs suspended for about the next 24 hours, but I'll need to actually use them at some point. Is there any point leaving them as they are now (i.e. is there any more info that anyone might want?) or should I just terminate them (I'll grab an application dump before I do so)?

Edit: I now have a 1.18GB and 70MB dump file for VirtualBox.exe and VBoxSvc.exe respectively.

[yakatz]

Same issue:

Host: Windows 7 x64, Virtual Box 4.2.6 r 82870. Guest: Windows Server 2012 Essentials.

Error only started after I installed Addons.

VBox.log growing extremely fast (20,000 lines in 6 hours).

Can I supply any information that will assist in tracking down the problem? I have the VBox.log mostly anonymized (used find and replace, so I hope it is good).

[yakatz]

I should have posted that I had the same problem with a Ubuntu VM around the same time and I have the log for that one too.

[progmars]

Still present on 4.2.10r84104

I noticed that I often get these lines at the end of log files after saving state normally:

08:53:58.299869 Changing the VM state from 'DESTROYING' to 'TERMINATED'. 08:53:59.231839 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The virtual machine is being powered down}, preserve=false

and the last line repeats couple of times.

But in cases when saving hangs at 100%, the last line is repeated hundreds of times (until I kill Virtualbox process manually).

My specs:

Host: Windows 7 SP1 64bit. RAM: 8GB. When saving hangs, I still have about 1.5GB free RAM.

Guest: Windows 7 SP1 32bit. RAM: 3.5GB. Guest additions installed.

[klaus]

That "last line" is actually generated because the VM manager GUI tries to get a screenshot of the VM periodically for its preview. So it has very little to do with the actual cause of the hang, it's just a symptom showing how long the VM is hanging before killing it.

[progmars]

Thanks, klaus, for clearing this up for me, I didn't know that.

Today it happened again. The log file says:

08:10:13.510847 Changing the VM state from 'RUNNING' to 'SUSPENDING'.
08:10:13.551646 AIOMgr: Endpoint for file 'V:\Win7Dev\System.vdi' (flags 000c0781) created successfully
08:10:13.656872 AIOMgr: Endpoint for file 'V:\Win7Dev\Data.vdi' (flags 000c0781) created successfully
08:10:13.754973 PDMR3Suspend: 240 637 872 ns run time
08:10:13.755003 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'.
08:10:17.030098 Changing the VM state from 'SUSPENDED' to 'SAVING'.
08:10:34.793818 SSM: Footer at 0x651fc80c (1696581644), 33 directory entries.
08:10:34.999009 SSM: Successfully saved the VM state to 'V:\Win7Dev\Snapshots\2013-04-15T15-44-58-473591600Z.sav'
08:10:34.999034 Changing the VM state from 'SAVING' to 'SUSPENDED'.
08:10:36.242396 Console::powerDown(): A request to power off the VM has been issued (mMachineState=Saving, InUninit=0)
08:10:36.243031 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The virtual machine is being powered down}, preserve=false
... again last line repeated hundreds of times ...

When the saving hangs at 100%, the VM is still using all of its allocated memory. There are ~2GB RAM free on the host. No other heavy activities were in progress while saving, I just closed the VM and started watching a Youtube video on Google Chrome while the VM was saving in background.

[Petr Vones]

Still with 4.2.12. Host: Windows 7 x64, Guest: Windows Server 2008 R2.

After that, the virtual machine can not be started again until host reboot.

[Petr Vones]

VirtualBox 4.2.12 close crash log

[Marco2]

log file

[Marco2]

Same issue for me Vbox 4.2.10 r84104. Host Win 7 x64. Guest Linux 2.6.

[frank]

Marco2, the user marcs wrote that with disabled 3D in the VM settings this does not happen. Can you confirm that?

[Petr Vones]

Replying to frank:

Marco2, the user marcs wrote that with disabled 3D in the VM settings this does not happen. Can you confirm that?

No, it happend to me with both 3D and 2D acceleration disabled. I don't have USB support installed.

[johnwesting12]

Same problem for me. VBox v4.2.12 r84980, Win 7 x64 host, Ubuntu 12.04 guest, no 3D acceleration. 2 logs are attached, don't know if these are relevant logs they're from C:\Users\myusername\.VirtualBox\. I have guest additions installed. I was using a Broadcom Bluetooth USB dongle in the VM with a custom USB kernel driver. I closed the app that was using the USB dongle and released the device in the VM before I closed the VM (suspended and saved the machine state). It stuck at 100%. I had to close the VM in the task manager. When I resumed the VM I found that the machine's state was not saved.

[Petr Vones]

More on this, maybe it is related to NAT networking. Can anyone else confirm that ?

[AmicaNoctis]

I had the same problem for the first time today after 3 weeks of using VirtualBox 4.2.12 rev84980.

OS: Windows 7 Ultimate x64 (both host and guest) Guest add-ons installed

I used the Devices menu to capture a USB stick by the guest, saved something and released it again, which went perfectly well (I didn't do this before). Somewhat later I tried to save the guest's state and had the same 100% hang.

Log file VBoxSVC.log.9 attached as amica.log

[Lofi007]

Replying to Petr Vones:

More on this, maybe it is related to NAT networking. Can anyone else confirm that ?

Looks suspicious. Here's the log when it hangs:

...
00:02:28.689562 /TM/VirtualSync/CurrentOffset           0 ns
00:02:28.689571 ********************* End of statistics **********************
00:02:29.404872 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The virtual machine is being powered down}, preserve=false
00:02:30.406494 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The virtual machine is being powered down}, preserve=false
...

and here when it doesn't:

...
00:01:13.266680 /TM/VirtualSync/CurrentOffset      245998 ns
00:01:13.266683 ********************* End of statistics **********************
00:01:13.270153 NAT: zone(nm:mbuf_cluster, used:0)
00:01:13.270530 NAT: zone(nm:mbuf_packet, used:0)
00:01:13.270536 NAT: zone(nm:mbuf, used:1)
00:01:13.270540 NAT: zone(nm:mbuf_jumbo_pagesize, used:0)
00:01:13.270893 NAT: zone(nm:mbuf_jumbo_9k, used:0)
00:01:13.271065 NAT: zone(nm:mbuf_jumbo_16k, used:0)
00:01:13.271160 NAT: zone(nm:mbuf_ext_refcnt, used:0)
00:01:13.277504 Changing the VM state from 'DESTROYING' to 'TERMINATED'.
00:01:13.393615 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The virtual machine is being powered down}, preserve=false
...

1. e. I still got the E_ACCESSDENIED error which someone pointed out isn't related to the hang.

But you can see that the next log entries when it hangs would have been NAT related.

[Lofi007]

fyi, the bug is still in VirtualBox-4.2.16-86992-Win

I upgraded from 4.2.14-86644-Win to 4.2.16-86992-Win, started the VM (NAT from the old version remained enabled), installed the Guest Additions. The Guest Additions required reboot, so I shut down the VM. Or more precisely, I tried. During the shut down the machine was hanging with the usual symptoms. Only a reboot helped to solve the problem.

After that I uninstalled VirtualBox, installed 4.2.16-86992-Win, did the same procedure, except that I disabled the network before starting the VM. This worked so far.

edit: nope. Disabling the network adapter doesn't solve the problem. It still occurs. Does anyone know logging settings which I could use in order to find the cause for this problem?

[wacher]

E_ACCESSDENIED

[wacher]

Same here. Log has been attached. (Host is Win7 64bit, guest is Win7 32 bits)

[Marco2]

Log File

[Marco2]

Same here. log file attached. Host Win7 64, Guest Linux 64

[ncsome]

Process monitor trace

[ncsome]

The same thing happens to me. Win7 64 host, linux 64 guest.

I have attached a screenshot (https://www.virtualbox.org/attachment/ticket/7756/error.jpg) and a csv showing the log of process monitor where you can see that it's trying to create a file mapping and it gets a "file locked with only readers"... This operations happens over and over writing the log file everytime... I also looked at the registry entries that the process is reading, exported and uploaded them here ...

it's really frustrating that this happens everytime I try to save the virtual machine state ...

[ncsome]

processmonlogfile

[ncsome]

registry entry

[ncsome]

running "ps ax | grep -i vb" on the guest machine and killing the process returned by that query before saving the VM state seems to prevent the issue from happening...

[Petr Vones]

Replying to ncsome:

running "ps ax | grep -i vb" on the guest machine and killing the process returned by that query before saving the VM state seems to prevent the issue from happening...

There are two processes in Windows guests, VBoxTray.exe running under logged user and VBoxService.exe running under SYSTEM account. I guess the first is innocent but the second one provides communication between the guest and host. Killing the second one process is probably not a good idea but if it helps it indicates the issue.

Isn't there anything interesting in guest event log ?

[Chondroma]

This is still happening intermittently to me with VirtualBox 4.2.16 r86992 w/Extension Pack 4.2.16, using a Windows 7 x64 SP1 host and a Debian wheezy x64 guest. I didn't notice this happening before I updated to this current version of VirtualBox.

I can't reproduce it reliably, but I can comment that it tends to occur after the guest has been running after a few days. I can't recall an instance when I've started the guest and tried to save its state after a short duration (<~6 hours) and had this bug.

I've attached the guest log and the VBoxSVC log.

[teddyzhao]

I just encountered this problem as everybody did. I am running Ubuntu 12.04 LTS guest on a Windows 7 Professional x64 SP1 host with VirtualBox 4.2.4 r81684.

@Chondroma: This happened to me when I only ran it for less than an hour.

Fortunately, I was able to recover my previous session and this is the most important thing I'd like to share with you all. Here is how I did it.

1. When it hangs at 100%, check the log file to see if the VM state has been saved successfully (see below). If so, you can terminate all VirtualBox related processes from the Window Task Manager.

   00:42:10.625421 SSM: Successfully saved the VM state to 'C:\VirtualBox VMs\UB Linux\Snapshots\2013-09-11T13-18-17-401051000Z.sav'
   00:42:10.625476 Changing the VM state from 'SAVING' to 'SUSPENDED'.
   

2. Reopen the VirtualBox and your VM state will be "Powered Off" instead of "Saved" because of the failure. Just turn it on and save it again. If it doesn't hang this time, you will have another file (e.g. 2013-09-11T14-09-40-972717900Z.sav) in the "\Snapshots" folder and the VM state should be "Saved".

3. Copy both .sav files to another location as a backup. Delete the new file in the "\Snapshots" folder and rename the old file (2013-09-11T13-18-17-401051000Z.sav) to the new one (2013-09-11T14-09-40-972717900Z.sav).

4. Start the VM, and it will load the new file (actually your old saved session when it crashed) and everything should recover.

Hope someone will benefit from it.

[Petr Vones]

Can anyone confirm the issue with 4.3 version ?

[wacher]

Is seems to be wrong in different way. Not hang anymore but simple crash.

[klaus]

The recipe in comment 55 looks way more complicated than it needs to be - if you just want to associate a saved state with a VM (better be sure that it's the right file and for the right state, otherwise this can lead to data loss) with VBoxManage adoptstate "vmname" /path/to/file.sav

[wacher]

Log for the modified #57 comment

[wacher]

14:49:10.733630 Changing the VM state from 'SUSPENDED' to 'POWERING_OFF'.
...
14:49:10.736047 Changing the VM state from 'POWERING_OFF' to 'OFF'.    
14:49:10.740217 Changing the VM state from 'OFF' to 'DESTROYING'.     
...
14:49:10.804199 Changing the VM state from 'DESTROYING' to 'TERMINATED'.

[Petr Vones]

Replying to wacher:

Is seems to be wrong in different way. Not hang anymore but simple crash.

How exactly did it crash ? The log does not contain any errors. It looks like the state had been saved correctly: https://www.virtualbox.org/attachment/ticket/7756/VBox.log.2.1#L1416

[wacher]

Yes, the state had been saved but after that VirtualBox.exe process crashed. The final VM state is Aborted. There are more log lines, please read more :) If you see the comments above mine, you can see that the saving of state is successful. Before 4.3 the Vbox process just hang and you have to kill it, from now you don't have to kill it, it collapse. This symptom is not really reproducable, cca 1-2 of 10 saving state is failed.

[wacher]

One more thing. I used to use 32 bits host with 32 bits guest and I never experienced this. Some months ago I have started to use 64 bit host, after that everything changed.

[Petr Vones]

Replying to wacher:

The final VM state is Aborted. There are more log lines, please read more :)

I can't find it in the log provided. It might help to post the VirtualBox.exe process crash information from Event Log.

[wacher]

Here is it:

Log Name:      Application
Source:        Application Error
Date:          2013.10.22. 0:18:44
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Tamas-PC
Description:
Faulting application name: VirtualBox.exe, version: 4.3.0.0, time stamp: 0x525d1b9c
Faulting module name: QtCoreVBox4.dll, version: 4.8.4.0, time stamp: 0x51cd576a
Exception code: 0xc0000005
Fault offset: 0x000000000011cae6
Faulting process id: 0xc18
Faulting application start time: 0x01cece2f4910ec2c
Faulting application path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
Faulting module path: C:\Program Files\Oracle\VirtualBox\QtCoreVBox4.dll
Report Id: bf2edb4f-3a9e-11e3-aa49-28924a269714

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-10-21T22:18:44.000000000Z" />
    <EventRecordID>1846</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Tamas-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>VirtualBox.exe</Data>
    <Data>4.3.0.0</Data>
    <Data>525d1b9c</Data>
    <Data>QtCoreVBox4.dll</Data>
    <Data>4.8.4.0</Data>
    <Data>51cd576a</Data>
    <Data>c0000005</Data>
    <Data>000000000011cae6</Data>
    <Data>c18</Data>
    <Data>01cece2f4910ec2c</Data>
    <Data>C:\Program Files\Oracle\VirtualBox\VirtualBox.exe</Data>
    <Data>C:\Program Files\Oracle\VirtualBox\QtCoreVBox4.dll</Data>
    <Data>bf2edb4f-3a9e-11e3-aa49-28924a269714</Data>
  </EventData>
</Event>

[Petr Vones]

Replying to wacher:

Good, it is Access Violation exception somewhere in Qt4 UI library.

[wacher]

Replying to Petr Vones:

Replying to wacher:

Good, it is Access Violation exception somewhere in Qt4 UI library.

Maybe you are right, but from my point of view it doesn't matter which part of VirtualBox has been failed.

[rwoolf]

I am on VirtualBox 4.3 and this happens to me on a regular basis. It happens at least 50% of the time when I try to save a session. Sometimes I get to 100% and it just sits there until I kill the process, and sometimes it just crashes towards the 100%. Win 7 pro as host, Elementary OS Luna as guest. I would be glad to provide any debug info if someone can tell me exactly what data I should collect.

[Petr Vones]

Interesting comment https://www.virtualbox.org/ticket/3207#comment:12 under similar older ticket regarding clipboard.

[Petr Vones]

Replying to rwoolf:

I am on VirtualBox 4.3 and this happens to me on a regular basis

Could you specify exact version, is it 4.3.0 or 4.3.2 ? There is similar issue that has been just fixed in 4.3.2 and closed https://www.virtualbox.org/ticket/3207#comment:15

[rwoolf]

Replying to Petr Vones:

Replying to rwoolf:

I am on VirtualBox 4.3 and this happens to me on a regular basis

Could you specify exact version, is it 4.3.0 or 4.3.2 ? There is similar issue that has been just fixed in 4.3.2 and closed https://www.virtualbox.org/ticket/3207#comment:15

I was on 4.3.0, but I upgraded to 4.3.2 in hopes that it solved the problem but no change in behavior. I am hanging over 50% of the time. Unfortunately this is unusable as I can't save state so I am moving over to VMWare as it seems to have no problems. I would be glad to help anyone troubleshoot this problem if they could tell me anything I could provide. This instability is on my Dell laptop. My Dell desktop machine does not exhibit this problem. Both have same Host and Guest OS.

[Petr Vones]

Replying to rwoolf:

I was on 4.3.0, but I upgraded to 4.3.2 in hopes that it solved the problem but no change in behavior. I am hanging over 50% of the time.

I share your frustration but I still like VirtualBox more than VMWare, I have a lot of old VirtualPC VHD files that VirtualBox can directly use without conversion required by VMWare.

I think that more verbose https://www.virtualbox.org/wiki/VBoxLogging logging is required to diagnose it.

[frank]

Guys, could you re-check with VBox 4.3.6 and attach a VBox.log file from such sessions where suspending hangs? Thank you!

[wacher]

GUI crashed, VM is aborted. Is this matter? (See comment#59) Are the virtualbox crashing and the suspending hangs related, maybe?

[Petr Vones]

Replying to wacher:

GUI crashed, VM is aborted.

Could you post the log file ?

[wacher]

VM log for crashed GUI

[wacher]

VM log for crashed GUI - eventlog entry

[wacher]

Here is the log, you can see changes of state: running > suspending > suspended > saving > suspended > powering_off > off > destroying > terminated
Everything goes right but suddenly something happens and the successfully saved state is destroyed, VM is terminated.

[Petr Vones]

Indeed, and the Access Violation exception somewhere in Qt4 library again.

[PRab]

I can confirm that this is still happening in 4.3.6. Windows 7 (64 bit) host, Windows 2012 guest. I will attach the log.

[Wayne Sallee]

Occasionally on an older version the saved state would become corrupted and I would have to discard the saved state. So I upgraded to 4.3.6 hoping it would fix it, but instead it always fails when saving state on one of my guests every time. I have 18 guests.

An interesting thing about the guest that fails, is that if I pause it, it will pause, but not grey out. Maybe that will add a clue as to what is happening. Likewise it will not grey out when saving machine state.

Wayne Sallee Wayne@…

[Wayne Sallee]

Ok here is a reproducible situation that should interest you. :-)

Linux Host Microsoft Windows Guest

Install guest additions. Reboot guest. On boot up you may get error something like "could not read from the boot medium, system halted". If so, reboot. Windows starts up. Pause guest. It will pause, but not grey out. Unpause, and save state. It will fail. Restart. Uninstall guest additions. Reboot. Pause guest. It will pause and grey out. Unpause and save state. It will save just fine.

So the Guest additions is causing the problem.

Wayne Sallee Wayne@…

[Wayne Sallee]

I tried it on a Linux Guest, and it only failed on the first restart after installing guest additions. Then worked fine.

I'll have to try a test xp install. And see what happens.

But I know that in the past with an older version of vbox I had linux and windows guests end up with corrupt failed states. So how much of that bug has carried through, I don't know.

Wayne Sallee Wayne@…

[Wayne Sallee]

Windows XP fresh install test installs vbox additions fine and doesn't even fail on first boot like the others.

But Windows 8 and Windows 8.1 fail on first boot, and on save state. For me they are just test systems, so they don't matter to me.

And linux fails only on first boot.

First boot means boot right after installing vbox additions as required by the vbox additions installation.

Wayne Sallee Wayne@…

[Ancow]

I have a bit of a special use case, and apparently the same symptoms as described here:
Virtualbox version 4.3.8
Host: Win 7 64bit
Guest: Debian Linux 64bit, installed on a physical partition of this machine and usually run standalone, i.e. without Virtualbox.

The hang occurs fairly regularly.

[Ancow]

VBox.log (Ancow)

[tcs]

Same problem still exists with varying frequency on my laptop and desktop systems, but regularly. Host: Win 7, up-to-date Guest: Oracle linux 6.5, with latest VBoxAdditions Virtualbox: 4.3.10 r93012 Above mentioned symptoms are all correct, hang at 100% when saving machine state when closing or when creating snapshot. Let me know if I can send you any data of diagnostic value.

[frank]

Hi all, is there any Linux user which experiences this problem? Looking through all these comments it looks like this is a Windows-specific problem (I'm talking about the host, not the guest). This information would be helpful for narrowing down the problem.

[Ancow]

I'm primarily a Linux user and only rarely boot over to Windows. I experience this bug fairly regularly while in Windows, but have never seen it in Linux. (My guests are both Windows and Linux on my Linux host. My Windows host only has the one Linux guest.)

[Wayne Sallee]

I use Linux.

The "saved state" problem does happen with Linux host. It happens more often after an upgrade. Does not happen very often.

Wayne Sallee Wayne@…

[Petr Vones]

Do you use NAT or Bridged adapter ? Does it make any difference to the issue ?

[Ancow]

Windows: I've tried both NAT and Bridged - no difference.

Linux: I use NAT exclusively.

[c--]

I've been using VirtualBox (currently 4.3.10) on a Linux (Fedora) host for a long time now (at least 2 yrs) and never had such a problem. A few months ago, I started using VirtualBox (also currently 4.3.10) on a Windows (7) host and it has already happened 3 times (!) in the last couple of weeks. (This might of course be incidental, maybe the Linux build has the same bug and it simply hasn't happened to me yet.) Always the same behavior: I close the VM, "save state", it's saving along happily until it reaches 100%. At that point, the window is kind of frozen (doesn't do anything, stays at 100% forever, not possible to close the window or anything) although the GUI is still responsive.

Here's how the log file ends (there are no dates, I hope I got the right log), note the error in the last line:

09:07:20.739605 Changing the VM state from 'RUNNING' to 'SUSPENDING'.
09:07:20.870438 AIOMgr: Endpoint for file 'D:\VirtualBox-VMs\Fedora-1\Snapshots/{ef8b4d1a-db58-4439-b32d-936445d6b8c4}.vdi' (flags 000c0781) created successfully
09:07:20.970604 PDMR3Suspend: 230 979 165 ns run time
09:07:20.970615 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'.
09:07:24.944428 Changing the VM state from 'SUSPENDED' to 'SAVING'.
09:07:24.944891 VUSB: detached 'HidMouse' from port 1
09:07:51.308465 SSM: Footer at 0x8879e981 (2289691009), 34 directory entries.
09:07:51.308499 VUSB: attached 'HidMouse' to port 1
09:07:52.254256 SSM: Successfully saved the VM state to 'D:\VirtualBox-VMs\Fedora-1\Snapshots\2014-06-10T15-08-21-162471200Z.sav'
09:07:52.254270 Changing the VM state from 'SAVING' to 'SUSPENDED'.
09:07:52.387287 Console::powerDown(): A request to power off the VM has been issued (mMachineState=Saving, InUninit=0)
09:09:54.714663 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={8ab7c520-2442-4b66-8d74-4ff1e195d2b6} aComponent={Console} aText={Already paused}, preserve=false

This is very frustrating. The whole point of saving the state is to keep unsaved work and instead it's crashing the VM causing even more (data) loss.

[frank]

No doubt this is frustrating and the bug has to be fixed. The problem is that we cannot reproduce this behavior so far. This problem might be related to the Windows host, I remember seeing a couple of similar reports, IIRC all for Windows hosts.

[c--]

Replying to frank:

The problem is that we cannot reproduce this behavior so far.

Unfortunately I have not found a way to trigger this behavior reliably yet. It just seems to happen occasionally. I haven't recognized a pattern yet.

This problem might be related to the Windows host, I remember seeing a couple of similar reports, IIRC all for Windows hosts.

This is my impression as well since it has never happened to me on my Linux box.

If there's something I could run to find the culprit (or maybe there's a debug/verbose switch somewhere), let me know. At this point, the log is the only interesting thing to check that I can think of. It's difficult to find the right entries though, because there don't seem to be any dates/timestamps (except for the start date in the first 2 lines).

Next time it happens, I'll update this bug (with some log entries, hopefully).

[Petr Vones]

Replying to c--:

This is very frustrating. The whole point of saving the state is to keep unsaved work and instead it's crashing the VM causing even more (data) loss.

The saved state is not lost. See #comment:55 A recovery option in VirtualBox GUI would help to workaround this issue.

I also think that more verbose log is needed to diagnose the issue. Anything particular described here https://www.virtualbox.org/wiki/VBoxLogging ?

[stattert]

Never had this issue, untill recently, happened 3 times now. Very painful to loose so much work. Windows 7 Professional, Virtual Box 4.2.6 with a Centos 6 machine

92:58:09.837084 SSM: Successfully saved the VM state to 'D:\VirtualBox VMs\Centos 6.3 (64 bit)\Snapshots\2014-11-18T09-25-38-006817000Z.sav' 92:58:09.837106 Changing the VM state from 'SAVING' to 'SUSPENDED'. 92:58:11.871481 Console::powerDown(): A request to power off the VM has been issued (mMachineState=Saving, InUninit=0) 92:58:12.076461 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The virtual machine is being powered down}, preserve=false 92:58:19.192750 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The virtual machine is being powered down}, preserve=false 92:58:19.194719 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The virtual machine is being powered down}, preserve=false

same error repeated continually

[frank]

Actually what we would need is an application dump, full application dump preferred, I'm not sure if a minidump would also help. How to create such a dump:

• Download the Microsoft sysinternals process explorer
• Start it as Administrator
• In the tree view, make sure to find the actual VirtualBox.exe process. You should be able to identify it by the process memory size
• Right click on the process and do 'Create Dump' / 'Create Full Dump'

It would be nice if you could make such an application dump available for us, together with the corresponding VBox.log file. You can contact me directly via frank _dot_ mehnert _at_ oracle _dot_ com on where to send the dump file.

[0cd]

I created full dump and mini dump. Full dump : 1.3b, mini dump : 13m. I will send mini dump to frank's e-mail. If dev's need full dump, reply e-mail to me or add a comment here. My virtulBox's version is 4.3.6 r91406.

[frank]

0cd, did you already contact me and I missed the email?

[rogerdpack]

I think I just experienced this (linux guest 4.3.20) possibly caused by old guest extensions though, I'll reinstall and keep my eye on it.

[c--]

Replying to c--:

Next time it happens, I'll update this bug (with some log entries, hopefully).

I've dumped this Windows box and installed Linux. I guess this mostly affects Windows hosts, it hasn't happened to me since.

[Didjit]

Just happened to me as well. I'll attach two logs: "VBox bad save.log" and "VBox good save after bad save.log". Save proceeded to 100% and then hung. A .sav faile was created but the VBox Manager showed the VM as "corrupted", "invalid", or something like that. Relaunching resulted in the prior .sav being deleted.

The host machine is Windows 7 Professional SP1, 64b. Oracle VM VirtualBox Manager version: 4.3.28 r 100309

[Didjit]

Log for failed attempt to save state

[Didjit]

log for successful saving of state after a failed attempt

[weidenrinde]

After using virtualbox for a long time now, I got this problem now the second time within weeks. Host: Ubuntu Linux 12.04, Virtualbox: 4.3.10_Ubuntu

[Maxim-Allen Mukhin]

Happened to me 3d time this month on Virtual Box version 5.0.12 r104815 running on Windows 10 Pro x64, guest machine is running Ubuntu 14 desktop lts.

[tenuki]

Same here..

[TastyWheat]

This just happened for the first time ever. I'm running Vbox 5.1.6 on Windows 7 x64 host with CentOS 6 guest.

[FstTesla]

Still applies. Vbox 5.1.10, host OS Windows 10 x64 (version 1607), guest OS Windows Server 2012 x64.

[Jorrit]

VirtualBox 5.1.18 hangs at 100% progress while suspending. The last lines of the log file are:

05:42:21.897466 ************** End of Guest state at power off ***************
05:42:21.920472 PDMR3PowerOff: 22 996 539 ns run time
05:42:21.920515 Changing the VM state from 'POWERING_OFF' to 'OFF'
06:06:47.499244 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Invalid machine state: Saving}, preserve=false aResultDetail=0

Guest: Ubuntu 16.04 64 bit Host: Windows 10 64 bit

[ChogyDan]

I experienced this with a Windows 10 64 bit host and an 14.04 64 bit Ubuntu guest. The only thing weird was that I was trying to paste something during the closing process.

In greater detail: there was some text in the guest that I wanted to copy to email on my host. So I ctrl+c the text on the guest, hit save machine state on the guest, then clicked over to the window on host and attempted to paste. Pasting didn't work. I clicked over to guest, and saw that saving state had frozen at %100.

Ill attach the log. It is log.1 because I started up the machine again to see how bad the loss was.

[ChogyDan]

ChogyDan log after crash

[Qtax]

VirtualBox 5.2.0.18431 hangs at 100% of "saving the execution state". First time I've seen it. Host: Windows 10 x64, guest: Xubuntu 16.04.

[ite-klass]

Had this happen to me two times this week.

5.2.12 on Windows host.

[drew]

Why is this still happening, virtualbox 6.0.4, windows host, windows client

32:24:03.234169 PDMR3PowerOff: 2 015 179 ns run time
32:24:03.234192 Changing the VM state from 'POWERING_OFF' to 'OFF'
56:23:05.892325 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Invalid machine state: Saving}, preserve=false aResultDetail=0
60:01:10.257903 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Invalid machine state: Saving}, preserve=false aResultDetail=0
72:59:39.187518 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Invalid machine state: Saving}, preserve=false aResultDetail=0
74:43:53.720332 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Invalid machine state: Saving}, preserve=false aResultDetail=0
74:44:46.373841 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Invalid machine state: Saving}, preserve=false aResultDetail=0
93:40:45.224031 GUI: UIMediumEnumerator: Medium-enumeration finished!

[Mr.MikeB]

Just happened to me. First time I've ever had this happen (in probably 4+ years)

"Version 6.0.4 r128413 (Qt5.6.2)" (From Help-About)

Host: Windows 10 x64, guest: Ubuntu 18.04

The Snapshots directory showed the disk snapshot and memory .sav file.

When I killed the VirtualboxVM.exe process in windows explorer, the last .sav file disappeared, and the VM showed aborted and I am very sad.

I have the vbox.log file if that would help.

[Mike B]

I HAVE SUCCESSFULLY RECOVERED FROM AN OCCURRENCE OF THIS

Hopefully, this helps fix it, but for those of you who end up with an aborted VM, here's what I did to recover. This is using VBox Version 6.0.4, Windows 10 host, Linux Guest.

1) BEFORE ENDING any VBox processes, I opened the directory where the VM's .vbox and Snapshots reside. I copied (using control-C, control-V) the {VM-Name}.vbox file and the Snapshots/{timestamp}.sav file. The backup of the .vbox file is important in case you mess up your edited file.

Also, apparently, the memory dump completes successfully, and it hangs writing out the .vbox file. Killing the process erased the .sav file the first time it happened, which is why the BEFORE is critical.

2) Exit the Virtualbox UI. Use Windows task manager to kill off the hung vbox process (this erases the memory-state's .sav file, which is why it's important to copy it. Yes, it's repeated because it's important)

3) At this point, I rebooted the host because I don't trust Windows. Note that Windows displayed "VirtualBox still has open connections" on the shutdown screen and I eventually had to "restart anyways".

4) After the reboot, BEFORE opening Virtualbox, edit the .vbox file (I used notepad) and near the top, in the <Machine> element, add only a stateFile attribute with the path to the .sav file you copied in step 1:

eg: <Machine uuid="{....}" name="Ubuntu 18.04" OSType="Ubuntu_64" stateFile="Snapshots/2019-04-22T12-34-56-789012345Z.sav" currentSnapshots=.... >

Again, it is ONLY the stateFile="..." that needed to be added for me.

5) Save the file. Open Virtualbox, Cross your fingers and start your VM.

Good Luck!

[Wayne Sallee]

Thanks for the tip Mr.MikeB.

Wayne Sallee
Wayne@ WayneSallee.com

[Wayne Sallee]

I can now confirm that Mr.MikeB's method works.

5 years ago I had problems with this bug. Now I have problems with another bug that becomes this bug.

My host is Linux.

Sometimes when returning from hibernate, one of the guests will be frozen. I can open and save/close other guests, and they work fine.

I can also from the virtualbox window (not guest window), chose to save state, or shut down. I can even see the activity as normal in the miniature window in the top right corner of that window.

But the saved state fails as this bug that we have here for 8 years.

So I used Mr.MikeB's method. After having Virtualbox save the state of the guest, before killing all of the virtual box programs, I made a copy of snapshots folder, and <guest>.vbox. Then I closed Virtualbox, and then killed the other vbox programs still running, as they don't properly close. I did not need to restart the host.

At this point if I were to start Virtualbox, it will show the guest as being aborted. Close Virtualbox, and make sure that there are no other vbox processes running.

I copied the " <Machine uuid=" line. It's easy to just copy and replace the whole line.

I copied the backed up <guest>.vbox back into the snapshots folder.

Then I started up Virtualbox, and the guest showed up as saved. I started up the guest, and everything worked.

Wayne Sallee
Wayne@ WayneSallee.com

[Wayne Sallee]

Wow I just realized that I butchered the instructions with my last post.

1) When guest window is not responding, go to Virtualbox, and save the state.
2) Copy <guest>.vbox, and Snapshots directory into a backup directory.
3) Close and kill all vbox processes.
4) Copy back the " <Machine uuid=" line in the <guest>.vbox
5) Copy back the .sav file in the Snapshots folder.
6) Start Virtualbox, and start the guest.

Again, Mr.MikeB was the one that figured this out. I'm just adding the fact that I have found that this also works when the guest window becomes unresponsive, and is probably the same bug.

Wayne Sallee
Wayne@ WayneSallee.com

[Laubrino]

It happened to me several times in last week. Version 6.0.8 r130520 (Qt5.6.2). It's crazy this bug is 9 years (!) old.

[zpneun]

I also can confirm MikeB's method (here: host and guest Windows 10).

Same issue - when saving state, it stops at 100% (VBox 6.0.8)

I really was afraid trying it, because my VM has 8GB of memory, and the .sav File was nearly exactly 4GB in size. Two possibilities:

(1) in fact, the running VM could have been using nearly exactly 4 of the 8 GB

(2) OR there might really be a problem saving state of VMs with more than 4GB

I had no idea what would happen if (2) was the case and then trying Mike's solution. But I tried it and it seemed to work!

[GeorgeP]

MikeB's method (with some modification described below) also help me recover my virtual machine. I have had exact this problem from time to time for several years. I am now using VirtualBox 5.2.26 r128414 on a Windows 7 host (guest OS is Linux).

4) After the reboot, BEFORE opening Virtualbox, edit the .vbox file (I used notepad) and near the top, in the <Machine> element, add only a stateFile attribute with the path to the .sav file you copied in step 1:

eg: <Machine uuid="{....}" name="Ubuntu 18.04" OSType="Ubuntu_64" stateFile="Snapshots/2019-04-22T12-34-56-789012345Z.sav" currentSnapshots=.... >

Again, it is ONLY the stateFile="..." that needed to be added for me.

For me, in addition to add the stateFile attribute, I also need to manually delete the aborted="true" attribute in the Machine element.