VirtualBox

Ticket #16350 (new defect)

Opened 6 years ago

Last modified 2 years ago

VERR_SSM_LOADED_TOO_MUCH when restoring snapshot

Reported by: mammoth Owned by:
Component: VM control Version: VirtualBox 5.1.12
Keywords: VERR_SSM_LOADED_TOO_MUCH Cc:
Guest type: Windows Host type: Windows

Description

I cannot resume VM state from existing snapshot, getting following error:

Failed to load unit 'vga' (VERR_SSM_LOADED_TOO_MUCH).

E_FAIL (0x80004005) ConsoleWrap IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Host: Windows10 Guest: Windows10

Attachments

Win10_RMS-2017-01-03-17-00-26.zip Download (142.9 KB) - added by mammoth 6 years ago.
VBox.log.gz Download (145.3 KB) - added by jimav 5 years ago.
VBox.log for comment #5, showing error messages about 'vga' (gzipped, it is too large otherwise)

Change History

Changed 6 years ago by mammoth

comment:1 Changed 6 years ago by DiaLight

comment:2 Changed 6 years ago by socratis

You upgraded VirtualBox while your VM was in a saved state. You should NOT do that, ever. You now have two available options:

  1. Lose/discard the saved state. That will enable you to start the VM, but with some loss of information since the last boot/snapshot.
  2. Downgrade VirtualBox to the version that you upgraded from. That will allow you to restore the saved state, shut down the VM properly and then upgrade VirtualBox to its current version.

Remember, a saved state is similar to hibernating your OS. Now imagine that while your OS is hibernating, you start changing components in your PC (BIOS, GPU, USB, network etc). It's not going to like it when it goes out of hibernation, right? Same thing with VMs; they don't like being upgraded while "hibernating".

comment:3 follow-up: ↓ 4 Changed 6 years ago by Bucky

"Downgrade VirtualBox to the version that you upgraded from."

Nice theory. Too bad it doesn't work.

Seriously, I downgraded back to the previous version of VB and got the same error. Waste of time. I still can't start the VM, at all.

Not to mention that many times in the past, I have upgraded VB underneath hibernated VM's, without getting errors.

The cause of the problem lies elsewhere.

Last edited 6 years ago by Bucky (previous) (diff)

comment:4 in reply to: ↑ 3 Changed 6 years ago by socratis

Replying to Bucky:

Nice theory.... Too bad it doesn't work... Waste of time....

Please try to keep your cool and focus. Plus, this is a double answer to both you and @DiaLight from ticket #16386.

to the previous version of VB

I didn't say "to the previous", I said to the last working version. Huge difference. That has never failed, unless you are facing an extremely rare case where you can't restore a saved state within the same version of VirtualBox, which is indeed really rare. But you haven't proved it yet, I'm sorry. Please try again to downgrade to the last known working VirtualBox version.

The cause of the problem lies elsewhere.

I have a couple of suspicions but I'll need more evidence before reaching a conclusion.

comment:5 Changed 6 years ago by Bucky

Thanks. I ended up backtracking a few snapshots back, and that did the trick.

comment:6 Changed 5 years ago by jimav

Exact same problem here, always using VB 5.1.18, _not_ across an update.

In fact, I created a snapshot on a _running_ vm (from the Machine menu of the VM gui), and kept working. Several hours later VirtualBox crashed spontaneously. I rebooted the host and loaded the the VM started okay from the "current state". But after restoring the snapshot, the error occurs.

In case it might matter: The snapshot was taken on a running VM from the VM gui's Device menu, rather than taken on a shut-down VM.

4/17/2017: Happened again, so it seems like a real bug. Closed, saving state; created snapshot "A". Restored an older snapshot, started, and ran for a while; did virtual power-off (not interested in state); restored snapshot "A". Tried to start, and got the VERR_SSM_LOADED_TOO_MUCH error. All in the space of about 5 minutes. Plenty (58G) of disk space avilable. VB 5.1.18.

