Shutdown with saving state fails at 98%

[Shmu26]

Host: Linux Mint 19.1 Cinnamon
Guest: Windows 10 1809 x64
VB: Version 6.0.10 r132072 (Qt5.9.5)
Log attached

[erwin9]

Same problem here, with both 5.0.32 and 6.0.10 = VM save does not work, it aborts systematically.
I had to go back to a previous version for that to work (currently using 5.2.27_129562 which I had on my disk).

Same symptom in the log filled with a myriad of warnings

Code: Select all

OpenGL Warning: Assertion failed: rc == VINF_SUCCESS=0, file /home/vbox/vbox-5.2.32/src/VBox/GuestHost/OpenGL/state_tracker/state_snapshot.c

at the end of the log file.
No error saying that things were aborted by the way, or why ...

Linux RHEL 7.6
Kernel 5.1.16-1.el7.elrepo.x86_64
Xfce desktop
Guest Windows 10 1809 x64

[ManfredU]

Same problem here, with both 5.0.32 and 6.0.10 = VM save does not work, it aborts systematically.

Same symptom in the log filled with a myriad of warnings

Code: Select all

OpenGL Warning: Assertion failed: rc == VINF_SUCCESS=0, file /home/vbox/vbox-5.2.32/src/VBox/GuestHost/OpenGL/state_tracker/state_snapshot.c

at the end of the log file.
No error saying that things were aborted by the way, or why ...

Same problem.
VB 6.0.10
Guest: Guest Windows 10 x64[
Host: Ubuntu 18.04 4.18.0-25-generic

[mpack]

@Shmu26, you have an Intel Business Graphics chipset on your host. I'm seeing lots of warnings in the log amounting to: we can't really accelerate your graphics because the host drivers are crap.

Intel are not famous for the quality of their OpenGL implementations, so maybe you need to turn off 3D acceleration (host OpenGL is how VirtualBox implements accelerated 3D graphics in a VM). Basic 2D graphics should still work fine, but maybe you can try accelerated 2D graphics too.

Or, try the new generation VBoxSVGA graphics that the VirtualBox devs are working on in v6.

[Shmu26]

Thanks. I now turned off the 3d acceleration, I don't think I need that for MS Office apps, anyways.
Is there maybe something else I can turn off to get seamless mode to work better? The issue I am facing is that the host wallpaper covers part of the screen.

[mpack]

One issue per topic please.

[erwin9]

Hello, maybe turning off 3D acceleration is a workaround for some of us, but anyway it is working with lower levels, and it is not working with both 5.0.32 and 6.0.10.
So there is a regression and something should be corrected it seems.

Note also that VBoxSVGA is only with 6, not with 5, so that workaround cannot work for all.

[mpack]

My workaround was never intended to work for all. If your problem is the same as Shmu26 then I provided a solution. If your problem is not the same then start your own topic, discussing a specific VirtualBox version. In this topic I will not address anything but the OPs posts.

[erwin9]

Well, I have the same symptom, I cannot save the VM, it aborts, hence me posting here.
I cannot judge whether this is the same cause though, sorry. I am fine to open another post if you want.

[Sechs]

Hi.

This week-end, I updated my VirtualBox from 5.2.20 to 6.10 (windows 10 host).
Everything seemed to run smoothly, but when i tried to save my current vm state (ubuntu 18.04), unfortunately the vm crashed, resulting in a windows error displaying :

Instruction at 0x... referenced memory at 0x.. The memory could not be read.

Strangely, if I uncheck " "Enable 3D acceleration", that save state crash does not occur anymore.

Here are the attached logs.

Thanks in advance for your help,

Aurelien

[socratis]

You had another 3D related problem back in Feb/2019. Have you updated your Nvidia drivers? I see a lot of:
[quote=""VBoxHardening.log""]

2214.413c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff91d3d0000
          'C:\WINDOWS\System32\OPENGL32.dll'
...
1168.4a50: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0xc0000005 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 534528 ms, the end);

[/quote]... which indicates a hardening problem. Please read really carefully the following FAQ: Diagnosing VirtualBox Hardening Issues for some generic guidelines/ideas. Remember, these are guidelines, not the exact solution, you have to use your judgement as to which program might be responsible.

I would start by completely uninstalling the following, or adding an exception for all-things VirtualBox:

1168.4a50:     FileDescription: Kaspersky Unified Driver
1168.4a50:     FileDescription: Filter Core [fre_win8_x64]
1168.4a50:     FileDescription: Core System Interceptors [fre_win8_x64]
1168.4a50:     FileDescription: Packet Network Filter [fre_win8_x64]
1168.4a50:     FileDescription: Keyboard Device Filter [fre_win8_x64]
1168.4a50:     FileDescription: Mouse Device Filter [fre_win8_x64]
1168.4a50:     FileDescription: Network Processor [fre_wnet_x64]
1168.4a50:     FileDescription: Filtering Platform Helper Class
1168.4a50:     ProductName:     Kaspersky™ Anti-Virus ®

