VirtualBox

Ticket #5828 (new defect)

Opened 4 years ago

Last modified 3 years ago

Unable to restore VM's saved state

Reported by: Wipeout Owned by:
Priority: major Component: other
Version: VirtualBox 3.1.2 Keywords:
Cc: Guest type: Windows
Host type: Windows

Description

Information duplicated from this forum post:  http://forums.virtualbox.org/viewtopic.php?f=6&t=26019&p=116632#p116632.

With 3.1.2 and snapshots taken since installing 3.1.2, I get the following when restoring from a saved state:

00:00:06.170 Changing the VM state from 'DESTROYING' to 'TERMINATED'. 00:00:06.419 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={6375231a-c17c-464b-92cb-ae9e128d71c3} aComponent={Console} aText={Failed to load unit 'pgm' (VERR_SSM_INTEGRITY_REC_TERM_CRC)} aWarning=false, preserve=false 00:00:06.420 Power up failed (vrc=VERR_SSM_INTEGRITY_REC_TERM_CRC, rc=E_FAIL (0X80004005))

When discarding saved state information, I'm able to start the machine without issue. Restored to earlier snapshot and am able to save and restore states without issue.

I'm seeing this on two different XP VMs. Have not tried to take a new snapshot of my Ubuntu VM yet, but did notice that when attempting to take a snapshot of one of my XP VMs that was powered off, the VBoxGUI crashed.

Attachments

1VBox.log Download (72.0 KB) - added by Wipeout 4 years ago.
Sample VBox.log with crash logged.
VBox.log.1 Download (70.3 KB) - added by jimoe 3 years ago.
I decided to upload the log file anyway.
VBox.log Download (74.0 KB) - added by bernie 3 years ago.
VBox.2.log Download (74.1 KB) - added by bernie 3 years ago.
VERR_SSM_INTEGRITY_DECOMPRESSION
VBox.log.2.1 Download (70.2 KB) - added by jimoe 3 years ago.
Yet another instance's log file
dmesg.txt Download (4.1 KB) - added by jimoe 3 years ago.
Crash dump of kernel trap.
VBox.3.log Download (91.0 KB) - added by TheDreamer 21 months ago.
This problem affects me now and then, here's the log of the latest occurence

Change History

Changed 4 years ago by Wipeout

Sample VBox.log with crash logged.

comment:1 Changed 4 years ago by davidef1986

I'm having the same issue on linux-x64 host with windows xp 32bit guest

comment:2 Changed 4 years ago by hasinasi

Is this by any chance related to this:  http://forums.virtualbox.org/viewtopic.php?f=1&t=26340&p=121027&hilit=saved#p121027

In my case (kubuntu 9.10-32bit host, VB 3.1.2), this did the trick.

comment:3 Changed 4 years ago by meptalon

I had the same problem with a Windows 7 x86 guest on a Windows 7 x64 host (VB 3.1.8r61349). Resetting the path for snapshots did cure the problem. Big thanks to Hanisasi

comment:4 Changed 3 years ago by jimoe

I have the same problem.

VBox 4.0.2. Opensuse v11.3, linux 2.6.34.7-0.7-desktop x86_64. WinXP sp3 32bit.

Sometimes attempting to restore from a Saved state produces a similar error. The only option is to Discard the saved state and boot from a powered off state. I'd add a log file except there is nothing any different that what is already provided.

00:00:02.816 Changing the VM state from 'DESTROYING' to 'TERMINATED'.
00:00:02.931 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={515e8e8d-f932-4d8e-9f32-79a52aead882} aComponent={Console} aText={Failed to load unit 'pgm' (VERR_SSM_INTEGRITY_REC_TERM_CRC)}, preserve=false
00:00:02.932 Power up failed (vrc=VERR_SSM_INTEGRITY_REC_TERM_CRC, rc=NS_ERROR_FAILURE (0X80004005))

Changed 3 years ago by jimoe

I decided to upload the log file anyway.

comment:5 Changed 3 years ago by frank

That error message says that the saved state is not consistent. Did you experience any write problems or disk-full conditions while the VM was suspended the last time?

comment:6 Changed 3 years ago by jimoe

I have been having problems with kernel traps recently since upgrading to VB v4.0. See ticket #8303. The earlier comment may be an artifact of that report.

comment:7 Changed 3 years ago by bernie

I'm reporting this error also. I've successfully saved and restarted my VMs a number of times, then this morning, I get:
Failed to open a session for the virtual machine xxx
Failed to load unit 'pgm' (VERR_SSM_INTEGRITY_REC_TERM_CRC)
I'll attach my log file.
I was using the VM just yesterday - I saved my machine state, suspended my machine overnight, and then couldn't restart my VM this morning. I'm using the same version of VirtualBox for both saving and restarting (3.2.8-ose).
I don't have any saved snapshots, but I do have a shared folder, and 2 network adaptors, one NAT, and one Host-only.
I didn't receive any messages about write problems, and have plenty of disk space (17GB free on my partition with the vdi files on it, 55GB free on '/', and 34GB free in /home.
VirtualBox version: 3.2.8_OSEr64453
Host OS: Ubuntu 10.10, 2.6.35-25-generic
Unfortunately, I will have to discard my machine state and start it again, as I have to use it today. I'm just posting in the hope that it might help you fix this problem.

Changed 3 years ago by bernie

comment:8 Changed 3 years ago by bernie

Similar issue again this morning - different VM, slightly different error message (VERR_SSM_INTEGRITY_DECOMPRESSION). This VM doesn't have any shared folders, so that's not the problem. No saved snapshots either. 2 network adapters again (NAT and Host-only).

I'm running 2 VMs at the same time - closed both last night (saving machine state). One restored successfully this morning, one didn't.

Changed 3 years ago by bernie

VERR_SSM_INTEGRITY_DECOMPRESSION

comment:9 Changed 3 years ago by jimoe

Yup, me too. It just happened with the same error message as Bernie noted.

Changed 3 years ago by jimoe

Yet another instance's log file

comment:10 Changed 3 years ago by jimoe

VBox v4.0.4 just demonstrated the defect again. See the log file VBox.log.2.1, about line 810.

comment:11 Changed 3 years ago by frank

When you closed the VMs by saving the VM state -- did that succeed or did the VM crash during saving the state?

comment:12 Changed 3 years ago by jimoe

Saving the VM state has always succeeded. It is restoring it that fails.

comment:13 Changed 3 years ago by frank

The question is if saving the state was successfully finished or ob the VM crashed before the state was saved (very unlikely, but still...).

comment:14 Changed 3 years ago by jimoe

And again. This time it was shortly after a kernel trap had occurred. Also, after the VM failed to start, VirtualBox itself would not open.

After rebooting the VM started without a problem, as did VirtualBox. It was apparently correctly saved; the system had become destablized to the point where VirtualBox could not work.

Changed 3 years ago by jimoe

Crash dump of kernel trap.

Changed 21 months ago by TheDreamer

This problem affects me now and then, here's the log of the latest occurence

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use