Last edited 5 years ago by jimav (previous) (diff)

Changed 5 years ago by jimav

VBox.log for comment #5, showing error messages about 'vga' (gzipped, it is too large otherwise)

comment:7 Changed 5 years ago by jimav

Sorry, the VBox.log.gz was for comment #6 (not #5 as it says).

I'm guessing this bug might be sensitive to the host's graphics. The host is Ubuntu 16.04 . X server is using VIDIA GLX Module 375.39. Using compiz.

There are OpenGL assertion errors in the VBox.Log:

Assertion failed: ptl->bytes=0, file /home/vbox/vbox-5.1.18/src/VBox/GuestHost/OpenGL/state_tracker/state_snapshot.c, line 574
00:00:13.038536 OpenGL Warning: Assertion failed: ptl->bytes=0, file /home/vbox/vbox-5.1.18/src/VBox/GuestHost/OpenGL/state_tracker/state_snapshot.c, line 574
00:00:13.038540 OpenGL Warning: Assertion failed: ptl->bytes=0, file /home/vbox/vbox-5.1.18/src/VBox/GuestHost/OpenGL/state_tracker/state_snapshot.c, line 574
00:00:13.213704 AssertLogRel /home/vbox/vbox-5.1.18/src/VBox/VMM/VMMR3/SSM.cpp(6340) int ssmR3DataReadUnbufferedV2(PSSMHANDLE, void*, size_t): !pSSM->u.Read.fEndOfData
00:00:13.213723 cbBuf=989921670
00:00:13.213728 AssertLogRel /home/vbox/vbox-5.1.18/src/VBox/HostServices/SharedOpenGL/crserverlib/server_main.c(2339) crVBoxServerLoadStatePerform: RT_SUCCESS_NP(rc)
00:00:13.213737 VERR_SSM_LOADED_TOO_MUCH (-1831) - A restore routine attempted to load more data then the unit contained.
Last edited 5 years ago by jimav (previous) (diff)

comment:8 follow-up: ↓ 9 Changed 2 years ago by JMH

I had the same problem without upgrading VirtualBox. Had a running VM under 6.1.6 on a Windows 10 laptop. Dell Command Update utility updated the host's graphics driver, requiring a host reboot. Saved the VM state, rebooted the host and now cannot start the saved VM.

comment:9 in reply to: ↑ 8 Changed 2 years ago by xplt

Replying to JMH:

I had the same problem without upgrading VirtualBox. Had a running VM under 6.1.6 on a Windows 10 laptop. Dell Command Update utility updated the host's graphics driver, requiring a host reboot. Saved the VM state, rebooted the host and now cannot start the saved VM.

Looks like I've encountered the same issue today: I also used VBox 6.1.6 on a Windows 10 host (with Fedora 31 as a guest), installed an update for Windows and after that, I was unable to restore the snapshot (had the same error message). I had to "Discard" snapshot's state, so VBox didn't crash, and loaded the guest system.

comment:10 Changed 2 years ago by tothpaul

just had this error the VM is under W10, the host under W8.1. it is a laptop which was on standby. when i reactivated it, the VM was frozen, I wanted to try to save the state and restore it. Version 6.1.12 r139181 (Qt5.6.2)

Last edited 2 years ago by tothpaul (previous) (diff)

comment:11 Changed 2 years ago by AnrDaemon

Could this be related to upgraded GFX drivers?

I've backtracked a number of versions but still unable to restore the saved state.

comment:12 Changed 2 years ago by glossner

I also had this problem on 8/17/2020. My system is an alienware desktop with 2080 GPU.

I checked the video driver install date. No change.

I didn't update the VM manager.

The VM Manager would not allow me to change the 3D acceleration checkbox.

I was able to export the VM and reimport it. After import I unchecked 3D acceleration on the imported VM and it restarted with no lost state. I shut down the machine, checked 3D acceleration, and it restarted fine.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use