Also, from your VBox.log, I see about five gazillion of:
[quote=""VBox.log""]

00:05:52.996060 OpenGL Warning: Trying to switch contexts when the attribute stacks weren't empty.  Currently, this is not supported.
...
00:08:45.307759 OpenGL Warning: Assertion failed: rc == VINF_SUCCESS=0, file F:\tinderbox\win-6.0\src\VBox\GuestHost\OpenGL\state_tracker\state_snapshot.c, line 622

[/quote]
So, try to 1) completely uninstall Kaspersky, 2) update your Nvidia drivers.

[Empty Vessel]

I'm having the same issue with 6.0.10 using my virtual Windows 7 and 8.1 guests, with all the OpenGL errors towards the end of the log. My laptop contains both an Intel 630 and an Nvidia 1060, and the issue occurs using both (logs attached for Windows 7). Turning off 3D acceleration cures the problem. Both GPUs have current drivers according to manufacturers websites.

** Update ** - I've reinstalled 6.0.8, and downgraded the GAs as this was the last version I used. All my guests now suspend cleanly with 3D acceleration enabled. I'll stick with this build for now... Uploaded logs 608 in case there's anything useful to be learned from them.

[ddbug]

While exiting & save guest VM state, Vbox 6.0.10 crashes:

VirtualBoxVM.exe - Application Error
---------------------------
The instruction at 0x00007FFD807DCB3E referenced memory at 0x0000000000003288. The memory could not be read.

Looks like referencing 0 pointer.

I don't have debugger on the host so have to terminate and lose the VM state.

Vbox was updated to 6.0.10 from 6.0.6.

Interesting snippet from the log:

Code: Select all

00:02:47.690986 Changing the VM state from 'RUNNING' to 'SUSPENDING'
00:02:47.784748 AIOMgr: Endpoint for file 'XXXXXXXXXX\Snapshots/{893c7750-04d9-4828-952b-1ed89b558bba}.vdi' (flags 000c0781) created successfully
00:02:47.851499 PDMR3Suspend: 160 432 434 ns run time
00:02:47.851519 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
00:02:47.851532 Console: Machine state changed to 'Paused'
00:02:50.215689 GUI: Request for close-action to save VM state.
00:02:50.215713 GUI: Passing request to save VM state from machine-logic to UI session.
00:02:50.216053 Console: Machine state changed to 'Saving'
00:02:50.216633 Changing the VM state from 'SUSPENDED' to 'SAVING'
00:02:50.217573 VUSB: Detached '0000000005f29b70[proxy 0bda:0129]' from port 1 on RootHub#1
00:02:53.624234 OpenGL Warning: Assertion failed: rc == VINF_SUCCESS=0, file F:\tinderbox\win-6.0\src\VBox\GuestHost\OpenGL\state_tracker\state_snapshot.c, line 622
.......... LOT OF SAME LINES ..............
00:02:53.624234 OpenGL Warning: Assertion failed: rc == VINF_SUCCESS=0, file F:\tinderbox\win-6.0\src\VBox\GuestHost\OpenGL\state_tracker\state_snapshot.c, line 622

00:02:53.627872 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 0000000000001628!!!
00:02:53.627879 
00:02:53.627879 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=00007ffd807dcb3e
00:02:53.627883 ExceptionInformation[0]=0000000000000000
00:02:53.627887 ExceptionInformation[1]=0000000000003288
00:02:53.627890 
00:02:53.627890 cs:rip=0033:00007ffd807dcb3e

Complete log is attached.

Thanks.

-- pa

[banzeo]

Hello,

I face a similar problem on Linux Debian 10 (buster) host with a Win10 Virtual Machine.

When I choose to close the Machine & Save the state (File | Close | Save the state of the machine), it starts saving, and after some time the progress bargoes to 100% and in the VirtualBox GUI the state of the virtual machine is "Aborted"

I didn't have such a problem with 5.2.30, it appeared with 5.2.32
It is still present in the dev build 5.2.33-132430

Steps:
1 Install dev build
2 Launch the VBox GUI
3 Launch the VM (Win10)
4 Once the VM is loaded, go to File | Close | Save the state of the machine
5 in the VBox GUI the VM is in state "Aborted"
6 Relaunch the VM
7 In the VM, Stop Windows (Start menu / Halt)
8 In the VBox GUI the VM is in state "Powered Off" (
9 Create the log as suggested in your post. I added VBox.log , VBox.log.1 just in case.


Developpment build used + extension pack :
VirtualBox-5.2.33-132430-Linux_amd64.run
Oracle_VM_VirtualBox_Extension_Pack-5.2.33-132271.vbox-extpack

[banzeo]

I don't have such a device, so that can not be the reason for me.